Re: [FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf
On 7/10/15, Kieran O'Leary kieran.ole...@irishfilm.ie wrote: Please also provide the mov file. Carl Eugen ___ This is three frames of colour bars, ingested as avid 1:1 10 bit.mxf, exported same as source.mov. https://dl.dropboxusercontent.com/u/3740512/samesource01.mov -- This email has been scanned for spam and malware by The Email Laundry. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user It looks to me both files are 8bit only. The first one with extra stuff added at begining. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf
Kieran O'Leary kieran.oleary at irishfilm.ie writes: I exported the sequence as a same as source quicktime. Please also provide the mov file. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf
On 7/10/15, Kieran O'Leary kieran.ole...@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. -K -- This email has been scanned for spam and malware by The Email Laundry. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf
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. -K -- This email has been scanned for spam and malware by The Email Laundry. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf
Kieran O'Leary kieran.oleary at irishfilm.ie writes:
That scares me! The bitrate looks close to v210
(220Mbps vs 213Mbps), but it's actually 8-bit video?
You can use the following inlined patch to check
for yourself.
PLEASE fix your mailer!
Paul, will you implement a patch for the original sample?
Carl Eugen
diff --git a/libavformat/mxfdec.c b/libavformat/mxfdec.c
index b3c25b7..e623f50 100644
--- a/libavformat/mxfdec.c
+++ b/libavformat/mxfdec.c
@@ -1964,6 +1964,7 @@
st-codec-codec_id = (enum AVCodecID)codec_ul-id;
}
+st-codec-codec_tag = MKTAG('A', 'V', 'u', 'p');
av_log(mxf-fc, AV_LOG_VERBOSE, %s: Universal Label: ,
avcodec_get_name(st-codec-codec_id));
for (k = 0; k 16; k++) {
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf
It looks to me both files are 8bit only. The first one with extra stuff added at begining. ___ That scares me! The bitrate looks close to v210 (220Mbps vs 213Mbps), but it's actually 8-bit video? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf
On 7/10/15, Carl Eugen Hoyos ceho...@ag.or.at wrote: Kieran O'Leary kieran.oleary at irishfilm.ie writes: That scares me! The bitrate looks close to v210 (220Mbps vs 213Mbps), but it's actually 8-bit video? You can use the following inlined patch to check for yourself. PLEASE fix your mailer! Paul, will you implement a patch for the original sample? Nope, its too much broken. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] Framemd5 filter error for atomised Avid 1:10 bit.mxf
-Original Message- From: ffmpeg-user [mailto:ffmpeg-user-boun...@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.ole...@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 ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
