compressor 4.4.5 - video rendering error: 10008

Question

Level 1

9 points

compressor 4.4.5 - video rendering error: 10008

Do you anybody knows where is logs from compressor ? I would like to find exact place of error in source video :-) It's simple right ? :-)

WHY ?

I'm using FCP on iMac Pro with Catalina to editing and cut videos. Because Apple don't have any analytic tool to check source videos before encoding :-( I'm using "SHARE master file" in FCP. YES this takes lot of time on CPU but if the source video have a problem like glitch, black screen etc. FCP inform where exactly problem is ... number of frame, exact time, name of source file, etc. So FCP was my debugging tool for errors in source videos.

Today is a first day when FCP complete encoding source videos without any problem and compressor NOT ... endend with a obligate error "video rendering error: 10008". IMHO FCP use to encoding only CPU, but compressor use GPU to accelerate whole encoding process (maybe).

I really don't want split my more than 2 hours video to 20 pieces and encode every piece separately in compressor. It's not professional solution from 21 century :-(

Thanks for HELP

iMac Pro, macOS 10.15

Posted on Nov 1, 2019 5:49 AM

Reply

Answer 1

MarekBukal Author

Level 1

9 points

Nov 5, 2019 7:52 AM in response to MarekBukal

UPDATE: From my point of view i think the whole problem with Final Cut Pro are corrupted media in project library. Those media hangs FCPX, crashing encoding, etc.

So today i'm developing "small script" to analyze, fix and revert corrupted media in my library. First test are amazing and now FCPX working like before. No freeze, no rotating beach ball and my project was for the first time EXPORTED !

link to gitlab: https://gitlab.com/manasovo/repair-tool-for-final-cut-pro-media/

Reply

Answer 2

BenB

Level 6

13,348 points

Nov 3, 2019 6:55 AM in response to MarekBukal

FCPX and Compressor use the same compression engine. How much CPU and how much GPU used depends on the codec you're working with, not the app.

What is the codec of your source video, and what are you trying to encode it to?

What percentage of your system drive is free space?

Reply

Answer 3

MarekBukal Author

Level 1

9 points

Nov 3, 2019 12:10 PM in response to BenB

i have a different codecs in source videos like h.264 and h.265 HEVC, free 780GB (32%) on local storage and 13TB (60%) on NAS where is FCP library located. Target is 4K mean 3840x2160 with 59.94 fps.

I don't think the problem is in the hardware, codec etc. One or more source video is corrupt ... for example log from ffmpeg bellow:

CMD line: ffmpeg -v error -i bad_source_video.mov -f null -

[hevc @ 0x7ffb540d1000] Invalid NAL unit size (1687082343 > 1020805).

[hevc @ 0x7ffb540d1000] Error splitting the input into NAL units.

[hevc @ 0x7ffb540dc000] Could not find ref with POC 0

Error while decoding stream #0:0: Invalid data found when processing input

[null @ 0x7ffb54009c00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 304 >= 300

[null @ 0x7ffb54009c00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 304 >= 301

[null @ 0x7ffb54009c00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 304 >= 302

[null @ 0x7ffb54009c00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 304 >= 303

[null @ 0x7ffb54009c00] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 304 >= 304

[hevc @ 0x7ffb54084000] Duplicate POC in a sequence: 28.

[hevc @ 0x7ffb540b0000] Duplicate POC in a sequence: 29.

Error while decoding stream #0:0: Invalid data found when processing input

If you have this source video (BTW takes from iPhone) in project whole encoding stopped.

I just need to know on which file Compressor stuck and repair it or cut it ... depends :-)

That's all

P.S. if the Compressor and FCP have a same engine what is the benefit of Compressor ? More settings, more options, etc ? I need to make some tests with quality, size of file, time to encode etc. :-) But first i need to repair my project of course.

Reply