On Fri, Apr 5, 2013 at 2:24 PM, Nicolas BERTRAND <[email protected]>wrote:
> Le 05/04/2013 14:22, Hendrik Leppkes a écrit : > >> On Fri, Apr 5, 2013 at 2:18 PM, Nicolas BERTRAND <[email protected] >> >**wrote: >> >> Le 05/04/2013 02:06, Kieran Kunhya a écrit : >>> >>> + AV_PIX_FMT_XYZ12LE, ///< packed XYZ 4:4:4, 36 bpp, (msb) 12X, >>> >>>> 12Y, 12Z (lsb), the 2-bytes value for each X/Y/Z is stored as little >>>>> endian, 4 lower bits set to 0 >>>>> + AV_PIX_FMT_XYZ12BE, ///< packed XYZ 4:4:4, 36 bpp, (msb) 12X, >>>>> 12Y, 12Z (lsb), the 2-bytes value for each X/Y/Z is stored as big >>>>> endian, 4 >>>>> lower bits set to 0 >>>>> >>>>> >>>> Why do you set the lower bits to zero? The rest of libav has the upper >>>> bits set to zero for high bit depth formats. >>>> >>>> Well because its specified like that in section3.2.2.2 of DCI spec. >>>> >>> http://dcimovies.com/****specification/DCI_DCSS_v12_**<http://dcimovies.com/**specification/DCI_DCSS_v12_**> >>> with_errata_2012-1010.pdf<http**://dcimovies.com/** >>> specification/DCI_DCSS_v12_**with_errata_2012-1010.pdf<http://dcimovies.com/specification/DCI_DCSS_v12_with_errata_2012-1010.pdf> >>> > >>> >>> >>> >>> Should ideally still be consistent with the other libav pixel formats, i >> would think. >> > > But what about "compatibilty" with others apps? it they expeceted XYZ in > DCI format? > > Consistency between all the pixel formats seems more important to me, otherwise devs trying to support all of them are in for a surprise if the position of the data changes randomly between formats. _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
