On Tue, 20.11.07 14:14, Kevin Williams ([EMAIL PROTECTED]) wrote: > > Thanks a lot for the detailed response. I really appreciate it. > > On November 19, 2007 09:58:37 pm Lennart Poettering wrote: > > My educated guess is that some of your apps use PA natively, others > > don't but hardcode are configured to use the raw ALSA devices, or raw > > OSS devices. Now, PA closes all devices after a short time of > > idle. So, what might happen to you is that you first use a native > > app. That causes PA top open the device. If you then use a non-native > > app, then it won't work. But after the idleness timeout it will > > suddenly and magically start to work, because PA closed the devices. > > Voila ! That explains the weird behaviour seen with all the apps. But, if the > option "exit-idle-time" is responsible then, I don't have it set in > daemon.conf !
exit-idle-time is unrelated to this. The suspend timeout is controlled via the "timeout" parameter of module-suspend-on-idle. > The error message I get is "Audio output unavailable. The device is busy. > Xine > engine parameter: ". > After a while, the error message changes to "xine was unable to > initialize any audio drivers" !! > > Any ideas ? No, unfortunately not. It would be helpful if you could get your hands on some more verbose Xine debug output, though. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 _______________________________________________ pulseaudio-discuss mailing list pulseaudio-discuss@mail.0pointer.de https://tango.0pointer.de/mailman/listinfo/pulseaudio-discuss
