Re: 2nd display not working (ogl disapearing)
I take that back…, s-video is working with regular jitter matrix patches.
If I run a patch with open gl, using a floating window, it draws black as I
drag it to the video output. Only the frame remains. If I drag it back, the
context gets redrawn and the objects are back.
If change the position of jit.window to a different monitor, it says:
jit.gl.render: building GL on window "context"…
sounds reasonable, only on s-video it stays black.
Is this some kind of bug? I’m really getting worried now. Please tell me I’m
doing something wrong.
This should work. However, you haven’t provided us enough information
to offer any advice. As always, please follow the oft posted bug
reporting guidelines with detailed information about your HW,
Graphics card, driver version, Software version, a simple example
patch that illustrates the problem with clear steps to reproduce.
Otherwise there is little chance we will take the time to investigate
Sorry I wasn’t clear. I can use any patch from the help files.
Take jit.gl.render help. move floating window with the rotating plane and
move it to the 2nd monitor. In the case of s-video, I only see the window
object with a black content. move it back the rotating plane is there again.
This works fine with non-opengl like a video played in the jit.windowhelpfile.
For my vga output the jit.window help file doesn’t work either. I only get a
distorted image of the last frame. If I place the window halfway, only the
half on my primary monitor keeps playing.
I reported my system in the first mail, but here it is:
win xp home, jitter 1.5.2, nvidia go6800, dell inspiron 9300, pentium M.
Yesterday I did a presentation using the vga output, and oddly enough I got
it to work (ogl also) using the "clone display" setting of my video card
instead of "dual display". I can’t work like that for life performances
because then I’d loose my interface.
Other apps like mediaplayer or winamp work fine using a second monitor.
As I understand it, the part of the window that is on the second display
actually has a different render context than the one on the first.
so if you move a window from one screen to another, that new context
does not have the initialisation that the first one has had.
this is confusing as in your patch there is only one jit.gl.render
when I move a window from one screen to another, I always have to
redefine textures and erasecolor etc again for the jit.gl.render
Thanks for clarifying. Unfortunately, I’m unable to reproduce your
problems on my PC, when I simply drag the window in
jit.gl.render.help to the second VGA monitor. Here’s my machine info:
AMD Dual Opteron
XP Pro SP2
GeForce 6800 GT
NVidia ForceWare Driver 77.22 (not the latest)
This should work properly, and my first recommendation would be to
try updating your graphics card drivers if possible.
Thanks Joshua and Jennek, I got it working on both vga and s-vhs. I think
because of adding jit.displays, I’m not really sure. I also tried to update
my drivers, but only Dell drivers are supporting my go6800. There are lots
of problems that remain. I can’t figure them all out, but it seems there
are multiple bugs going on.
- my cpu is increased by at least 20% both vga and s-vhs (is this normal? My
patch is open-gl only)
– changing the jit.window’s sync attribute while using the 2nd display
freezes max, both vga and svhs
– switching the window between primary and secondary output makes changes
opengl object settings. Especially gl.models disappearing. I have to change
the material_mode setting to bring them back.
– when playing around max often reaches 95% cpu usages and stays up, even
though my patch always runs between 30-60%
The best result I’ve had with vga. setting the window to the 2nd output
before turning on the rendering, because switching window positions seems to
cause a lot of trouble. Using svhs I haven’t managed to get reasonable cpu
usage at all.
I know this is not a proper bug report, but If there are settings / things I
can try to solve some of these problems I’d really appreciate the help. I
don’t have time left to really get into these bugs, because I’ve lost a lot
of time already and I have to prepare for a gig in few days. I guess keeping
my fingers crossed it the most I can do :-(
Did you try your patch on a mac yet? Otherwise as an backup you can also use my PowerBook for the performance. I had never problems with jit.windows on a second monitor on a mac.
>> 16 March 2006 opening of the SWITCH exposition with performances at V2_ Rotterdam, The Netherlands. More info: http://switch.wdka.hro.nl/ < <
thanks for offering, but I don’t think I have time to test it. Switching to
mac would also mean I have to test and recompile some externals and pluggos
I’m using. Maybe as a last resort…I hope not.
Forums > Jitter