Doom9's Forum - View Single Post - eac3to

kypec · 14th February 2009, 07:22

Hello madshi, first I want to thank you for such an excellent tool.
I use it only for very simple decoding of AC3 (within VOB) to WAV, however, there is some bug in the output header of WAV file occuring.
According to this RIFF WAVE specification details the Compression code in Format chunk should be 1 (0x0001) for standard uncompressed PCM.
When I run eac3to something.vob something.wav -libav -down16 the resulting wav file has Compression code set to -1 (0xFFFE) which is wrong. All other attributes are just fine (Number of channels=2, Sample rate=48000, Average bytes per second=192000, Block align=4, Bits per sample=16). Consequently, some apps like normalize for instance refuse to work with such WAV files. Is this related to libav or is it your WAV output writer which produces such corrupted header values?

14th February 2009, 07:22	#8238 \| Link
kypec User of free A/V tools Join Date: Jul 2006 Location: SK Posts: 826	Hello madshi, first I want to thank you for such an excellent tool. I use it only for very simple decoding of AC3 (within VOB) to WAV, however, there is some bug in the output header of WAV file occuring. According to this RIFF WAVE specification details the Compression code in Format chunk should be 1 (0x0001) for standard uncompressed PCM. When I run eac3to something.vob something.wav -libav -down16 the resulting wav file has Compression code set to -1 (0xFFFE) which is wrong. All other attributes are just fine (Number of channels=2, Sample rate=48000, Average bytes per second=192000, Block align=4, Bits per sample=16). Consequently, some apps like normalize for instance refuse to work with such WAV files. Is this related to libav or is it your WAV output writer which produces such corrupted header values?