[FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf

Kieran O'Leary kieran.oleary at irishfilm.ie
Fri Jul 10 17:01:13 CEST 2015

-----Original Message-----
From: ffmpeg-user [mailto:ffmpeg-user-bounces at ffmpeg.org] On Behalf Of Paul B Mahol
Sent: 10 July 2015 15:23
To: FFmpeg user questions
Subject: Re: [FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf

On 7/10/15, Kieran O'Leary <kieran.oleary at irishfilm.ie> wrote:
>> framemd5 won't help you determine 'how much' visual difference there 
>> is between an exported file and a reference file. Depending on how 
>> you run it, framemd5 would only confirm if the two files decode to 
>> the same raw frame or different ones, it's a yes/no answer and not a 
>> 'how much'. I suggest sending both streams as input to the psnr or 
>> ssim filters which are better able to quantify visual difference.
>>Also ffmpeg is not detecting the pixel format of your mxf file, you 
>>may  have to declare the pixel format before the input.
> Dave Rice
> --
> Hi Dave,
> Thanks for that. I will set the pixel format later and see if that 
> gets it working.
> Re the framemd5, I should have been more clear. I wanted to use the 
> framemd5s to prove that the video stream was altered when transcoding 
> from
> 1:1 10bit to v210. I realise that it would just give a yes or no 
> answer to this question. I honestly didn't have a clue how to compare 
> them after that and see how much alteration occurs. Thanks yet again 
> for your invaluable help.

AVup is just packed uyvy422.
But something is not correct as there is greenish thing on top, also the dimensions doesnt seems to be correct.


I'm getting out of my depth here, but isn't uyvy422 8-bit? Would avup 10 bit be uyvy42210? I'm having a little difficulty with the term "packed". Are you referring to the packed/planar distinction? And yes, the 720*592 dimension seems odd. Seems to pop up here as well: https://trac.ffmpeg.org/ticket/162

More information about the ffmpeg-user mailing list