Antoine Villeret

i'm trying to do some fast video tracking (>200fps)

so i've started to program a GLSL shader for image segmentation

but i realised that i can't render a very simple OpenGL scene faster than 60 fps ether with jit.window nor jit.pwindow destination

whereas i can do rendering up to 500 fps with a matrix destination

but as i'm using some shader i got the same error as described here : 

https://cycling74.com/forums/index.php?t=msg&goto=155341&rid=902&S=bab6c5f44f861ffab92ebfb8d6efb474&srch=shader+matrix+render#msg_155341

does anyone know a solution to do openGL readback at high frame rate with shader computing ?

i'm trying to do some fast video tracking (>200fps)
so i've started to program a GLSL shader for image segmentation
but i realised that i can't render a very simple OpenGL scene faster than 60 fps ether with jit.window nor jit.pwindow destination
whereas i can do rendering up to 500 fps with a matrix destination
but as i'm using some shader i got the same error as described here : 
https://cycling74.com/forums/index.php?t=msg&goto=155341&rid=902&S=bab6c5f44f861ffab92ebfb8d6efb474&srch=shader+matrix+render#msg_155341

fast-opengl-rendering

With screen refresh of 60 hertz = 60 cycles/sec = max of 60 fps 

(closely equivalent to what your eyes can perceive)

of course you could compute things faster, but to output to screen it 

is limited by your refresh rate of you monitor. By default in Jitter, 

the GL renderer (render+window) and the refresh rate are synced.

On 5-Feb-09, at 12:35 PM, Antoine Villeret wrote:

> i'm trying to do some fast video tracking (>200fps)

> so i've started to program a GLSL shader for image segmentation

> but i realised that i can't render a very simple OpenGL scene faster 

> than 60 fps ether with jit.window nor jit.pwindow destination

> whereas i can do rendering up to 500 fps with a matrix destination

> but as i'm using some shader i got the same error as described here :

> does anyone know a solution to do openGL readback at high frame rate 

With screen refresh of  60 hertz = 60 cycles/sec = max of 60 fps  
(closely equivalent to what your eyes can perceive)

of course you could compute things faster, but to output to screen it  
is limited by your refresh rate of you monitor.  By default in Jitter,  
the GL renderer (render+window) and the refresh rate are synced.

>
> hi,
>
> i'm trying to do some fast video tracking (>200fps)
> so i've started to program a GLSL shader for image segmentation
> but i realised that i can't render a very simple OpenGL scene faster  
> than 60 fps ether with jit.window nor jit.pwindow destination
> whereas i can do rendering up to 500 fps with a matrix destination
> but as i'm using some shader i got the same error as described here :
> https://cycling74.com/forums/index.php?t=msg&goto=155341&rid=902&S=bab6c5f44f861ffab92ebfb8d6efb474&srch=shader+matrix+render#msg_155341
>
> does anyone know a solution to do openGL readback at high frame rate  
> with shader computing ?
>
> thanks a lot
>
> antoine


On Feb 5, 2009, at 9:35 AM, Antoine Villeret wrote:

I would suggest you disable synchronization on your window (@sync 0). 

Otherwise, the maximum framerate is tied to the update of the display. 

There will be tearing however, but it sounds like you are using this 

less for display than for image analysis.

> but i realised that i can't render a very simple OpenGL scene faster  
> than 60 fps ether with jit.window nor jit.pwindow destination
> whereas i can do rendering up to 500 fps with a matrix destination

I would suggest you disable synchronization on your window (@sync 0).  
Otherwise, the maximum framerate is tied to the update of the display.  
There will be tearing however, but it sounds like you are using this  
less for display than for image analysis.

sync parameter doesn't affect the frame rate

but i turned off doublebuffer attribute and i achieve 500 fps !!

and you're right, i'm interested in image analysing not in displaying 500 fps !

sync parameter doesn't affect the frame rate
but i turned off doublebuffer attribute and i achieve 500 fps !!
and you're right, i'm interested in image analysing not in displaying 500 fps !

>> but i realised that i can't render a very simple OpenGL scene 

>> faster than 60 fps ether with jit.window nor jit.pwindow destination

>> whereas i can do rendering up to 500 fps with a matrix destination

> I would suggest you disable synchronization on your window (@sync 

> 0). Otherwise, the maximum framerate is tied to the update of the 

> display. There will be tearing however, but it sounds like you are 

> using this less for display than for image analysis.

what's the difference put "sync 0" on render or/and window ?

>
>
>> but i realised that i can't render a very simple OpenGL scene  
>> faster than 60 fps ether with jit.window nor jit.pwindow destination
>> whereas i can do rendering up to 500 fps with a matrix destination
>
> I would suggest you disable synchronization on your window (@sync  
> 0). Otherwise, the maximum framerate is tied to the update of the  
> display. There will be tearing however, but it sounds like you are  
> using this less for display than for image analysis.
very interesting.
what's the difference put "sync 0" on render or/and window ?
thx.

fast openGL rendering