20 Mar
2012
20 Mar
'12
10:31 a.m.
On 03/20/2012 10:08 AM, Lorenzo Sutton wrote:
On 19/03/12 20:51, Fons Adriaensen wrote:
[...]
~/.asoundrc: yes[1], jack-plugin:no
http://alsa.opensrc.org/Jack_and_Loopback_device_as_Alsa-to-Jack_bridge
you use the alsa loopback-device instead of the jack-plugin.
Since the "snd-loop" kernel-module is a fully-fledged alsa-device,
application support is in general much better than with the jack-plugin;
however you will have alsa_in/out (or zita-a2j/j2a) running all the time
to bridge the loopback-device to jack (depending on resampling- quality
and CPU it uses 1-3% CPU and eats up a bit more of a laptop's battery).
best,
robin
[1] the .asoundrc is only used to set the default output to the loopback
and to allow concurrent access of alsa-clients to it. It's not required
(you could configure most alsa-clients to directly output to the
loopback-[sub]devices), but handy.
(meanwhile I'm back home, the loopback device
is hw:3 here)
[terminal 1]
fons@zita1:/audio/audiofiles/tracks> mplayer -ao alsa:device=hw=3.1
diana-krall-almost-blue-44.wav
[...]
[terminal 2]
fons@zita1:~> zita-a2j -d hw:3,0 -r 44100
Starting synchronisation
/me makes connections in qjackctl and hears lovely piano intro...
[...]
If I understood everything correctly you *still* need to set up your
.asoundrc with the jack plugin to have this working right?