On Thu, 14.02.08 01:20, Colin Guthrie (gmane at colin.guthr.ie) wrote: > Is pulse supposed to maintain several EsounD socket connections. > > After logging in I see about 10 or 11 such clients in paman. While doing > lsof and grepping for the socket file itself only pulseaudio is recorded > as having them open. Perhaps it's not closing the sockets correctly? Or > perhaps apps just maintain a permananet socket connection and all is as > it should be? Certainly several apps have libesound open so it's > entirely possible. Every gnome app keeps one connection open to be able to quickly fire sound events. > Also (completly OT now but as I may have your attention ;) when I use > the latest mplayer svn pulse code, when I use -ao esd (pointless I know) > I see two connections in paman Clients tab... one is a standard named > "EsounD client..." and the other is simply "MPlayer" (same as appears > for a -ao pulse). the named one is the one that actually streams audio. The other is used for vol control. > mplayer + esd has a fairly high latency FWIW, audio > and video appear out of sink for me and just playing a simple mp3 is > slower to start than with -ao pulse too. Just thought I'd mention it > (not really an important issue IMO but the same latency may affect other > apps where no specific pulse interface exists - certainly users have > reported that to me - so if you have any thoughts please share them :)). esd provides no time synchronization info whatsoever, and this is absolutely not suitable for getting lip sync video. Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4
