I guess not only interesting for @Silicon who PM'ed me about analyzing mpeg2 headers for a specific error,
here some example job that checks if vbv_delay values below 10.000 were found. If there were such values, the workflow will fail at the end.
I am not 100% sure if this is a real MUST for xdcam but in videos that worked for Silicon, all vbv_delay values were larger than 50.000, so i guess the check should be fine.
This could be a starting point for doing very deep QC checks and see if the mpeg2 stream for example is XDCAM compatible (or check other standards).
@Silicon, i believe you can use this in forward production to detect if a video is affected (without import to mam), so you get your logs from the video server and can send them to the vendor.
Analyze mpeg headers - mini QC example workflow
Analyze mpeg headers - mini QC example workflow
emcodem, wrapping since 2009 you got the rhyme?
Re: Analyze mpeg headers - mini QC example workflow
Hi emcodem
I haven’t noticed this post until today - shame on me
We are still waiting for a new occurrence of the issue, but it is summer so the amount of studio production is lower.
I will definitely use it for detection of potentially incompatible files.
I haven’t noticed this post until today - shame on me
We are still waiting for a new occurrence of the issue, but it is summer so the amount of studio production is lower.
I will definitely use it for detection of potentially incompatible files.
BR,
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)
Silicon
--------
FFAStrans 1.3.0.2; WebInterface 1.3.0.0
Manager: VM: 2x Xeon E5-2630v3@2.4GHz, 8GB RAM
Workers: 3x HP DL360 G9 (2x Xeon E5-2643v3@3.4GHz,16GB RAM, nVidia M2000)+ 2x Lenovo SR665 (2x AMD EPYC730216C@3.0GHz,128GB RAM, nVidia P2200)