search for: xstride

...data in common, IMHO.. >You'll also note the specification says nothing about packed formats. >Packed vs. planar is completely orthogonal to the rest of the issues, >and only arises when storing the raw pixel data directly. Supporting >either is relatively easy in software with an xstride/ystride for each >component, so there is hardly a reason not to (Theora doesn't because it >greatly simplifies several inner loops to be able to assume xstride=1; a >raw codec should not be as affected by such an issue). And there is >definitely a reason _to_ support them in a raw f...

On Tue, Nov 08, 2005 at 09:36:52PM +0800, illiminable wrote: > > Then there's YUY2 which is interleaved Y0 U0 Y1 V0 Y2 U1 Y3 V1, and YVYU > (Y0 V0 Y1 U0 Y2 V1 Y3 U1), and UYVY (U0 Y0 V0 Y1 U0 Y2 V0 Y3)... and then > there's AYUV, which has a 4th alpha channel. We will only be doing [A]YUV ordered planar encoding, no other order, not packed using one of several methods.

On Tue, Nov 08, 2005 at 09:36:52PM +0800, illiminable wrote: > > Then there's YUY2 which is interleaved Y0 U0 Y1 V0 Y2 U1 Y3 V1, and YVYU > (Y0 V0 Y1 U0 Y2 V1 Y3 U1), and UYVY (U0 Y0 V0 Y1 U0 Y2 V0 Y3)... and then > there's AYUV, which has a 4th alpha channel. We will only be doing [A]YUV ordered planar encoding, no other order, not packed using one of several methods.

...n variables, versions, etc is used to detirmine compatability. The fields we're talking about will go into packet0, so that a list of which plugins can accept it can be easily generated. > Agreed.. Though it's worth pointing out that it's possible to have > images wthere the xstride/ystride between components is not constant > (endian issues, UVYY packings, etc). How to handle interlacing is > another problem, if you're trying to make a super generic format. A line > has to be drawn somewhere, and it's hard to say where that is. Interlace certainly needs t...