IOhannes m zmoelnig zmoelnig@iem.at wrote:
this sounds a bit to complicated to me.simpler:start pd like normalcreate the gemwindow on "another" display with an argument to the create-message: [create localhost:0.1(
hi thanks for the reply. i tried this but all i got was....
watchdog: signaling pd... error: GEM: could not open X display localhost:0.1 Creating on display localhost:0.1 watchdog: signaling pd... watchdog: signaling pd... watchdog: signaling pd... error: GEM: Could not open display localhost:0.1 error: GEM: Unable to create window error: GEM: gemwin: no window made
could there be a problem with my XFree86config file. should i use the nvidia twinview option instead of multiheadlayout? i attached my xfree config file just in case
also, when running a fullscreen Gem window, is their a optimal resolution?
depends on your hardware (vga-beam, tv-beam)if you use "dimen" to set the dimension, fullscreen will try to set this resolution first and falls back to the current resolution of your display if it doesn't succeed:e.g. [dimen 640 480, fullscreen 1, create( sets the resolution of the display to 640x480 (even if the XF86Config says 1024x768) and creates the window at this resolutione.g. [dimen 500 500, fullscreen 1, create( will most likely fail to set the display resolution to 500x500 and thus the windows will have a resolution of 1024x768
mfg.a.dsr IOhannes
hi crew> i was wondering if someone could send me a hint or link to help with my GEM second monitor issue. DISPLAY=localhost:0.1; pd -guicmd "DISPLAY=localhost:0.0; /usr/lib/pd/bin/pd-gui" -lib Gem -lib zexy
tdunstan@ihug.com.au wrote:
watchdog: signaling pd... error: GEM: could not open X display localhost:0.1 Creating on display localhost:0.1 watchdog: signaling pd... watchdog: signaling pd... watchdog: signaling pd... error: GEM: Could not open display localhost:0.1 error: GEM: Unable to create window error: GEM: gemwin: no window made
could there be a problem with my XFree86config file. should i use the nvidia twinview option instead of multiheadlayout? i attached my xfree config file just in case
unfortunately i am not a big X-guru and i have never tried to use 2 screens without xinerama on dual-headed cards. if you are not too biased against twinview i would suggest using it.
anyhow: if you are using the multiheadlayout, you will have to allow remote connection to it. probably the easiest way to test is, with some tiny X-application ( i always use "xclock" for this) so, what would suggest to do is:
- start up your multihead-X
- get access to the second screen; launch a terminal there; execute
"xhost +" or similar (probably you want to be more restricted); 3) go back to the first screen; 3a) do some testing: "export DISPLAY=localhost:0.1; xclock"; 4) launch pd/Gem; make sure that the display variable is set correctly (esp. if you have been testing) 5) [create localhost:0.1(
so far, i have only been able to create remote Gem-windows on systems , where both machines were equipped with nvidia-cards. (shouldn't be a problem for you) on other configurations it crashes; i guess this has something to do with offscreen-rendering
oh. i just had a look at sources and found one cause for the crashes. i have fixed this for now (checked it in already). the new version disables the fullscreen mode on a remote display (the possibility was one cause for the crash) sometimes the window cannot be created the first time you try (i guess this is due to the asynchronous nature of Xfree86). just retry.
TODO: probably the [gemwin] should give some status, whether there actually is a window or not
mfg.asd.r IOhannes
hi,
are there some irregularities on the list since yesterday? a posting of me was not delivered, and maybe some of other people too? I got about 15 postings yesterday???
marius.
-
IOhannes m zmoelnig -
marius schebella -
tdunstan＠ihug.com.au