[pulseaudio-discuss] Problem with 0.9.7 and Audacious

[Thomas Jost]

Le 20 novembre 07 à 02:16:26, Lennart Poettering <lennart at poettering.net> a
écrit :

> On Fri, 16.11.07 18:36, Thomas Jost (thomas.jost at gmail.com) wrote:
> 
> > Hi,
> > 
> > I have the same kind of problem with mplayer (svn version) and its
> > pulseaudio output : shorts pauses about every seconds, which makes it
> > impossible to watch anything.
> 
> HHmm, does Mplayer SVN ship a Pulse plugin now? Or did you apply the
> patch I wrote a long time ago but which afaik never got merged?

Well I was using your patch on my Gentoo laptop, but I didn't need it when
I installed mplayer on my Archlinux workstation as it does now include a
Pulse plugin :
http://svn.mplayerhq.hu/mplayer/trunk/libao2/ao_pulse.c?view=log
And anyway the result was the same with both versions.


> > I noticed that if I don't load module-x11-publish (or if I run
> > "pax11publish -r"), things work nicely. And if I then run "pax11publish
> > -e" it starts not working again.
> >
> > In the same time everything works perfectly with xine and mpd, without
> > having to disable module-x11-publish or anything else.
> 
> Hmm, my instinct tells me that this probably has something to do with
> using TCP vs. using UNIX sockets. If you use module-x11-publish then
> the order of protocols that are published to X11 and thus are used by
> clients to connect to the PA server depend on the order the native
> protocol modules have been loaded into the server.
> 
> If module-x11-publish is not used then UNIX sockets are always
> preferred over TCP sockets. If you use module-x11-published is used
> then it *might* be the other way round.
> 
> Please paste what "pax11publish" (without any arguments) outputs!

You're right, it's definitely a TCP vs. UNIX socket problem. I've checked
it running pulseaudio -v, mplayer is using TCP sockets when
module-x11-publish is enabled and UNIX sockets when it is not.

thomas at schnouki % pax11publish
Server: schnouki.rez
Cookie: ea0269b5da7e30e...

I've noticed that when unsetting the server name in pax11publish (using
padevchooser: right click -> default server -> default), it works again
using an UNIX socket.

The odd thing is that mpd and xine are using TCP sockets as well without
any problem, mplayer really seems to be the only one which fails.

However I found a workaround : I'm using PA as a system-wide daemon (I
want mpd to work even if my X server crashes !) and before I was just
calling "pax11publish -e" in my .xinitrc (I use slim as a login
manager) before launching XFCE ; now I'm calling it like this :
PULSE_SERVER="PULSE_SERVER="{schnouki}unix:/var/run/pulse/native tcp:schnouki.rez:4713" pax11publish -e
and it works fine.

Thanks for the tip about TCP and UNIX sockets!

> Most likely MPlayer is using very short buffers in PA. They can be
> smaller if you use UNIX sockets, and need to be a bit larger if you
> use TCP. By default they are chosen quite large, so that they are safe
> on all transports. I wonder why that is not sufficient on mplayer.
> 
> 
> Lennart

Don't know, I haven't seen anything concerning buffer size in the mplayer
plugin code -- didn't really check it anyway.
However this problem only appeared with PA 0.9.7: I never had any problem
with 0.9.6.

Thomas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20071120/542e70e7/attachment-0001.pgp>