> > We just upgraded an Ubuntu server running automations for the BFI National > Archive from FFmpeg v4.4.2 to FFmpeg v7.1.1, then v8.0. We have HDR Dolby > Vision JPEG2000 MXF files from an external supplier that automations using > FFprobe v4 already partially processed, but which in v7 and v8 are being > rejected with this message (returning exit status 1): > [mxf @ 0xfefa0f7b0600 ] error reading header metadata > > N_10683320_06of20.mxf: Invalid data found when processing input > > FFprobe v4 does raise a couple of warnings (returns exit status 0): > [mxf @ 0x55e53763c840 ] wrapping of stream 0 is unknown > [mxf @ 0x55e53763c840 ] IndexSID 129 segment 0 has invalid IndexExitRate > Our automation scripts capture the exit status 0 as a sign of file > readability/health so the FFppeg upgrade these files are not progressing - > no doubt for good reason. I’d be interested to know more about this failure > please and how we might get them progressing through FFmpeg. I attach > metadata text files from MediaInfo, regular and mediatrace. I'm sorry but > we cannot supply the source files, but happy to extract any other metadata > you may need to aid diagnosis. > > Hi Joanna,
have you already tried running the IMF Package through more format-targeted tools like Photon and ASDCPlib? Did these flag any issues? I'm skeptical about a few all-zero values where I would usually expect a valid UUIDv4 in the verbose header output you have attached to your message. Best regards, Erik _______________________________________________ ffmpeg-user mailing list -- [email protected] To unsubscribe send an email to [email protected]
