On Wed, 12 Mar 2014 12:06:13 +0100 Luca Barbato <[email protected]> wrote:
> On 12/03/14 11:46, Vittorio Giovara wrote: > > On Wed, Mar 12, 2014 at 8:12 AM, Luca Barbato <[email protected]> wrote: > >> On 12/03/14 07:48, Vittorio Giovara wrote: > >>> --- > >>> As noted by wm4 the full scale formats have been deprecated for ages but > >>> the entries of the enum have not (which this patch takes care of). > >>> > >>> Also I'm a bit puzzled that pixel formats are in lavu while color space > >>> and > >>> color range are in lavc. Would it be better to move them all to lavu? > >>> > >>> Another point, (again AFAIU) pixel format/range/space seem to be more a > >>> frame > >>> property, instead of a context one (kinda like interlacing). Would it > >>> make sense > >>> to move everything there? The API I would envision would be an entry in > >>> AVFrame > >>> and an AVFrameSideData for the color range and spaces. > >>> > >> > >> I think swscale is the reason... > >> > > > > Can you explain more in detail? > > > > The swscaler and filters using it iirc do not really support some/all of > the properties you mentioned. Some video filters might abuse the existence of the J formats to signal that they can or can not take limited/full range input. libswscale should handle the limited range flag correctly by now, but it's possible that it still doesn't work correctly for some format combinations. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
