Robin Price

I quite liked the jit.gl.render.radialblur example that comes in the examples folder and decided to make my own version of it. I pretty much copied everything, just swapping the video textured cube for a nice sphere drawn with points. Only problem is the feedback doesn't work when I open the patch, I have to open the radialblur example and then it magically starts working - weird !!!

I don't even have to start the radialblur patch rendering just opening it seems to do it. What kind of voodoo ....?

Any ideas why this is happening, how can different instances of jit.gl.render in different patchers effect each other ?

I have included my patch, can anyone else replicate my problem or does it just start feeding back from the get go ?

Thanks in advance this has driven me insane all night and I'm going to bed.

opengl-feedback-radialblur-example-going-mad

Here's another approach to the same problem. The patch you're going

off of uses some older techniques before the jit.gl.object or

jit.gl.mesh objects existed. You can render to a texture by setting

the @capture attribute and process it with shaders via the jit.gl.slab

Here's another approach to the same problem.  The patch you're going
off of uses some older techniques before the jit.gl.object or
jit.gl.mesh objects existed.  You can render to a texture by setting
the @capture attribute and process it with shaders via the jit.gl.slab
object.

True that these examples are old, but here is what the problem was :

(actually just a coma missing somewhere, try to find it)

On 16-Aug-08, at 9:24 PM, Wesley Smith wrote:

> Here's another approach to the same problem. The patch you're going

> off of uses some older techniques before the jit.gl.object or

> jit.gl.mesh objects existed. You can render to a texture by setting

> the @capture attribute and process it with shaders via the jit.gl.slab

True that these examples are old, but here is what the problem was :
(actually just a coma missing somewhere, try to find it)
The following patch works.

> Here's another approach to the same problem.  The patch you're going
> off of uses some older techniques before the jit.gl.object or
> jit.gl.mesh objects existed.  You can render to a texture by setting
> the @capture attribute and process it with shaders via the jit.gl.slab
> object.
>
>
>
>
>
> wes


https://cycling74.com/forums/index.php?t=msg&goto=140130&rid=4892&S=98846e35a313a3381935105a31d5c2a3&srch=glreadback#msg_140130

I found this a useful start, fbo seems bettter on my setup, less cpu usage.

Quote: Kyred wrote on Sun, 17 August 2008 12:42

----------------------------------------------------

i don't believe they are officially documented anywhere, but as the above linked post describes, they determine the mechanism for performing texture readbacks. the best method to use is dependent on your particular card, so test them out and then try the jitter-config file trick that jkc mentions.

if you want to know more google opengl + RTT, Pbuffer, or Fbo

i believe ctt is the slowest, but supported by the most cards. as wes mentions in the thread, rtt and fbo may or may not be faster depending on the card.

Quote: Kyred wrote on Sun, 17 August 2008 12:42
----------------------------------------------------
> Hello,
>
> Where can we find documentation about 
>
> ; jitter glreadback
>
>
> Please.
> Thank you.
----------------------------------------------------

i don't believe they are officially documented anywhere, but as the above linked post describes, they determine the mechanism for performing texture readbacks.  the best method to use is dependent on your particular card, so test them out and then try the jitter-config file trick that jkc mentions.  

if you want to know more google opengl + RTT, Pbuffer, or Fbo
i believe ctt is the slowest, but supported by the most cards. as wes mentions in the thread, rtt and fbo may or may not be faster depending on the card.


Ok maybe this is a little off topic but...

Could cycling possibly create some sort of patching/GPU utility that Windows users can use use for setting/determining the best default jitter rendering parameters(fbo)? I upgrade my GPU quite frequently and it always is a major pain.... not to mention the sync issues... fow windows users vvvv is looking better and better every day.

Ok maybe this is a little off topic but... 

Could cycling possibly create some sort of patching/GPU utility that Windows users can use use for setting/determining the best default jitter rendering parameters(fbo)?  I upgrade my GPU quite frequently and it always is a major pain.... not to mention the sync issues... fow windows users vvvv is looking better and better every day.

We also had major sync problems with Jitter on Vista recently. It 

would be great if this problem could be solved in the near 

On Aug 22, 2008, at 12:24 AM, Tyler Nitsch wrote:

> Ok maybe this is a little off topic but...

> Could cycling possibly create some sort of patching/GPU utility that 

> Windows users can use use for setting/determining the best default 

> jitter rendering parameters(fbo)? I upgrade my GPU quite frequently 

> and it always is a major pain.... not to mention the sync issues... 

> fow windows users vvvv is looking better and better every day.

