In my experience, the order of channels in jack are stable enough to use this simple channels remapping trick:
mplayer -channels 4 -af channels=4:4:0:0:1:3:2:1:3:2 -ao jack:port=ambdec AJH_eight-positions.amb Adapt as needed. -- Marc Fons Adriaensen <f...@linuxaudio.org> a écrit : > On Thu, Nov 14, 2013 at 12:00:10AM +0000, Andy Furniss wrote: > > > I am not experienced with ambdec, but while trying something today I > > noticed something confusing when feeding direct with mplayer - > > > > mplayer -channels 4 -ao jack:port=ambdec pwh-VoiCE-Round.amb > > > > The channels are crossed as in the screenshot. This doesn't happen > > if I were to use the same mplayer command to a different sink. > > > > I suppose it does match the order on the config screen, but not the > > jack input names. > > > > http://imageshack.com/a/img203/1880/1xzw.png > > Mplayer's Jack support is broken, it doesn't allow you to specify the > ports to connect to, only the application name. And Jack itself has > no notion of any 'order' of the ports, whatever order there is has to > be inferred from the port names. Mplayer doesn't do this, and the > result is more or less random connections. > > In this case the sequence matches the one in the config window, > probably because Ambdec creates its ports in that order, and when > asked for Ambdec's ports, Jack happens to list them in the same order > again. But that is not documented in Jack's API, so you can't rely on > it. > > The only solution is to fix Mplayer. > _______________________________________________ Sursound mailing list Sursound@music.vt.edu https://mail.music.vt.edu/mailman/listinfo/sursound
