Re: Alsa-devel digest, Vol 1 #1207 - 14 msgs

Re: Alsa-devel digest, Vol 1 #1207 - 14 msgs

[Nathaniel Gray]

On Wednesday 04 June 2003 06:48 am, 
alsa-devel-request@lists.sourceforge.net wrote:
> Florian,
>    Yes. Thanks. This is something Jaroslav pointed out later in the
> morning. With this strategy I got at least a simple alsa application
> to play sounds cleanly, so this was helpful.
>
>    Can you shed any light on getting a game like frozen-bubble to use
> Alsa? When I try to start this app it lock up with error messages
> about resources being busy.

That means that some other program is using the soundcard (only one 
program at a time can use it).  If you're running KDE then ARTS is a 
likely suspect and you can try running "artsdsp frozenbubble".  
Otherwise you can try "fuser /dev/dsp" or "fuser /dev/snd/pcmC0D1p" to 
find out the PID of the process that's using it.

Someday the dmix plugin might be usable in which case this problem will 
go away.

>    Am I correct in guessing that an app like frozen-bubble is using
> the OSS portion of Alsa? Is there some setup that I can do to point
> OSS sound requests to this default device?

That's pretty much automatic.  There's nothing you need to do.

-- 
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

Re: Re: Alsa-devel digest, Vol 1 #1207 - 14 msgs

[Mark Knecht]

On Wed, 2003-06-04 at 11:24, Nathaniel Gray wrote:
> On Wednesday 04 June 2003 06:48 am, 
> alsa-devel-request@lists.sourceforge.net wrote:
> > Florian,
> >    Yes. Thanks. This is something Jaroslav pointed out later in the
> > morning. With this strategy I got at least a simple alsa application
> > to play sounds cleanly, so this was helpful.
> >
> >    Can you shed any light on getting a game like frozen-bubble to use
> > Alsa? When I try to start this app it lock up with error messages
> > about resources being busy.
> 
> That means that some other program is using the soundcard (only one 
> program at a time can use it).  If you're running KDE then ARTS is a 
> likely suspect and you can try running "artsdsp frozenbubble".  
> Otherwise you can try "fuser /dev/dsp" or "fuser /dev/snd/pcmC0D1p" to 
> find out the PID of the process that's using it.
> 
> Someday the dmix plugin might be usable in which case this problem will 
> go away.

Nathanial,
   Hi. Thanks for the ideas. While I know it's not practical for you to
have gone back and reread all the the traffic on this over the last week
or two, I think this answer, while technically correct, possibly doesn't
apply in this case:

1) As I've reported, I'm running fluxbox which has no specific sound
support, servers, etc., to the best of my knowledge. There is certainly
nothing obvious when looking at processes. I've used Alsa under both
Gnome and KDE, so I am familiar with these potential problems. 

2) The single application answer would apply to other Alsa apps, like
aplay also. However, I can run aplay multiple times before I run
frozen-bubble, and I can run it immediately after killing frozen-bubble
after the hand. If some other application was using Alsa, and blocking
frozen-bubble, then I would expect it to block ALL other Alsa apps, and
not just frozen-bubble.


> 
> >    Am I correct in guessing that an app like frozen-bubble is using
> > the OSS portion of Alsa? Is there some setup that I can do to point
> > OSS sound requests to this default device?
> 
> That's pretty much automatic.  There's nothing you need to do.

Probably true, but I was told that using aplay would be automatic also,
and it wasn't. I've had to associate a pcm.!default entity to get it to
work, so something is not quite right. I continue to wonder if something
similar is effecting the OSS part of this machine.

I will have to look into the fuser idea. It sounds interesting.
Currently I have a different sound card loaded and this problem does not
appear. I'll have to load up the Via driver and try this out.

None the less, thanks for your insights. I will continue to look for the
answer, but this is software and I am blind.

With best regards,
Mark



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

Re: Re: Alsa-devel digest, Vol 1 #1207 - 14 msgs

[Patrick Shirkey]

Mark Knecht wrote:
> 
> 
> Probably true, but I was told that using aplay would be automatic also,
> and it wasn't. I've had to associate a pcm.!default entity to get it to
> work, so something is not quite right. I continue to wonder if something
> similar is effecting the OSS part of this machine.
> 

Have you also symlinked /dev/dsp to /dev/adsp0 as that will allow oss 
apps to use the hw:0,1 channel?


-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

Re: Re: Alsa-devel digest, Vol 1 #1207 - 14 msgs

[Jaroslav Kysela]

On Thu, 5 Jun 2003, Patrick Shirkey wrote:

> Mark Knecht wrote:
> > 
> > 
> > Probably true, but I was told that using aplay would be automatic also,
> > and it wasn't. I've had to associate a pcm.!default entity to get it to
> > work, so something is not quite right. I continue to wonder if something
> > similar is effecting the OSS part of this machine.
> > 
> 
> Have you also symlinked /dev/dsp to /dev/adsp0 as that will allow oss 
> apps to use the hw:0,1 channel?

It not required. See to alsa-kernel/Documentation/OSS-Emulation.txt, look 
for 'dsp_map' and 'adsp_map'.

						Jaroslav

-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs



-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.

RE: Re: Alsa-devel digest, Vol 1 #1207 - 14 msgs

[Mark Knecht]

> > >
> >
> > Have you also symlinked /dev/dsp to /dev/adsp0 as that will allow oss
> > apps to use the hw:0,1 channel?
>
> It not required. See to alsa-kernel/Documentation/OSS-Emulation.txt, look
> for 'dsp_map' and 'adsp_map'.
>
> 						Jaroslav
>
Patrick and Jaroslav,
   Interesting ideas. I'll goo look at these docs this evening.

   I think this may specifically be a Via82xx driver problem. If I change
only one line in modules.conf (snd-via82xx to snd-hdsp) the problem does
away, so I don't think it's anything specific about my setup, although it
could have something to do with my specific motherboard I guess.

   Anyway, thanks for the ideas.

Mark






-------------------------------------------------------
This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
thread debugger on the planet. Designed with thread debugging features
you've never dreamed of, try TotalView 6 free at www.etnus.com.