We also had major sync problems with Jitter on Vista recently. It  
would be great if this problem could be solved in the near  
future.........

>
> Ok maybe this is a little off topic but...
>
> Could cycling possibly create some sort of patching/GPU utility that  
> Windows users can use use for setting/determining the best default  
> jitter rendering parameters(fbo)?  I upgrade my GPU quite frequently  
> and it always is a major pain.... not to mention the sync issues...  
> fow windows users vvvv is looking better and better every day.
>
>
>

Telcosystems
PO box  174
3000 AD
Rotterdam
www.telcosystems.net
info@telcosystems.net


Could you send a patch / bug report to support@cycling74.com and/or

the forum? This is really the only way such issues are going to popup

on our radar and be dealt with in a timely manner.

On Fri, Aug 22, 2008 at 2:41 AM, subzero wrote:

> We also had major sync problems with Jitter on Vista recently. It would be

> great if this problem could be solved in the near future.........

> On Aug 22, 2008, at 12:24 AM, Tyler Nitsch wrote:

>> Ok maybe this is a little off topic but...

>> Could cycling possibly create some sort of patching/GPU utility that

>> Windows users can use use for setting/determining the best default jitter

>> rendering parameters(fbo)? I upgrade my GPU quite frequently and it always

>> is a major pain.... not to mention the sync issues... fow windows users vvvv

>> is looking better and better every day.

Could you send a patch / bug report to support@cycling74.com and/or
the forum?  This is really the only way such issues are going to popup
on our radar and be dealt with in a timely manner.
thanks,
wes

On Fri, Aug 22, 2008 at 2:41 AM, subzero  wrote:
> We also had major sync problems with Jitter on Vista recently. It would be
> great if this problem could be solved in the near future.........
>
> On Aug 22, 2008, at 12:24 AM, Tyler Nitsch wrote:
>
>>
>> Ok maybe this is a little off topic but...
>>
>> Could cycling possibly create some sort of patching/GPU utility that
>> Windows users can use use for setting/determining the best default jitter
>> rendering parameters(fbo)?  I upgrade my GPU quite frequently and it always
>> is a major pain.... not to mention the sync issues... fow windows users vvvv
>> is looking better and better every day.
>>
>>
>>
>
> Telcosystems
> PO box  174
> 3000 AD
> Rotterdam
> www.telcosystems.net
> info@telcosystems.net
>
>


Hello Wes, thanx for getting back. We will do this asap.

On Aug 22, 2008, at 5:38 PM, Wesley Smith wrote:

> Could you send a patch / bug report to support@cycling74.com and/or

> the forum? This is really the only way such issues are going to popup

> on our radar and be dealt with in a timely manner.

> On Fri, Aug 22, 2008 at 2:41 AM, subzero 

>> We also had major sync problems with Jitter on Vista recently. It 

>> great if this problem could be solved in the near future.........

>> On Aug 22, 2008, at 12:24 AM, Tyler Nitsch wrote:

>>> Ok maybe this is a little off topic but...

>>> Could cycling possibly create some sort of patching/GPU utility that

>>> Windows users can use use for setting/determining the best default 

>>> rendering parameters(fbo)? I upgrade my GPU quite frequently and 

>>> is a major pain.... not to mention the sync issues... fow windows 

>>> is looking better and better every day.

Hello Wes, thanx for getting back. We will do this asap.
Best Lucas

> Could you send a patch / bug report to support@cycling74.com and/or
> the forum?  This is really the only way such issues are going to popup
> on our radar and be dealt with in a timely manner.
> thanks,
> wes
>
> On Fri, Aug 22, 2008 at 2:41 AM, subzero   
> wrote:
>> We also had major sync problems with Jitter on Vista recently. It  
>> would be
>> great if this problem could be solved in the near future.........
>>
>> On Aug 22, 2008, at 12:24 AM, Tyler Nitsch wrote:
>>
>>>
>>> Ok maybe this is a little off topic but...
>>>
>>> Could cycling possibly create some sort of patching/GPU utility that
>>> Windows users can use use for setting/determining the best default  
>>> jitter
>>> rendering parameters(fbo)?  I upgrade my GPU quite frequently and  
>>> it always
>>> is a major pain.... not to mention the sync issues... fow windows  
>>> users vvvv
>>> is looking better and better every day.
>>>
>>>
>>>
>>
>> Telcosystems
>> PO box  174
>> 3000 AD
>> Rotterdam
>> www.telcosystems.net
>> info@telcosystems.net
>>
>>

opengl feedback radialblur example - going mad