Problem with Prores 422HQ-file

[dff.ffm]

Hi there, have a Prores 422HQ file with 400 Gigs, 85 minutes, 4K.
After making all adjustments, I wanted to start process, but "examing audio" ran for one hour 15 minutes. On I5-9600K, 32 Gigs RAM. Suspected the low core number of my machine and ran same thing on a "gamers" machine, with double cores and newer processor. Resulting in 65 minutes of audio analyze.
Thankyou for your good work - TG

[dff.ffm]

Stream #0:0(eng): Video: prores (HQ) (apch / 0x68637061), yuv422p10le(tv, bt709, progressive), 3840x2160, 698823 kb/s, SAR 1:1 DAR 16:9, 24 fps, 24 tbr, 24 tbn, 24 tbc (default)
Metadata:
creation_time : 2024-02-06T14:37:51.000000Z
vendor_id : appl
encoder : Apple ProRes 422 HQ
timecode : 00:00:00:00
Stream #0:1(eng): Audio: pcm_s24le (lpcm / 0x6D63706C), 48000 Hz, 6 channels, s32 (24 bit), 6912 kb/s (default)
Metadata:
creation_time : 2024-02-06T14:37:51.000000Z
vendor_id : [0][0][0][0]
Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
Metadata:
creation_time : 2024-02-06T14:37:51.000000Z
timecode : 00:00:00:00
Unsupported codec with id 0 for input stream 2

[carl]

Is the prores file on a local hard drive? I suspect the bottleneck here would be the disk IO bandwidth.

[dff.ffm]

prores was copied to my local HD. Project-Output was targeted to (fast) external drive.
TG

[carl]

Thanks for the information. There is an open ticket about this general problem (slow audio analysis). It sounds like you are indeed CPU-bound. What version of DCP-o-matic are you using?

[hostsurvive]

Hey folks, I'm encountering a bit of a snag here. I've got a Prores 422HQ file clocking in at a hefty 400 gigs, spanning 85 minutes, in glorious 4K resolution.

After meticulously adjusting everything, I geared up to kickstart the processing, only to find that the "examining audio" phase took a staggering one hour and 15 minutes to complete. My rig boasts an Intel Core i5-9600K processor and a hefty 32 gigs of RAM. Suspecting that the limited core count might be bottlenecking the process, I decided to run the same task on a "gamers" machine equipped with double the cores and a newer processor.

The result? A significantly improved audio analysis time of 65 minutes. It seems the additional processing power made quite the difference.

A huge thanks to everyone involved in this endeavor for their hard work and dedication!

[dff.ffm]

@ hostsurvive
monkey see - monkey do.
congratulations!

[dff.ffm]

@ carl
2.16.74