This matter has already been told to Takehiro, and he said
he will commit a new code later.
This is an information.


Add debug code into encodeSideInfo2() in bitstream.c as
follows.

----
+         DEBUGF("%d %d\n", (int)gi->region0_count,
+                           (int)gi->region1_count);
          CRC_writeheader(gfc,gi->region0_count, 4,&crc);
          CRC_writeheader(gfc,gi->region1_count, 3,&crc);
----

Under some conditions, you will see some frames have -1 as
the value of region0_count or region1_count.
These values are invalid obviously.

The values in the bitstream would be 15 and 7. These values may
cause awful result, but in many case, it seems hard to recognize
the corrupted result.

I think this bug has been there in three or four months.
I want to know how to avoid this bug temporarily.


Iwasa Kazmi
--
MP3 ENCODER mailing list ( http://geek.rcc.se/mp3encoder/ )

Reply via email to