Welcome Guest ( Log In | Register )

Multichannel Channel Order
post Dec 12 2011, 22:21
Post #1

Group: Members
Posts: 20
Joined: 29-September 11
Member No.: 94046

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
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
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.


It was actually a WAVEX if that makes any difference.

This post has been edited by xslig: Dec 12 2011, 22:37
Go to the top of the page
+Quote Post
Start new topic
post Dec 13 2011, 06:29
Post #2

WavPack Developer

Group: Developer (Donating)
Posts: 1351
Joined: 3-January 02
From: San Francisco CA
Member No.: 900

QUOTE (xslig @ Dec 12 2011, 14:21) *
It was actually a WAVEX if that makes any difference.

Yeah, actually that does make a difference. It turns out that the original intent of the --channel-order option was to specify the channel order when it was unknown, either in the case of a raw file (which you discovered) or the case of a WAV file that does not have the extensible header. For WAV files with the extensible header, the assumption was that the channel order was well defined (almost the whole point of having that header was to supply exactly that info). It would seem that your WAVEX files do, in fact, specify unassigned channels (SoX files, for instance, appeared like this until a fix that I contributed).

Since this has come up a couple times, my plan for the next revision is to allow some option to override the channel order...perhaps a new option --force-channel-order. In the meantime, you should be able to use raw files or simply not write the WAVEX header (or, of course, have a WAVEX header that correctly specifies the channels).

Hope this helps and thanks! smile.gif

Go to the top of the page
+Quote Post

Posts in this topic

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:


RSS Lo-Fi Version Time is now: 30th November 2015 - 23:16