MpegMapperSegmented::CalcDiskToDisplayOffset (XDCAM AVID)

[FranceBB]

Hi,
with the latest development version of ffmpeg (ffmpeg-20180611-8c20ea8), it seems that some files are not correctly muxed in .MXF.
I’ve used the following command line:

 C:\Encoding\ffmpeg.exe -i "%%~nxF" -pix_fmt yuv422p -vcodec mpeg2video -s 1920:1080 -aspect 16:9 -vf setfield=tff -flags +ildct+ilme -r 25 -b:v 50000k -minrate 50000k -maxrate 50000k -bufsize 36408333 -acodec pcm_s24le -ar 48000 -g 12 -bf 2 -profile:v 0 -level:v 2 -color_range 1 -color_primaries 1 -color_trc 1 -colorspace 1 -f mxf "C:\Encoding\%%~nF encoded.mxf"

The original video is an H.264 profile High, level 5.1, ref1, 3840x2160, progressive 8bit muxed in an .mp4. Nothing weird.
The encoding starts but at the end I get:



The encoded video plays fine on VLC, MPC-HP and PotPlayer, however if I import it into AVID Media Composer or if I link it it displays an error. If I try to transcode the original file in AVID, it works flawlessly, which is weird.
I've also tried to pipe Avisynth to ffmpeg and encode, but it didin't solve the problem:

video=FFVideoSource("test.mp4")
audiook=FFAudioSource("test.mp4")
audio=MergeChannels(audiook, audiook, audiook, audiook)
AudioDub(video, audio)

ResampleAudio(48000)
Normalize(0.20)
ConvertAudioTo24bit()
Limiter(min_luma=16, max_luma=235, min_chroma=16, max_chroma=240)

ConvertFPS(50)
Spline64ResizeMT(1920, 1080)
assumeTFF()
separatefields()
selectevery(4,0,3)
weave()
Converttoyv16(interlaced=true)

Even after using Avisynth and encoding with ffmpeg, AVID prompted me to this error:



This is not the first time I have to deal with this. It's odd.
I managed to encode it already, but I decided to report this here 'cause it's odd.

Original File + Encoded File: https://we.tl/A9Cgvr79zn

Is it ffmpeg? Is it AVID? Who's guilty?

[kolak]

It's rather ffmpeg. It's not a "precise" tool and sometimes it doesn't follow some specs etc. AVID from other hand requires things to be precise, sometimes even too much
This info about missing frame doesn't look "good" in ffmpeg.

[FranceBB]

Originally Posted by kolak

It's rather ffmpeg. It's not a "precise" tool and sometimes it doesn't follow some specs etc. AVID from other hand requires things to be precise, sometimes even too much
This info about missing frame doesn't look "good" in ffmpeg.

Yep... Later on I found out that it's ffmpeg... Remuxing the MXF with BBC BMX Transwrap and solves the problem most of the time, so it's definitely ffmpeg.
It's sad 'cause the only other open source encoder capable to encode in MPEG-2 that I know is x262, but it does have its own issues...
Last but not least, there's ffmbc, but it's not the panacea to each and every issue either...

[kolak]

Is ffmbc maintained?
Looks like binaries are so outdated.

[FranceBB]

Originally Posted by kolak

Is ffmbc maintained?
Looks like binaries are so outdated.

It's not, that's why I was using ffmpeg.
Anyway, since I only need an encoder as I pipe the A/V stream from Avisynth, I was trying ffmbc as well 'cause even if it's outdated and it doesn't have new decoders, I only need to encode an uncompressed audio/video stream.
Besides, I don't think MPEG-2 encoders are updated frequently (or at all) nowadays...

[richardpl]

This is build from 2018, so it is not latest.