[FFmpeg-user] HD MXF SMPTE ST377 Standard Compliance Problem with multiple IndexTableSegments carring Unique ID twins (maybe a bug)
Chris von Görstinger
christophgerstbauer at gmail.com
Mon Nov 19 16:00:41 EET 2018
Hello Martin Vignali,
When rewrapping the ffmpeg-made mxf with bmxtranswrap I used following 2
types to test: OP1A or RDD9.
OP1A: Index Table Segments Problems are gone, but there is now a SAMPLERATE
RDD9: Index Table Segments Problems are gone, but there is now a KLV
Preface Problem (Preface does not start at a KLV grid line (KAGSIZE=512))
But yes, the index table segment problems are gone when rewrapping with BMX.
The issue ere is: We want to use ffmpeg to make a Standard Compliant (just
OP1a) file. Without rewrapping (rewrapping would cost extra time to remake
the file). I want to spare every unnecessary transcoding step.
We did the same in the past with IMX50 MXF Op1a format with ffmpeg. -> now
the ffmpeg made IMX50 MXF (Op1a) is now an MXF witch is completly standard
compliant and that is a BIG THING in the broadcasting world.
I mean: Now you can generate an MXFfile for professional needs with an open
source tool (!). How many MXFs from FinalCut, Premiere, Resolve,... do you
know which meet the MXF Standard ST377 completely without a problem?
Due to the fact that FFMPEG is not a blackbox and the developers can be
asked to improve this or that, or hinted to a bug because they have not
time to test everything, we can help to improve ffmpeg, like I am trying it
For my personal opinion FFmpeg has the most potential of all transcoders in
Just my 5 cent.
Am Mo., 12. Nov. 2018 um 11:07 Uhr schrieb Martin Vignali <
martin.vignali at gmail.com>:
> I think this report is interesting.
> Creating file for broadcast delivery, is not just about having a file which
> play or doesn't play
> It's mainly about passing Quality Control.
> Even if a file can be play in most of software, if it doesn't pass
> broadcaster QC, it will be reject.
> In my use i always remux MXF generate by ffmpeg using bmxtranswrap, to have
> "clean" mxf.
> Mxf is a very complicated format, with very expensive "documentations".
> Reason why, few people can improve it inside ffmpeg.
> As suggested by Marton Balint, some developers (not me), have more chance
> to work on it, with a financial support.
> If you can sponsor it, you can try to contact developper who have recently
> improve the mxfenc.
> @Chris von Görstinger :
> If you remux your file with bmx, does it still show warning in the MXF
> Analyser ?
> If yes, i suggest to create a bug report on trac.
> Ideally, using an ffmpeg generator instead of a file as source.
> ffmpeg-user mailing list
> ffmpeg-user at ffmpeg.org
> To unsubscribe, visit link above, or email
> ffmpeg-user-request at ffmpeg.org with subject "unsubscribe".
More information about the ffmpeg-user