Hi, On Mon, Jul 09, 2007, Takehiko Abe wrote: > On Sun, 2007-07-08 at 22:06 +0200, Loïc Minier wrote: > > Ok, so basically the problem is that in the default totem-xine and > > xine configurations, playback fails because alsa is used instead of > > esound, correct? > I don't know. (So, I guess alsa cannot be used while esound daemon > is running?)
In most cases, apps wont be able to use alsa directly when esound or another app is using alsa, they should use esound when esound is running, it is a software sound multiplexer. However, in some cases, the sound hardware supports being used multiple times (it has multiple "channels"), in which case you may use alsa twice or more, by multiple apps, or by esound and other apps. > > I think you had to enable esound explicitely yourself, but still I > > think xine should try to use esound first; if you agree with the > > analysis, I'll file this as an enhancement request against xine. > > Sorry, I'm not sure about this one either. I switched off esound > and content with the result for now. > > I still don't get exactly what esound is for. And it caused me some > other problems too (namely, esd was not started automatically and > 'Recording Level Monitor' complained about it, then 'Sound Recorder' > stopped working when I started it manually.) On most hardware, esound is required if you need multiple applications to output sound silmutaneously. For example, you receive an email alert when listening to music. When esound is running, you should configure all apps (or they should configure themselves automatically) to use esound. My questions are: - how did we come to the problem which made you report a bug: is it because you enabled esound that you got the bug? - if it's because of esound, would you agree that if xine tried to use esound if available and then would default to alsa, then your bug would be fixed? -- Loïc Minier
