hamedramzi / ffmbc

Automatically exported from code.google.com/p/ffmbc
0 stars 0 forks source link

10bit DNxHD decoding bug #60

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Decoding AVID DNxHD MFX file (or QT) into v210 AVI (or MOV) will introduce 
artefact in high contrast areas.
There is aliasing around white letters on attached sample.

Original issue reported on code.google.com by andrew.k...@gmail.com on 7 Oct 2011 at 3:13

Attachments:

GoogleCodeExporter commented 9 years ago
Closer look reveals that this is a serious issue. Quality is affected a lot- my 
example is not the best- there are much more pronounce problems- it affects 
even color bars.

Original comment by andrew.k...@gmail.com on 8 Oct 2011 at 12:09

GoogleCodeExporter commented 9 years ago
Without any sample I cannot fix

Original comment by baptiste...@gmail.com on 13 Oct 2011 at 12:09

GoogleCodeExporter commented 9 years ago
I will provide sample.

Original comment by andrew.k...@gmail.com on 13 Oct 2011 at 9:48

GoogleCodeExporter commented 9 years ago
Here are bars- decode to v210 (with simple -vcodec v210 command) and decode by 
AVID QT decoder and compare. There is aliasing, double lining on bars borders.

Original comment by andrew.k...@gmail.com on 14 Oct 2011 at 8:57

Attachments:

GoogleCodeExporter commented 9 years ago
Ok, thanks a lot for the sample, I'll fix this in the next rc.

Original comment by baptiste...@gmail.com on 14 Oct 2011 at 3:25

GoogleCodeExporter commented 9 years ago
Could you please check the issue with rc4 ?

Original comment by baptiste...@gmail.com on 27 Oct 2011 at 3:44

GoogleCodeExporter commented 9 years ago
Will do

Original comment by andrew.k...@gmail.com on 27 Oct 2011 at 9:14

GoogleCodeExporter commented 9 years ago
I had a quick look and it doesn't look like it's fixed at all.
I will confirm.

Original comment by andrew.k...@gmail.com on 29 Oct 2011 at 12:47

GoogleCodeExporter commented 9 years ago
Humm, crap, can you please confirm you have the latest tarball ?

Original comment by baptiste...@gmail.com on 29 Oct 2011 at 8:48

GoogleCodeExporter commented 9 years ago
Yes- rc4.
It looks a bit different than older version, but still not good. Same problem 
applies to ffmpeg, so there has to be bug somewhere in the decoder code.

Original comment by andrew.k...@gmail.com on 30 Oct 2011 at 2:18

GoogleCodeExporter commented 9 years ago
Hummm, weird, I don't see anything weird here,
did you check the sha1 of your rc4 tarball ?

Original comment by baptiste...@gmail.com on 1 Nov 2011 at 1:35

GoogleCodeExporter commented 9 years ago
I'm using exe from here:

http://forum.doom9.org/showthread.php?t=162615

Here is QT v. FFMBC

Original comment by andrew.k...@gmail.com on 1 Nov 2011 at 1:19

Attachments:

GoogleCodeExporter commented 9 years ago
Ah well, these binaries are unsupported.
Compile yourself with the latest tarball and re-open the ticket if you still 
experience the issue.

Original comment by baptiste...@gmail.com on 1 Nov 2011 at 6:27

GoogleCodeExporter commented 9 years ago
What does it mean unsupported?

Where can I find official compiling procedure?

Original comment by andrew.k...@gmail.com on 1 Nov 2011 at 9:32

GoogleCodeExporter commented 9 years ago
Compiled it by myself from latest source and problem seams to be gone. Will 
check for sure tomorrow. Thanks!

Original comment by andrew.k...@gmail.com on 2 Nov 2011 at 12:12

GoogleCodeExporter commented 9 years ago
Ah, great thanks for the report !

Original comment by baptiste...@gmail.com on 2 Nov 2011 at 1:00

GoogleCodeExporter commented 9 years ago
Confirmed- issue is fixed in latest rc4. There is some tiny difference on 
chroma compared to renders from AE, but I think it's due to AE going through 
RGB. Probably ffmbc is more accurate, not sure.

Original comment by andrew.k...@gmail.com on 2 Nov 2011 at 11:54