[FFmpeg-devel] [PATCH 1/2] vf_colorspace: Interpret unspecified color range as limited range
Ronald S. Bultje
rsbultje at gmail.com
Thu Sep 15 16:38:06 EEST 2016
On Thu, Sep 15, 2016 at 9:32 AM, Vittorio Giovara <
vittorio.giovara at gmail.com> wrote:
> On Sep 15, 2016, at 2:45 PM, Ronald S. Bultje <rsbultje at gmail.com> wrote:
> Hi Vittorio,
> On Thu, Sep 15, 2016 at 8:33 AM, Vittorio Giovara <
> vittorio.giovara at gmail.com> wrote:
>> I agree we should always be very very careful about automatic
>> assignments, although this one seems pretty safe.
>> I don't think it's necessary, but if you prefer I can add a warning
>> whenever range is not specified (even though it might trigger a few false
> Which false positive are you afraid of?
> By "false positive" I mean only the fact that it might needlessly print a
> warning, and the user might be confused by it.
Right, but only because the range was not set. I'd like to get to the ideal
end situation where we encourage everyone (users, decoders, etc.) to always
explicitly set the range.
Aside, is it correct that if the pix_fmt was set to a YUVJ4xx variant,
range is automatically set to _JPEG?
More information about the ffmpeg-devel