Xesdeeni
23rd April 2003, 19:18
Someone using my WSOLA port (http://www.geocities.com/xesdeeni2001/) (speeds up or slows down audio without shifting the pitch) has encountered a problem with the WAV file output from DVD2AVI. I've verified this myself with DVD2AVI 1.76. It appears that the WAV file chunk sizes are not correct, and this trips up the checking that WSOLA does.
In the example I just tried, I created a 314,663,164 byte WAV file from a VOB. The initial size, located in bytes 4-7, should indicate the size of the entire file minus 8 (for the 'RIFF' header and the size of the size field itself), or 0x12C160FC (314,663,156). But the header indicates 0x12C086D4, saying the file is only 314,607,316 bytes long.
Then the 'data' chunk size, which starts at offset 0x24, indicates a size of 0x12C086B0 (314,607,280), which is shorter that the remainder of the file. This should only happen if another chunk starts after the 'data' chunk. But, when you look at file offset 0x20 + 0x8 + 0x12C086B0 = 0x12C086D8, there are just a bunch of null bytes with no more chunks in sight.
Has anyone else seen this issue? Has this been addressed in other DVD2AVI versions?
Xesdeeni
In the example I just tried, I created a 314,663,164 byte WAV file from a VOB. The initial size, located in bytes 4-7, should indicate the size of the entire file minus 8 (for the 'RIFF' header and the size of the size field itself), or 0x12C160FC (314,663,156). But the header indicates 0x12C086D4, saying the file is only 314,607,316 bytes long.
Then the 'data' chunk size, which starts at offset 0x24, indicates a size of 0x12C086B0 (314,607,280), which is shorter that the remainder of the file. This should only happen if another chunk starts after the 'data' chunk. But, when you look at file offset 0x20 + 0x8 + 0x12C086B0 = 0x12C086D8, there are just a bunch of null bytes with no more chunks in sight.
Has anyone else seen this issue? Has this been addressed in other DVD2AVI versions?
Xesdeeni