I am having an issue creating an RDD9 compliant MXF using FFMPEG within FFASTrans.
I am transcoding from a QT Pro Res 422 HQ MOV to XDCAM MXF then re-wrapping using BMX Trans Wrap to ensure RDD9 compliance.
The expected file specs after transcode are:
PAL 1920x1080 50i XDCAM 422 50mbps long-gop, closed gop. M=3, N=12
2x AES PCM audio streams, 1 channel in each.
My command is as follows:
c:\FFAStrans1.0.0\FFAStrans1.0.0\Processors\ffmpeg \x64>ffmpeg.exe -i "z:\100_incoming_media\OM_TEST.mov" -profile:v 0 -level:v 2 -map 0:1 -r 25 -pix_fmt yuv422p -aspect 16:9 -intra_vlc 1 -b:v 50000000 -minrate 50000000 -maxrate 50000000 -bufsize 17825792 -rc_init_occupancy 17825792 -sc_threshold 1000000000 -non_linear_quant 1 -color_primaries bt709 -color_trc bt709 -colorspace bt709 -seq_disp_ext 1 -video_format component -color_range 1 -chroma_sample_location topleft -signal_standard 4 -dc 8 -qmin 3 -qmax 28 -mpv_flags +strict_gop -strict 1 -g 12 -bf 2 -field_order tt -top 1 -flags +cgop+ildct+ilme -alternate_scan 1 -map 0:2 -map 0:3 "z:\10000_temp\MXFTEST\OM_Test_Out.mxf"
Everything is fine, except for the GOP structure.
Running FFProbe, the GOP structure is IBB PBB PBB PBP
I submit this to clients Baton File QC and they fail it, as the expected GOP is: IBB PBB PBB PBB
If I remove the +cgop flag from the command I do get the desired IBB PBB PBB PBB
But as expected, the GOP isn't closed and fails file QC.
What else is interesting, doing the exact same transcode with the same parameters within Telestreams Vantage transcoding system
I get a GOP structure that looks like this at the very beginning "BB IBB PBB PBB PBB". It opens with two B frames at the beginning of the file and then subsequently follows the correct closed GOP pattern throughout.
I'm thinking I am either doing something wrong with the FFMPEG Command, or just missing something.
Or the outputted file from FFMPEG and its GOP structure is correct and Baton File QC parameters are being too strict.
Or there is slim chance that there is bug with FFMPEG creating XDCAM Closed Gop files.
At the end of the day, it's down to the difference between a "B" frame and "P" frame at the end of a Closed GOP outputted from FFMPEG.
I understand that Closed GOPs are separate and don't cross reference each other, hence why there would be a P frame at the end of the closed GOP and not a B frame...
Just annoying that the clients Baton file QC says this can't be so... a literal "computer says no" moment.
Anways, hope this made sense. Happy to clarify further.
+ Reply to Thread
Results 1 to 5 of 5
Did you ever get this worked out? I suspect your "client" is the same as mine
This thread (https://ffmpeg-user.ffmpeg.narkive.com/TXOnNTfT/ffmpeg-mpeg-2-gop-structure) suggests that the issue is with FFMPEG, though.
Ii did. In the end I just had to have a sit down with the client and explain that just because Baton QC software is complaining, doesn't necessarily mean it won't fail on play out.
Just a pedantic Client at the end of the day.
I'm in the middle of a house move, but can send you tomorrow the ffmpeg code I use for our client, if you like.
Oh, that would be great! Thanks.
Sorry for the late reply mate!,
here is the FFmpeg parameters I used:
-profile:v 0 -level:v 2 -map 0:0 -r 25 -pix_fmt yuv422p -aspect 16:9 -intra_vlc 1 -b:v 50000000 -minrate 50000000 -maxrate 50000000 -bufsize 17825792 -rc_init_occupancy 17825792 -sc_threshold 1000000000 -bf 2 -non_linear_quant 1 -color_primaries bt709 -color_trc bt709 -colorspace bt709 -seq_disp_ext 1 -video_format component -color_range 1 -chroma_sample_location topleft -signal_standard 4 -dc 8 -qmin 3 -qmax 28 -strict 2 -g 12 -mpv_flags +strict_gop -field_order tt -top 1 -flags +ildct+ilme+cgop -alternate_scan 1 -map 0:1 -map 0:2
I also use BMXTransWrap as well, to re-wrap it to an RDD9 compliant container.
I do all this within FFAStrans - as its all part of greater workflow/automation.
Hope this helps.