Re: [FFmpeg-devel] Default color range encoding in Avid ACLR tags embeedded in QuickTime .movs

2015-02-10 Thread Michael Niedermayer
On Tue, Feb 10, 2015 at 10:45:46AM +, Kevin Wheatley wrote: > On Tue, Feb 10, 2015 at 10:34 AM, Michael Niedermayer > wrote: > > if theres no way to store unknown range then your suggestion sounds > > reasonable, can you send a patch? > > I'm not aware of a value to specify in the ACLR atom

Re: [FFmpeg-devel] Default color range encoding in Avid ACLR tags embeedded in QuickTime .movs

2015-02-10 Thread Kevin Wheatley
On Tue, Feb 10, 2015 at 10:34 AM, Michael Niedermayer wrote: > if theres no way to store unknown range then your suggestion sounds > reasonable, can you send a patch? I'm not aware of a value to specify in the ACLR atom for unspecified - I could guess at a value of 0 but that is pure speculation,

Re: [FFmpeg-devel] Default color range encoding in Avid ACLR tags embeedded in QuickTime .movs

2015-02-10 Thread Michael Niedermayer
On Tue, Feb 10, 2015 at 09:17:34AM +, Kevin Wheatley wrote: > Hi, > > Just looking through the FATE tests and the changes I wanted to make > on reading ACLR atoms and I came across an issue. I wondered what the > expected encoding range is for Y'CbCr during the FATE test runs as > well as more

[FFmpeg-devel] Default color range encoding in Avid ACLR tags embeedded in QuickTime .movs

2015-02-10 Thread Kevin Wheatley
Hi, Just looking through the FATE tests and the changes I wanted to make on reading ACLR atoms and I came across an issue. I wondered what the expected encoding range is for Y'CbCr during the FATE test runs as well as more generally. It would appear that the assumption that the range should be AV