Hi and thanks so much for the reply.
->>In response to your message<<-
--received from Jacob S.--
> That's odd. I'm using esd on my system (previously with OSS drivers, now
> with Alsa) and I can hear sound from flash just fine; as well as play
> xmms at the same time, etc.
I'm fairly sure the system is using esd with OSS drivers so this
could be the difference. Well, actually, how do I confirm OSS
drivers? The correct sound module, cmpci, is getting loaded. That's
typically what I think of as the driver. Where/how does OSS come in.
I for sure don't have ALSA installed. I didn't do any sound
configuration myself. The build correctly identified the sound card and
loads the correct module with no configuration/help needed on my part
(a nice difference from previous builds of Debian :)
>
> What happens if you kill any existing esd instances, run "esd &" from a
> terminal in X (assuming you're logged in as a user, not root) and then
> run "esdctl unlock"? Are you able to play both xmms and flash sounds?
> Also, you are using the esd output plugin in xmms, aren't you?
>
I have no idea what 'esdctl unlock' does but I did as you said (got
a series of increasing pitch tones when I ran 'esd &') but
got the same result: xmms et al. work fine, while the browser,
trying to employ the flash plugin, incurably freezes.
Maybe I should try esd employing ALSA drivers?
Paul
>
> On Tue, 20 Jul 2004 11:04:27 -0700
> Paul Yeatman <[EMAIL PROTECTED]> wrote:
>
> > Hi again. I'm responding to my own post. It wasn't until today,
> > weeks after my original post, that I got more clues as to is going on
> > concerning flash causing Mozilla to freeze on my Debian Sarge system.
> > The problem appears to be with esd. Esd (appears to be ) used by
> > default by gnome and is started--esd -nobeeps--when you log in. This
> > works fine with everything: xmms, xine, etc. The only case in which
> > it doesn't work is when the flash plugin is invoked from a web
> > browser. The animation will soon stop and the browser is toast. I
> > feel fortunate today to discover that if esd is first killed before
> > going to a website running flash, the flash runs fine albeit without
> > sound. If "auto_spawn=0" is changed to "1" in /etc/esound/esd.conf
> > and any esd processes are first killed, going to a flash website will
> > automatically start an esd process and flash will play normally (with
> > sound!) but then nothing else, such as xmms, will work until the flash
> > completes and the esd processes automatically completes (after 5
> > seconds in my case). This kinda defeats the point of esd, doesn't it?
> > Can anyone help me out with what is going on here? As all other
> > audio/video applications I run simultaneously use the initial esd
> > process started by gnome, why can't flash? Should I force gnome to
> > use something other than esd?
>
> That's odd. I'm using esd on my system (previously with OSS drivers, now
> with Alsa) and I can hear sound from flash just fine; as well as play
> xmms at the same time, etc.
>
> What happens if you kill any existing esd instances, run "esd &" from a
> terminal in X (assuming you're logged in as a user, not root) and then
> run "esdctl unlock"? Are you able to play both xmms and flash sounds?
> Also, you are using the esd output plugin in xmms, aren't you?
>
> HTH,
> Jacob
>
> --
> GnuPG Key: 1024D/16377135
>
> Random .signature #43:
> Q: How many Microsoft Programmers does it take to screw in a lightbulb?
> A: It cannot be done. You will need to upgrade your house.
>
> Q: How many Linux users does it take to change a lightbulb?
> A: Two. One to write the HOWTO-LIGHTBULB-CRONJOB, and another to read
> it.
--
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]
