Multichannel Channel Order Options

[xslig]

I've found that the option "--channel-order=" only works with raw PCM.

I had a 5 channel WAV (FL,FR,LFE,BL,BR) that I encoded. I then used "wvunpack -s foo.wv" and got back "channels: 5 (unassigned speakers)"

I wanted to have the channels assigned so

CODE

wavpack --channel-order=FL,FR,LFE,BL,BR foo.wav

and got back "this WAV file already has channel order information!"

I converted the WAV to raw PCM then

CODE

wavpack --channel-order=FL,FR,LFE,BL,BR foo.raw --raw-pcm=48000,24,5

which worked.

Is the option "--channel-order=" supposed to work like this?
I would think it's counter-intuitive that one couldn't change the channel order of a WAV file with the "--channel-order=" option.

---
Edit:

It was actually a WAVEX if that makes any difference.

This post has been edited by xslig: Dec 12 2011, 22:37

[lvqcl]

http://msdn.microsoft.com/en-us/windows/ha.../gg463006#ECMAC :

Having nChannels exceed the number of bits set in dwChannelMask can produce inconsistent results and should be avoided if possible.

http://msdn.microsoft.com/en-us/library/wi...2(v=vs.85).aspx

KSAUDIO_SPEAKER_DIRECTOUT represents a configuration with no speakers and is defined in Ksmedia.h as zero. [...] For example, channels 0 through 30 might contain, respectively, drums, guitar, bass, voice, and so on. For this kind of raw audio data, speaker positions are meaningless, and assigning speaker positions to the input or output streams could cause a component such as KMixer to intervene inappropriately by performing an unwanted format conversion. If a device is unable to process the raw audio streams, it should reject a request to change its speaker configuration to KSAUDIO_SPEAKER_DIRECTOUT.

IMHO current SoX behaviour is preferred: SoX output data are (usually) regular audio files (speech/music/etc), not some raw audio data.

[Gumboot]

Well, then by implication the channel allocation is simultaneously redundant and untrustworthy, because it's not derived from any real knowledge but instead inferred from a convention.

The inconsistency to which the Microsoft documentation refers is precisely the inconsistency you're proposing to make mandatory by writing a guess into an authoritative field.

This post has been edited by Gumboot: Dec 13 2011, 17:54