->>In response to your message<<-
--received from Wim De Smet--
>
> On Wed, 21 Jul 2004 14:14:03 -0700, Paul Yeatman <[EMAIL PROTECTED]> wrote:
> > I just noticed something I didn't notice before. Since I have learned
> > I need to kill esd before going to a flash-enabled web site to see the
> > flash correctly (and not have my browser die), I assumed the flash was
> > spawning its own esd process. Actually, I just noticed that, while
> > flash is playing correctly--without freezing and with sound--no esd
> > process is running. So flash must be accessing /dev/dsp directly which
> > thus must be the problem when an esd process is already running.
>
> Sounds logical.
>
> >
> > Thus, the solution would seem to be (as Wim pointed out) the sound
> > driver wrapper used by Mozilla. Unless I'm using it wrongly (again,
> > I'm using Sarge), it doesn't appear to solve the problem. I'm assuming
> > if I'm using esd that I want the value of "esddsp" for MOZILLA_DSP.
> > Yet neither this nor the value "auto" seems to allow flash to play from
> > a web browser while esd is running. In both cases, the flash
> > animation and the browser itself hangs. Part of the strangeness
> > is that this wasn't a problem in Woody. This has only been the
> > case since I've upgraded to Sarge (which possibly is due to a
> > later version of Mozilla?).
>
> It seems strange that it doesn't just work out of the box. Are you
> using the latest version of the flashplugin btw (installed with the
> deb package I presume?). You may want to file a bug report on this. I
> think it should just work...
At the moment, I have Flash installed from a download from Macromedia
itself. This is only because I could never get things to work with the
Debian flashplugin-nonfree package nor a flash plugin package provided
from another apt source site (both using version 7, I'm fairly
confident). Now the value I was using for MOZILLA_DSP was "espdsp" the
whole time (I never thought to try different values for this back
then). I don't know if that has anything to do with why things were
not working but seems to me to be the best setting given that I'm using
esd. Due to the overall problem, I spent some time in the Macromedia
Flash mailing list where I read someone commenting about how many
problems would be avoided if people only read the instructions and
followed advice/instructions given via the mailing list. This is when
I downloaded the plugin, version 7.0 r25, directly from Macromedia and
followed the instructions to the "t" (which, interestingly enough,
places one of the two files in a different location). I hoped this may
solve things but no dice. This is what I still have installed at the
moment.
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. Likewise, I find
it strange that things didn't work right out of the box (and if
I've had such a problem with it, why not many others?). Where do you
suggest filing a bug report: with Debian, Mozilla, Macromedia, . .
. ?
Thanks to you and everyone else for the replies with insights and
feedback.
Paul
--
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]
