Some encoded MXF files not compatible with Avid consolidating

[3dsasha]

Hello! I made simple workflow XDCAM-HD -> Folder just for convert multiple sources to edit with Avid Media Composer. It works great but today I found some types of files that not encoded correctly for Avid consolidate process:

avid.JPG (88.81 KiB) Viewed 8471 times

I found at Avid site this old article:

The editing application uses source index tables now to ensure that this media is wrapped correctly. If the media is wrapped correctly, the media will play back correctly. If the media is corrupt, the media will not playback and you will receive an “Exception: Failed to convert display to disk order” error.

I changed wrapper in processor to MXF (BMX) and mov, interlace, audio tracks , but result is same.
These encoded MXF files can be played by viewers, can be linked, viewed and imported by Avid MC, but can not be consolidated. The CONSOLIDATE process in Avid (as I think) is fast unwrapping tracks from source MXF to MXF OP-Atom to avid media folder. And here is the problem.
Example of source file to encode is attached https://drive.google.com/file/d/1POn7RS ... sp=sharing
May be it is not a bug, and somebody advice me how to do?
Many thanks!!

[emcodem]

Hey 3dshasha,

OK this is interesting and disturbing at the same time. In this case, ffmpeg seems really to have produced a defective MXF index just like Grassvalley K2 servers did/do. I was not aware that this actually can happen. But at the same time as we have many avid users here, it is kind of unbelieveable that this didnt happen to anyone else. Do you have kind of a old/special version of Avid MC or recently updated?
If this is about what i believe it is, then you should have this in about 1 of 15 files at least, and it depends on the duration of the file.

But the BMX stuff does not seem to have any MXF structural errors.

Anyway, using your input file, i created 2 versions to test for you, could you please try both and come back here with the results?

https://drive.google.com/drive/folders/ ... WbOuajBfOk

[3dsasha]

Thanks for reply! I tried bmx.mxf - error was the same with "media index table". But cgop.mxf was consolidated fine! I did not write correct previous post. My encoded mxf was available to link and play in Avid but cannot be consolidated and imported. And if I play that in Avid to 33:04 (2 frames to end) - the same error is showing up! We have 2018.12.10 perpetual license Avid and up-to-date last 2020.12 version. Both shows the same results and errors. Different PCs.
cgop.mxf is good!

[emcodem]

uhm ok.. still disturbing hehe

i uploaded one more file, could you try this one too please?

[3dsasha]

Sony_reference.mxf is processed fine!

[emcodem]

ok, i'll create one more file, takes 30 minutes

[emcodem]

Done, please check out the 3 new files when you find the time

[3dsasha]

File duration-2 is good (33:04). Others gives errors. Maybe source files are corrupted/wrong? As I see most my problem files were downloaded from telegram but not all of them. May be messenger does something wrong with files?

[emcodem]

Great, thanks for testing this out!

No the source file is not really relevant here, i suspect you will have the same error whenever you produce exactly this duration. Most likely also when you produce the same duration minus 12xN frames, where N is 1 to duration/12. - so i suspect that 1 of 12 encoded files should typically suffer from this error.

We definitely face some ffmpeg related problem here, there is no question about that. It produces Open-GOP and the last frames obviously cannot be decoded, so the Duration of the MXF header should be reduced by those frames (so called rollout).
@momocampo knows how to workaround in MC, i am sure he will post his opinion soon.

Meanwhile, i have to investigate the problem a little bit deeper and decide if i want to fix the problem inside ffmpeg or at least discuss it with the ffmpeg guys.
Also we need to have an internal talk about possible solutions, e.g. use closed GOP.

I'll get back when i know more.

[momocampo]

Hello 3dSasha,
Yes, I have this problem regularly unfortunately. Go to the end of your file in Avid MC and you will see the message (screencapture).
As @encodem said, there is a "structural" issue with this kind of files. While waiting to find out the problem, here is a simple workaround :

Link your file in a bin, double-click to load it into the player. Mark your clip (in-out) and move back your output point from 2 frames (you select your entire master clip except the 2 last frames, don't worry these 2 last frames aren't in your original file). Make a subclip with your selection and consolidate it WITHOUT any handle !
Hope you understood.

CHeers ,)
B.