ping?
On Mon, Oct 19, 2009 at 12:45:30PM +0200, Daniel Mack wrote:
On Wed, Sep 16, 2009 at 11:48:58PM +0200, Lennart Poettering wrote:
On Wed, 16.09.09 15:15, Daniel Mack (dan...@caiaq.de) wrote:
From: Kim Lester k...@dfusion.com.au
OS X does not define clockid_t or
On Mon, 26.10.09 15:03, Leszek Koltunski (les...@koltunski.pl) wrote:
We can do this, Not sure it makes a lot of sense though in the general
case, and makes we wonder how long before someone wants to attach this
informaton to a monitor, not a screen or display.
And then again, running a
Yepp, and I'd argue the non-xinerama setup is useless.
(...)
I long had a feeling that I am being a pest with my dual screen, no-one
seems to like it :) Least of all the people in the Gnome mailinglist...
1) Think about this usercase (that I already wrote about before):
- a monitor and a
My two cents :
I agree that this setup (with 2 screens) isn't useless at all! I had the
same setup a few years ago, when PA didn't exist, very nice. Someone could
watch a movie on the TV while I was working on the other screen. But I
thought that the multiple screen feature has been removed from
The patch below attaches X11 properties to a Screen, not a Display. Using
it, I am able to do the following:
leszek# pax11publish -D :0.0 -O alsa_output.pci-_01_06.0.analog-stereo
-e
leszek# pax11publish -D :0.1 -O alsa_output.pci-_00_07.0.analog-stereo
-e
leszek# xprop -root -display
Cool. The above patch actually fully works. One kjust has to load two
modules-x11-publish:
pactl load-module module-x11-publish display=:0.0
sink=alsa_output.pci-_01_06.0.analog-stereo
pactl load-module module-x11-publish display=:0.1
sink=alsa_output.pci-_00_07.0.analog-stereo
On Mon, 26.10.09 23:45, Leszek Koltunski (les...@koltunski.pl) wrote:
The patch below attaches X11 properties to a Screen, not a Display. Using
it, I am able to do the following:
Uh. As mentioned earlier I'd prefer if when reading those props we
would fallback to screen 0 if the default screen
On Mon, 26.10.09 23:45, Leszek Koltunski (les...@koltunski.pl) wrote:
diff -Naur pulseaudio-0.9.19-old/src/pulsecore/x11prop.c
pulseaudio-0.9.19-new/src/pulsecore/x11prop.c
--- pulseaudio-0.9.19-old/src/pulsecore/x11prop.c2009-10-26
23:07:57.0 +0800
+++
Hi,
Thanks for fast answering the email concerning Pulseaudio instabilities
under Ubuntu Karmic.
Our issue seems not to be so related with realtime issues under Ubuntu.
I understand that it is an important problem and I hope that this
situation will be fixed soon.
We recently discovered that
On Mon, 2009-10-26 at 16:05 +0100, Lennart Poettering wrote:
On Mon, 26.10.09 15:03, Leszek Koltunski (les...@koltunski.pl) wrote:
*snip*
) whereas 'separate X screen' creates 2 separate desktops (2 copies
of gnome-panels appear, one on each monitor, dragging is impossible,
each monitor has
On Fri, 23.10.09 18:55, Alexandre Savard
(alexandre.sav...@savoirfairelinux.com) wrote:
We are developing a VOIP phone.
I upgraded my ubuntu 9.10 Karmic last thursday. Since, I can't get any
audio playback from pulseaudio or very crappy one. There is several
playback buffer underrun
On Mon, 2009-10-26 at 16:05 +0100, Lennart Poettering wrote:
NVidia offers two ways to do it: you can setup the second monitor to be what
they call a separate X screen ( and that it precisely what I have here )
or a TwinView (nvidia-speak for Xinerama ).
this is bogus. gnome-panel is
On Tue, 2009-10-27 at 16:39 +1100, Jeremy Visser wrote:
Basically, X thinks it has a giant monitor the size of all your
screens.
Monitors, MONITORS, dammit. ;)
signature.asc
Description: This is a digitally signed message part
___
pulseaudio-discuss
13 matches
Mail list logo
