[FFmpeg-user] Stream copy of mxf format is weird

[Syehoon Kim]

2024년 1월 30일 (화) 오후 7:53, Nicolas Gaullier <nicolas.gaullier at cji.paris>님이 작성:
>
> >De : ffmpeg-user <ffmpeg-user-bounces at ffmpeg.org> De la part de Syehoon Kim
> >
> >I think there is nothing wrong with the original input file.
> Can you check with -c copy, I mean exactly ffmpeg -i input.mxf  -map v -c copy -f framecrc -
> If your input has B frames, you should be able to distinguish the dts and pts columns.
Below is the stdout of ffmpeg -i original.mxf -map v -c copy -f framecrc -:
0,         -1,          2,        1,   672483, 0x8bd399df.03 bitrate=
-0.0kbits/s speed=N/A
0,          0,          0,        1,    68278, 0x151ccf19, F=0x0
0,          1,          1,        1,    94762, 0x93b9fc75, F=0x0
0,          2,          5,        1,   274535, 0x6a5d2af8, F=0x0
0,          3,          3,        1,   128771, 0x247b89da, F=0x0
0,          4,          4,        1,   175939, 0x430aadb2, F=0x0
0,          5,          8,        1,   270016, 0xea154608, F=0x0
0,          6,          6,        1,   192351, 0x2e347924, F=0x0
0,          7,          7,        1,   199322, 0xeaebc0b6, F=0x0
0,          8,         11,        1,   259604, 0x4d57f015, F=0x0
0,          9,          9,        1,   199440, 0x3df86353, F=0x0
0,         10,         10,        1,   203249, 0xedd312f0, F=0x0
0,         11,         14,        1,   255367, 0x49a8fd8c, F=0x0
0,         12,         12,        1,   198382, 0xa4ca616b, F=0x0
0,         13,         13,        1,   193293, 0x1755209c, F=0x0
0,         14,         17,        1,   278686, 0x10a26986
0,         15,         15,        1,   145956, 0xf641c2c3, F=0x0
0,         16,         16,        1,   133157, 0xf9e4753b, F=0x0
0,         17,         20,        1,   243905, 0xf3728bbb, F=0x0
0,         18,         18,        1,   129545, 0x3c7547b0, F=0x0
0,         19,         19,        1,   123770, 0xcae5af54, F=0x0
0,         20,         23,        1,   250163, 0x45a54b5d, F=0x0
0,         21,         21,        1,   127813, 0xc83680c4, F=0x0
0,         22,         22,        1,   127352, 0x59a077c4, F=0x0
0,         23,         26,        1,   245345, 0xdc11da2f, F=0x0
0,         24,         24,        1,   131952, 0xd3b80148, F=0x0
0,         25,         25,        1,   134883, 0x6aa3627c, F=0x0
0,         26,         29,        1,   237893, 0x8b3ee2da, F=0x0
0,         27,         27,        1,   134788, 0x8d4d28c5, F=0x0
0,         28,         28,        1,   133607, 0x3d2db42b, F=0x0
0,         29,         32,        1,   485516, 0x66aa7aee
0,         30,         30,        1,   126395, 0x5863b059, F=0x0
0,         31,         31,        1,   121790, 0xaaf2b8f1, F=0x0
0,         32,         35,        1,   252756, 0x9f802af6, F=0x0
0,         33,         33,        1,   118577, 0x4b280fa6, F=0x0
0,         34,         34,        1,   119502, 0x93c109c5, F=0x0
0,         35,         38,        1,   247543, 0xcea9d0ae, F=0x0
0,         36,         36,        1,   119215, 0x3d100930, F=0x0
0,         37,         37,        1,   117839, 0x8fd807fc, F=0x0

I see nothing wrong. (Please note that the original.mxf consists of B
frames, and I know that the order of dts should be mixed.)

> >Like you said, maybe it is due to the defect of the mxf wrapper.
> >Thank you for notifying about mxf wrapper's timestamp issue.
> >Kim Syehoon
> Well, I was talking about the mxf wrapper in a general manner, not ffmpeg's implementation.
> But anything might happen.
> Can you share a sample of your input (it would be required for trac anyway) ?
Of course I can. Below is the URL from the company(SBS) where I work.
In case it causes an http 500 error, just refresh it.
https://megamail.sbs.co.kr:8443/xmegaAttach/BigFileDown.file?type=attachDown&fileName=Clip0003.MXF&fileIndex=K3YpOVEsvZg5eTu3mmTNF6F52kcPSl68poeFOYkO71k%3D

If you don't like it, maybe I can share it with Google Drive below, or
something.
https://drive.google.com/file/d/14y95vS_tIAO9xtxnFbX-5xh32p1nrADQ/view?usp=sharing

Please check it out.
Sincerely,
Kim Syehoon