17 Apr
2015
17 Apr
'15
6:16 a.m.
hi all, continuing from a previous email where I try to start up several
audio applications from a custom init script , which is run from rc.local,
I noticed that I get several
Capture open error: Device or resource busy
error messages for the alsa_(in|out) instances I set up:
alsa_out -d hw:DSP24,0 -c 10 -j dsp_out -r 48000 -p128 -n2 &
alsa_in -d hw:DSP24,0 -c 12 -j dsp_in -r 48000 -p128 -n2 &
alsa_out -d hw:Intel -c 8 -j hda_out -r 48000 -p128 -n3 &
alsa_in -d hw:Intel -c 2 -j hda_in -r 48000 -p128 -n3 &
These work when I use the script manually by logging in the pc.
but from rc.local the seems to be a problem with alsa.
on some reboots, perhaps one (random) of these will work , but usually non
of the 4 will be loaded correctly.
what could be conflicting here?
17 Apr
17 Apr
6:38 a.m.
On 04/17/15 13:16, Athanasios Silis wrote:
hi all, continuing from a previous email where I try
to start up
several audio applications from a custom init script , which is run
from rc.local,
I originally wanted to point out that the use of rc.local for this stuff
is discouraged, but you've just discovered this yourself now.
You should really consider your approach and come up with something
else.
what could be conflicting here?
Everything. Your login manager is probably using the card.
The whole concept of integrating desktop distros with rc.local for audio
is not going to fly, because the distros set device permissions based on
the logged in user.
There might also be a system-wide pulseaudio daemon running, probably as
root. You might get away with pasuspender -- alsa_out, but I wouldn't be
surprised if not, unless you wrap your su call in pasuspender.
Also note that you shouldn't be using alsa_in/out at all, use zita-a2j
and zita-j2a or use jackd-0.124.x where you can simply specify
additional cards:
$ jackd -A Intel -d alsa -d hw:DSP24,0
I don't know what you're trying to achieve, but I see mostly two
options:
(a) if you don't need a desktop, don't use one.
(b) if you do need a desktop, use their autostart features
For (b): You can have auto-login for a certain user. You can have
autostart for this user. Just run your script from the usual XDG
directories (or however your distro implements autostart).
Also consider switching to KXstudio - a lot of work went into it to make
things work. An integration effort other distros never bothered to do.
Cheers
7:19 a.m.
On Fri, 17 Apr 2015 13:38:36 +0200, Adrian Knoth wrote:
Just run your script from the usual XDG directories (or
however your
distro implements autostart).
Likely the default DE for Ubuntu Studio still is XFCE4. If so, the OP
could run xfce4-session-settings, likely also available by the main
menu.
xfce4-session-settings -> tab "Application Autostart" -> "+
Add"
7:23 a.m.
Lots of good info, thanks.
I will certainly abandon the rc.local approach and try with autostart.
The pc I am refering to above is a jackd client, so the "system* hooks
connect to the jack master, that is why I need to enable the local
soundcards (on the jack client) through alsa_* . I shall change that to
zita_* as well.
yes ubuntu studio uses xfce4 . I shall try KXStudio as well :)
On Fri, Apr 17, 2015 at 2:38 PM, Adrian Knoth <adi(a)drcomp.erfurt.thur.de>
wrote:
On 04/17/15 13:16, Athanasios Silis wrote:
hi all, continuing from a previous email where I try to start up
Everything. Your login manager is probably using the card.
The whole concept of integrating desktop distros with rc.local for audio
is not going to fly, because the distros set device permissions based on
the logged in user.
There might also be a system-wide pulseaudio daemon running, probably as
root. You might get away with pasuspender -- alsa_out, but I wouldn't be
surprised if not, unless you wrap your su call in pasuspender.
Also note that you shouldn't be using alsa_in/out at all, use zita-a2j
and zita-j2a or use jackd-0.124.x where you can simply specify
additional cards:
$ jackd -A Intel -d alsa -d hw:DSP24,0
I don't know what you're trying to achieve, but I see mostly two
options:
(a) if you don't need a desktop, don't use one.
(b) if you do need a desktop, use their autostart features
For (b): You can have auto-login for a certain user. You can have
autostart for this user. Just run your script from the usual XDG
directories (or however your distro implements autostart).
Also consider switching to KXstudio - a lot of work went into it to make
things work. An integration effort other distros never bothered to do.
Cheers
several audio applications from a custom init
script , which is run
from rc.local,
I originally wanted to point out that the use of rc.local for this stuff
is discouraged, but you've just discovered this yourself now.
You should really consider your approach and come up with something
else.
what could be conflicting here?
3300
days inactive
3300
days old
jackaudio@lists.linuxaudio.org
3 comments
3 participants
participants (3)
-
Adrian Knoth -
Athanasios Silis -
Ralf Mardorf