[FFmpeg-trac] #4261(undetermined:new): Systematic artefacts from 10bit Source
FFmpeg
trac at avcodec.org
Fri Apr 17 13:08:12 CEST 2015
#4261: Systematic artefacts from 10bit Source
-------------------------------------+-------------------------------------
Reporter: solidghost | Owner:
Type: defect | Status: new
Priority: normal | Component:
Version: unspecified | undetermined
Keywords: | Resolution:
Blocking: | Blocked By:
Analyzed by developer: 0 | Reproduced by developer: 0
-------------------------------------+-------------------------------------
Comment (by cehoyos):
I tested the following:
{{{
$ ffmpeg -r 0.1 -i Uncompressed_YUV_10_bit_422.mov -qscale 2 -dc 11 -r 25
out.m2v
}}}
{{{
$ ffmpeg -i out.m2v -vf crop=100:100:0:0,scale=1000:1000 -qscale 2
-vframes 1 out.jpg
}}}
{{{
$ ffmpeg -i out.m2v -sws_flags
lanczos+accurate_rnd+full_chroma_int+full_chroma_inp -vf
crop=100:100:0:0,scale=1000:1000 -qscale 2 -vframes 1 out2.jpg
}}}
And I have difficulties seeing systematic artefacts visible in out.jpg and
even less in out2.jpg indicating you are reporting a scaler issue in your
decoding application.
Additionally, I tested:
{{{
$ ffmpeg -i out.m2v -f xv -vf
crop=100:100:0:0,scale=1000:1000,format=yuyv422 -
}}}
And the output looks essentially gray here.
(I think) I also tested with my hardware scaler:
{{{
$ ffmpeg -i out.m2v -f xv -vf crop=100:100:0:0,format=yuyv422 -
}}}
Enlarging the small window to my hd1080 screen shows no artefacts here.
I also tested the following but I don't think ffplay is a good application
for this test (it doesn't support yuv422 and depends on an external
library):
{{{
$ ffplay out.m2v -vf crop=100:100:0:0,scale=1000:1000
}}}
--
Ticket URL: <https://trac.ffmpeg.org/ticket/4261#comment:15>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list