Quote:
Originally Posted by madshi
That documentation is outdated. The WAV file created by eac3to is perfectly fine. It just uses a newer revision of the WAV file format, which is not supported by some applications. If you run into trouble you can use the eac3to "-simple" switch which will make eac3to output "old style" WAV files (with Compression code 0x0001). Please note that old style WAV files do not have a field to store the channel configuration of the channels. So for multichannel data, using the new file format revision is recommended. See also here: http://www.microsoft.com/whdc/device...ultichaud.mspx |
Thanks for your explanation, I noticed there are some
Extra format bytes in the header present. It's also nice that there is
-simple option switch prepared already. Unfortunately its existence is well hidden in the documentation (usage help). Could you please make it visible in further releases (and maybe also other undocumented switches which there possibly are)?
:::EDIT:::
I do not want to sound rude, yet I still think that the Compression code should be set to
0x0001.This is standard value meaning
Uncompressed PCM. It has nothing to do with number of channels, sample rate, bit depth of samples, or mapping of the channels in case of WAVE_FORMAT_EXTENSIBLE enhancements. Therefore I see no reason why you set it to 0xFFFE for standard uncompressed PCM Windows WAV file, it just doesn't make sense.
:::EDIT 2:::
Sorry, now I found that 0xFFFE designates that WAVE_FORMAT_EXTENSIBLE additions. Sorry for being such dumb ass.
