[XviD-devel] encoding xvid (2)

Ricardo Ferreira ricardo-c-ferreira at ptinovacao.pt
Thu Sep 11 20:17:44 CEST 2003


Although the documentation (xvid-decoding.txt) points to stride as the
number of bytes in each row, according to my experience with XVID, you have
to use as the number of pixels in each row => stride=width.

Ricardo Ferreira
ricardo-c-ferreira at ptinovacao.pt
PT Inovação

> -----Original Message-----
> From: Christoph Nägeli [mailto:chn at kbw.ch] 
> Sent: quinta-feira, 11 de Setembro de 2003 13:30
> To: xvid-devel at xvid.org
> Subject: Re: [XviD-devel] encoding xvid (2)
> 
> 
> Hello,
> 
> I'm not quite sure about the stride value. The documentation 
> 'xvid-decoding.txt' says thats the difference between the memory 
> address of the first pixel and the address of the first pixel of the 
> next row is the stride value. The next sentence is when the image is 
> one big block, then 'stride=width'.
> 
> So I think I have to use 'stride=width', but the memory difference 
> would be in XVID_CSP_RGB32 would be 4 times the width. I tried both, 
> 'stride=width' gives the strange image and with 'stride= 4*width' my 
> app crashes.
> 
> I think there is no stride value for encoding, isn't it?
> 
> Regards
> Christoph Nägeli
> 
> On Donnerstag, September 11, 2003, at 10:18  Uhr, Christoph Lampert 
> wrote:
> 
> >
> > Hi,
> >
> > your description sounds like you used the wrong "stride" value for
> > decoding (or encoding). Maybe you didn't use one at all?
> >
> >
> 
> 
> _______________________________________________
> XviD-devel mailing list
> XviD-devel at xvid.org
> http://list.xvid.org/mailman/listinfo/xvid-devel
> 



More information about the XviD-devel mailing list