[XviD-devel] [BUG?] intra meaning

[Edouard Gomez]

--OXfL5xGRrasGEqWY
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Dirk Knop (dknop@gwdg.de) wrote:

> Gom, a little childish we are today, aren't we?

The log  was not  intended to upset  you, it  was supposed to  show your
point of view with your explaination  to me. Sorry if that annoys you, i
thought it was logical to describe the "voodoo" that messed up the code.

I'm not a flame starter, you should know that.=20

> we decided to report some frame types - in the stats they look like this =
now
> #define NNSTATS_KEYFRAME    (1<<31)
> #define NNSTATS_BFRAME        (1<<30)
> #define NNSTATS_SKIPFRAME    (1<<29)
> #define NNSTATS_PADFRAME    (1<<28)
> #define NNSTATS_DELAYFRAME    (1<<27)

Ok why not ? this is not core business.

> These frame types are indicated by frmae.intra (pFrame.intra in core):
>=20
> 0: pframe
> 1: iframe
> 2: bframe
> 3: skipframe (NVOP)
> 4: padframe (dunno what that was anymore %) )
> 5: delayframe (those 1byte frames for queing up bframes).
> [...]

Then now the proposed solutions:

1) Why don't  you modify vfw  so it looks  at intra doing =3D=3D  instead of
   some & ?

Or

2) Let's find a real free slot without any signification in vfw.=20
   (then just give me the value)

Tell me which one is good for you and this bug is closed. Period.

--=20
Edouard Gomez

--OXfL5xGRrasGEqWY
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+LZaRR5dTYz5sWMcRAt+cAJ0cvY+ipUrB7u8QVTDSTzhSWlqhCwCgjLI3
UP0d63Jw6a/rs5Bsla7flWM=
=bqO6
-----END PGP SIGNATURE-----

--OXfL5xGRrasGEqWY--