17 Apr
2015
17 Apr
'15
9:18 a.m.
73
Ron / W4MMP
On 4/17/2015 08:23, jack-devel-request(a)lists.jackaudio.org wrote:
> Send Jack-Devel mailing list submissions to
> jack-devel(a)lists.jackaudio.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
> or, via email, send a message with subject or body 'help' to
> jack-devel-request(a)lists.jackaudio.org
>
> You can reach the person managing the list at
> jack-devel-owner(a)lists.jackaudio.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Jack-Devel digest..."
>
>
> Today's Topics:
>
> 1. Re: running jackd from rc.local (Adrian Knoth)
> 2. alsa_* device or resource is busy (Athanasios Silis)
> 3. Re: alsa_* device or resource is busy (Adrian Knoth)
> 4. Re: Jack on Raspberry PI 2 (Ron) (Ron)
> 5. Re: Jack on Raspberry PI 2 (Ron) (Jeremy Jongepier)
> 6. Re: alsa_* device or resource is busy (Ralf Mardorf)
> 7. Re: alsa_* device or resource is busy (Athanasios Silis)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 17 Apr 2015 12:04:32 +0200
> From: Adrian Knoth <adi(a)drcomp.erfurt.thur.de>
> To: Athanasios Silis <athanasios.silis(a)gmail.com>om>, Jeremy Jongepier
> <jeremy(a)autostatic.com>
> Cc: Developers JACK <jack-devel(a)lists.jackaudio.org>
> Subject: Re: [Jack-Devel] running jackd from rc.local
> Message-ID: <5530DAB0.9050804(a)drcomp.erfurt.thur.de>
> Content-Type: text/plain; charset=windows-1252; format=flowed
>
> On 04/17/15 12:00, Athanasios Silis wrote:
>
>> that did it.
>> I know little about pam.d because I mostly use slackware. so may I ask:
>>
>> if this code snippet was commented out up until now, who/what givew me
>> elevated permissions when I log into my ubuntu session?
> The same line, just in a different file under /etc/pam.d/ - most likely
> named after your logon manager (gdm I guess).
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 17 Apr 2015 14:16:51 +0300
> From: Athanasios Silis <athanasios.silis(a)gmail.com>
> To: Developers JACK <jack-devel(a)lists.jackaudio.org>
> Subject: [Jack-Devel] alsa_* device or resource is busy
> Message-ID:
> <CADgchnvUANaho4R5ch+4mz=CKzeSJ=m11ia5wOCNZca5j4SRcw(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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?
>