#9860: yuvj420p spam
--------------------------------------+-----------------------------------
Reporter: Jacky Koning | Owner: (none)
Type: enhancement | Status: open
Priority: wish | Component: swscale
Version: git-master | Resolution:
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
--------------------------------------+-----------------------------------
Changes (by Balling):
* component: ffmpeg => swscale
Comment:
Replying to [comment:9 Jacky Koning]:
> https://trac.ffmpeg.org/ticket/6088 This one? I did a google search like
"deprecated pixel format used, make sure you did set range correctly
site:trac.ffmpeg.org"
No, some other one that was talking about many many lines instead of one,
I common some up with it. There are a lot of such tickets, it is won't fix
for jpeg, since that one always uses full range, but we did not migrate
jpeg decoder to new API yet and it is a real problem, e.g., the use of old
API can put BT.709 instead of BT.601 yuv inside and it also does not
change the chroma siting from left or top-left to jpeg's center. (See my
own bug #9693.) That is also why we cannot try apply Paul's patchset that
removes long time ago deprecated yuvj* formats.
I mean your issue is simple to fix: just decrease the visability to -v
trace for this line.
--
Ticket URL: <https://trac.ffmpeg.org/ticket/9860#comment:10>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
FFmpeg-trac@avcodec.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac
To unsubscribe, visit link above, or email
ffmpeg-trac-requ...@ffmpeg.org with subject "unsubscribe".
