> Paul Yeatman <[EMAIL PROTECTED]> writes:
>
> > I now am convinced that the problem resides with the appearance that
> > Flash accesses /dev/dsp directly creating a conflict anytime another
> > application has already locked the dsp device first, such as esd. The
> > Mozilla wrapper that seems to offer a way around this doesn't appear to
> > work for me.
> >
> > My current solution is to change the default behavior of esd from
> > "auto_spawn" being set to off to being on and, as I'm using gnome,
> > either disabling sound in gnome altogether or killing the esd process
> > that is started once I log in. This solution is satisfactory for
> > the moment but took quite awhile to figure out.
>
> Have you tried the '-as' option of esd? I use 'esd -as 2' to require
> esd to release /dev/dsp 2 seconds after it finishes, so other devices
> can use it. That allows me to use programs with both esd and /dev/dsp
> output, but not at the same time.
Yes, this is what makes things work for me now and is essentially how
I'm running things although I'm currently using the default of 5
seconds (if I have any problem with this, I might try a shorter time as
you are using). Thanks for offering the suggestion.
The only bummer with this setup is that not all audio calls (that don't
use /dev/dsp directly) starts the esd process automatically. I don't
hear the general Gnome event sounds anymore, for instance, and I'm
assuming that this is because esd is no longer running in the
background and, apparently, they don't start the esd process on their
own. Some people would likely say "good" to this. I kinda miss 'em.
A very minor complaint. I'm happier to have Flash working :)
> --
> Carl Johnson [EMAIL PROTECTED]
>
>
--
Paul Yeatman (858) 534-9896 [EMAIL PROTECTED]
==================================
==Proudly brought to you by Mutt==
==================================
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
