Hi,
On Thu, Sep 15, 2016 at 9:32 AM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
>
> On Sep 15, 2016, at 2:45 PM, Ronald S. Bultje wrote:
>
> Hi Vittorio,
>
> On Thu, Sep 15, 2016 at 8:33 AM, Vittorio Giovara <
> vittorio.giov...@gmail.com> wrote:
>
>> I agree we should always be very
> On Sep 15, 2016, at 2:45 PM, Ronald S. Bultje wrote:
>
> Hi Vittorio,
>
>> On Thu, Sep 15, 2016 at 8:33 AM, Vittorio Giovara
>> 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,
Hi Vittorio,
On Thu, Sep 15, 2016 at 8:33 AM, Vittorio Giovara <
vittorio.giov...@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
> wheneve
> Hi, On Wed, Sep 14, 2016 at 5:09 PM, Vittorio Giovara < vittorio.giovara at
> gmail.com> wrote: > This is the assumption that is made in pixel format
> conversion do > throughout the code (in particular swscale and
> vf_colormatrix). > > Signed-off-by: Vittorio Giovara gmail.com> > --- > liba
Hi,
On Wed, Sep 14, 2016 at 5:09 PM, Vittorio Giovara <
vittorio.giov...@gmail.com> wrote:
> This is the assumption that is made in pixel format conversion do
> throughout the code (in particular swscale and vf_colormatrix).
>
> Signed-off-by: Vittorio Giovara
> ---
> libavfilter/vf_colorspace.
This is the assumption that is made in pixel format conversion do
throughout the code (in particular swscale and vf_colormatrix).
Signed-off-by: Vittorio Giovara
---
libavfilter/vf_colorspace.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/libavfilter/vf_colorspace.c b/libavfilter/vf_color
