Hi all,
A little over a year later I'm revisiting this project, where the core
challenge was to connect a second USB audio device and have PD (actually
pd-l2ork) utilize it, with all of this running automatically at boot.
The system has run quite well, but once every while (maybe 15% of the time)
PD fails to start up, with the qjackctl message window saying "Killed". I
haven't been able to find out what's going wrong, perhaps somebody can help
me. Otherwise I am thinking of making a jackd approach, so completely
non-GUI, and perhaps utilizing zalsa_out instead of zita-j2a.
Right now the system works like this:
- in /home/.config/lxsession/LXDE-pi/autostart, @qjackctl is added to
autostart it when the system (Raspbian) boots;
- in qjackctl's Setup page, a script is executed after startup,
- in that script these commands are run:
zita-j2a -d hw:Device_1 &
sleep 2
# to set the system volume:
amixer -c 1 cset numid=6 30
amixer -c 2 cset numid=6 30
sleep 2
pd-l2ork -rt -audiobuf 20 -inchannels 2 -outchannels 4
/home/pi/Documents/patch.pd &
Also in qjackctl's Setup page, Activate Patchbay persistence is checked to
make sure the 4 PD outputs are connected to the 4 out-channels in jack. I
wonder how this would be done on the command line.
I'm having difficulty in experimenting with zalsa_out; the example commands
that Robin Gareus suggested earlier don't seem to be valid on my system...
also I can't find any documentation on either zalsa or the -I option that he
mentioned:
Robin Gareus wrote
Is there a reason why you do want the external clients
instead of using
jack1's built-in version of zita-ajbridge?
jackd \
-I CARDNAME:zalsa_out/-dhw:CARD \
-I CARDNAME:zalsa_in/-dhw:CARD \
-dalsa ...
In your case try something like
jackd -I alsa-playback:zalsa_in/-dhw:CODEC_1 -dalsa -dhw:PCH -r48000
-p1024 -n2
If anyone has any suggestions and/or pointers for me what to try or where to
find more info, that would be great. Thanks in advance.
--
Sent from:
http://linux-audio.4202.n7.nabble.com/linux-audio-user-f5.html