On 10/31/2009 02:16 PM, mark386 wrote:
One thing that can be done with these drivers (at least with ati's
fglrx) when using xinerama is that compiz can be enabled on one screen
and that screen can be rotated independent of the other displays.
Multiple independent displays with multiple
On Fri, 2009-10-30 at 18:43 +0100, Lennart Poettering wrote:
Dude. This is nonsense.
To you maybe.
WMs such as metacity are xinerama-aware and have been about
forever.
Guess I am showing my age because I have to admit that the last time I
tired Xinerama was wy before metacity was
On Fri, 2009-10-30 at 18:43 +0100, Lennart Poettering wrote:
And that's why I am saying that multiple screens per display is just a
pointless excercise, since it gives you exactly NOTHING that multiple
montors per screen wouldn't give you -- no, it takes features away.
Sorry Lennart, in my
Dude. This is nonsense.
To you maybe.
WMs such as metacity are xinerama-aware and have been about
forever.
Guess I am showing my age because I have to admit that the last time I
tired Xinerama was wy before metacity was around.
Windows won't be maximized across the
On Sat, 2009-10-31 at 07:55 +0800, Ng Oon-Ee wrote:
On Fri, 2009-10-30 at 18:43 +0100, Lennart Poettering wrote:
And that's why I am saying that multiple screens per display is just a
pointless excercise, since it gives you exactly NOTHING that multiple
montors per screen wouldn't give you
'Twas brillig, and Ng Oon-Ee at 29/10/09 04:47 did gyre and gimble:
On Thu, 2009-10-29 at 12:03 +0800, Leszek Koltunski wrote:
Well, the patch is there; you can go apply it, then load two
'module-x11-publish' :
load-module module-x11-publish display=:0.0 sink=foo
load-module module-x11-publish
Look at pulseaudio.desktop and start-pulseaudio-x11. These do exactly that
just now.
The script would need modified for this use case (as it registers X session
handler too, not just the publication) but in theory, just running
start-pulseaudio-x11 on each display should get you the
On Thu, 29.10.09 16:36, Leszek Koltunski (les...@koltunski.pl) wrote:
Look at pulseaudio.desktop and start-pulseaudio-x11. These do exactly that
just now.
The script would need modified for this use case (as it registers X session
handler too, not just the publication) but in theory,
Disclaimer: I don't really have any skin in this game so you can tell me
I'm stupid or whatever you want, however...
On Mon, 2009-10-26 at 16:05 +0100, Lennart Poettering wrote:
Yepp, and I'd argue the non-xinerama setup is useless.
/me looks over from his primary display (with it's separate
Well, the patch is there; you can go apply it, then load two
'module-x11-publish' :
load-module module-x11-publish display=:0.0 sink=foo
load-module module-x11-publish display=:0.1 sink=bar
and voilla! It's working automagically.
( BTW, what is the best way to load the modules? I put the above
On Thu, 2009-10-29 at 12:03 +0800, Leszek Koltunski wrote:
Well, the patch is there; you can go apply it, then load two
'module-x11-publish' :
load-module module-x11-publish display=:0.0 sink=foo
load-module module-x11-publish display=:0.1 sink=bar
and voilla! It's working
On Tue, 27.10.09 16:39, Jeremy Visser (jer...@visser.name) wrote:
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
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
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 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
On Tue, 2009-10-20 at 18:32 +0200, Michał Sawicz wrote:
Dnia 2009-10-20, wto o godzinie 17:18 +0100, Colin Guthrie pisze:
Did you try setting the xprops manually? Make sure that works first
(although if pax11publish is looking at the wrong display, it could
be
the pulse client libs are
On Tue, 20.10.09 18:32, Michał Sawicz (mic...@sawicz.net) wrote:
Dnia 2009-10-20, wto o godzinie 17:18 +0100, Colin Guthrie pisze:
Did you try setting the xprops manually? Make sure that works first
(although if pax11publish is looking at the wrong display, it could
be
the pulse client
'Twas brillig, and Leszek Koltunski at 20/10/09 16:20 did gyre and gimble:
Seems to me that 'pax11publish' disregards the screen number given in
its -D parameter and only pays attantion to the X server number.
for every N, pax11publish -D :0.N overwrites the X11 properties of
0.0.
Did you
Dnia 2009-10-20, wto o godzinie 17:18 +0100, Colin Guthrie pisze:
Did you try setting the xprops manually? Make sure that works first
(although if pax11publish is looking at the wrong display, it could
be
the pulse client libs are doing the same...)
Doesn't 0.0 and 0.1 mean there's only
'Twas brillig, and Michał Sawicz at 20/10/09 17:32 did gyre and gimble:
Dnia 2009-10-20, wto o godzinie 17:18 +0100, Colin Guthrie pisze:
Did you try setting the xprops manually? Make sure that works first
(although if pax11publish is looking at the wrong display, it could
be
the pulse client
Here's my usercase:
I've got a monitor and sound card hw:0.0 set up as my primary video/audio
sinks.
I've also got a TV , located in a different room, connected to a TV-Out and
to another sound card, hw:1.0
I've also got a Bluetooth keyboard and mouse. So whenever I want to watch a
video or show
2009/10/19 Leszek Koltunski les...@koltunski.pl:
Now, I would make me one happy duck if I could somehow tell Pulse to
automatically route audio to hw:1.0 whenever I am working on the TV, that
is, whenever DISPLAY is 1.0.
It looks like PULSE_SINK environment variable is exactly what you need,
'Twas brillig, and Leszek Koltunski at 19/10/09 09:38 did gyre and gimble:
Now, I would make me one happy duck if I could somehow tell Pulse to
automatically route audio to hw:1.0 whenever I am working on the TV,
that is, whenever DISPLAY is 1.0.
Should be simple, PULSE_SINK= env var does
'Twas brillig, and Maarten Bosmans at 19/10/09 11:10 did gyre and gimble:
2009/10/19 Leszek Koltunski les...@koltunski.pl:
Now, I would make me one happy duck if I could somehow tell Pulse to
automatically route audio to hw:1.0 whenever I am working on the TV, that
is, whenever DISPLAY is 1.0.
Ok, thanks guys!
Pulse Convert
On Mon, Oct 19, 2009 at 6:20 PM, Jeremy Visser jer...@visser.name wrote:
On Mon, 2009-10-19 at 16:38 +0800, Leszek Koltunski wrote:
Every time I work on the TV, the sound should be sent to hw:1.0, so I
have to fire up the new 'gnome-sound-properties 2.28'
'Twas brillig, and Jeremy Visser at 19/10/09 11:20 did gyre and gimble:
On Mon, 2009-10-19 at 16:38 +0800, Leszek Koltunski wrote:
Every time I work on the TV, the sound should be sent to hw:1.0, so I
have to fire up the new 'gnome-sound-properties 2.28' (BTW, wonderful
app! simple and
On Mon, 19.10.09 16:38, Leszek Koltunski (les...@koltunski.pl) wrote:
Now, I would make me one happy duck if I could somehow tell Pulse to
automatically route audio to hw:1.0 whenever I am working on the TV, that
is, whenever DISPLAY is 1.0.
As the others already pointed out, the X11 props
30 matches
Mail list logo
