Forums > Jitter

fullscreen doesn't show the same as window

March 15, 2007 | 1:39 am

Hello

I’ve made a patch which consists out of several patches that process video on a videoplane. Each of them renders to the same gl.render-object. I gate the metronome that drives the individual patches. When I press a key the metronome is sent to the patch I want to turn on, and at the same time it receives an "enable 1" message, while the last one getting played gets turned off.

This is working when I look at the result in a floating window, but when I turn on fullscreen one the patches "freezes", and gets to be the frontmost picture. I think it’s strange everything works as expected up until I turn on fullscreen?

I don’t have much experience using openGL, but I was hoping someone could point me in the right direction?

Sorry that this isn’t explained in a better way…


March 15, 2007 | 3:20 am

is your jit.window double buffered? Try turning that on.

is this on XP or on Mac OS X?

On Mar 14, 2007, at 9:39 PM, Lut Lei wrote:

>
> Hello
>
> I’ve made a patch which consists out of several patches that
> process video on a videoplane. Each of them renders to the same
> gl.render-object. I gate the metronome that drives the individual
> patches. When I press a key the metronome is sent to the patch I
> want to turn on, and at the same time it receives an "enable 1"
> message, while the last one getting played gets turned off.
>
> This is working when I look at the result in a floating window, but
> when I turn on fullscreen one the patches "freezes", and gets to be
> the frontmost picture. I think it’s strange everything works as
> expected up until I turn on fullscreen?
>
> I don’t have much experience using openGL, but I was hoping someone
> could point me in the right direction?
>
> Sorry that this isn’t explained in a better way…

v a d e //

http://www.vade.info
abstrakt.vade.info


March 15, 2007 | 6:57 pm

This is on osx, on an intel mac.

I can’t really point my finger on what’s happening, and when I woke up today I couldn’t reproduce the problem.

Since jit.window is doublebuffered by default, I guess my instance is also, – not that I understand what this does.

I found it strange that when my jit.window was on my laptop it showed one thing, but the second I shoved it over to the TV, it showed another.

I just know that this inconsistency is probably perfectly logical in one way.


Viewing 3 posts - 1 through 3 (of 3 total)