Re: [FFmpeg-devel] [PATCH] Fix chroma positioning for 4:2:0 pixel format

2017-02-08 Thread Andy Furniss
Andy Furniss wrote: Another possible issue which I haven't fully investigated = This doesn't obey setfield, which makes me think that maybe it's only working by luck on tff input. Ugh, ignore that bit as I don't think it should matter as long as the filter always sees weaved frames. A quick

Re: [FFmpeg-devel] [PATCH] Fix chroma positioning for 4:2:0 pixel format

2017-02-08 Thread Andy Furniss
Andy Furniss wrote: Michael Niedermayer wrote: On Mon, Feb 06, 2017 at 05:14:14PM +0200, Maksym Veremeyenko wrote: Hi, Attached patch fixes chroma positioning during scaling interlaced 4:2:0. On a first iteration default context value been overwritten by new value and not been update on next

Re: [FFmpeg-devel] [PATCH] Fix chroma positioning for 4:2:0 pixel format

2017-02-08 Thread Andy Furniss
Michael Niedermayer wrote: On Mon, Feb 06, 2017 at 05:14:14PM +0200, Maksym Veremeyenko wrote: Hi, Attached patch fixes chroma positioning during scaling interlaced 4:2:0. On a first iteration default context value been overwritten by new value and not been update on next iterations for fields

Re: [FFmpeg-devel] [PATCH] Fix chroma positioning for 4:2:0 pixel format

2017-02-07 Thread Michael Niedermayer
On Mon, Feb 06, 2017 at 05:14:14PM +0200, Maksym Veremeyenko wrote: > Hi, > > Attached patch fixes chroma positioning during scaling interlaced 4:2:0. > > On a first iteration default context value been overwritten by new > value and not been update on next iterations for fields. This mean > that

[FFmpeg-devel] [PATCH] Fix chroma positioning for 4:2:0 pixel format

2017-02-06 Thread Maksym Veremeyenko
Hi, Attached patch fixes chroma positioning during scaling interlaced 4:2:0. On a first iteration default context value been overwritten by new value and not been update on next iterations for fields. This mean that vertical chroma position remain 128 for field#0 and field#1 instead of *64* a