[pulseaudio-tickets] [PulseAudio] #639: Phonon error-messages about not working device after KDE-login.
PulseAudio
trac-noreply at tango.0pointer.de
Mon Oct 5 09:23:11 PDT 2009
#639: Phonon error-messages about not working device after KDE-login.
------------------------+---------------------------------------------------
Reporter: COMER352L | Owner: lennart
Type: defect | Status: closed
Milestone: | Component: daemon
Resolution: invalid | Keywords:
------------------------+---------------------------------------------------
Changes (by coling):
* status: reopened => closed
* resolution: => invalid
Comment:
Dude, you clearly don't understand what's going on otherwise you would not
make comments like that. For a start Phonon and PulseAudio are very
different beasts and PulseAudio deals with things at a fundamentally lower
level than Phonon, so comparing them is useless even if Phonon appears to
solve some of the same problems as PA, in reality it's is mile and miles
short of providing the features and capabilities of PA. I'm quite happy to
accept that and the Phonon devleoper's do to, and so should you! If there
is any doubt, you should see how much resources and effort Nokia (who own
Qt) are putting into PulseAudio development right now! Just look at Jyri's
slides from LPC last week if you are in any doubt.
Regardless of that, if pulseaudio is running on your system, then it will
use the audio device. If some other app tries to access the audio device
when pulse has it open it '''will''' fail unless your card supports
hardware mixing. This is expected and cannot be avoided. This is why, if
you use pulseaudio, you should route '''all''' your audio through it,
either via the alsa-pulse plugin or via specific pulse client
implementations in various audio libraries/programs (e.g. mplayer's -vo
pulse, xine's pulse output plugin, vlc's pulse output plugin etc. etc.).
This is how pulseaudio is designed to work and how you would configure
pulse to "not interfere with phonon" (or rather configure phonon to not
interfere with pulse!
To expect both phonon and pulse to access the hardware at the same time on
devices that do not support hardware mixing shows a lack of understanding.
And please do not deride my efforts to improve the interaction between
pulseaudio and phonon. I've spent most of the last two weeks working on
exactly this (and it's no small feat!) and while you may not be "talking
about phonon-integration" that is the correct solution to this problem.
I'm working with various KDE and Qt developers to review my work before I
commit it to KDE's svn (yes I am a KDE developer too).
So the short answer is quite simple: do not run the pulseaudio daemon if
you plan to use any other audio output system than pulseaudio. The long
answer is here:
http://colin.guthr.ie/2009/10/kde-plus-pulseaudio-does-not-equal-sucks/
Please be a little more considered in your responses in future.
--
Ticket URL: <http://pulseaudio.org/ticket/639#comment:3>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server
More information about the pulseaudio-bugs
mailing list