Garrett

Getting some performance issues in jitter in some visuals that I have only just started building. Not sure whether this is jitter or opengl but I thought it may be because I was using metro. Someone suggested I use the cpuclock object (as demonstrated in the Animator receipe here: 

https://cycling74.com/story/2006/2/17/153427/406)

 but it does not seem to make any difference. When I rotate a shape I get a slight judder / it pauses very briefly. Is there some way to eliminate this? Any techniques to manage animation more efficently to improve speed? Or am I missing something completely in how this is done?

I've included my patch below, when you launch it turn it on and click into the patcher triangleshapes to access controls to turn on and rotate / move / scale an ellipse.

Getting some performance issues in jitter in some visuals that I have only just started building.  Not sure whether this is jitter or opengl but I thought it may be because I was using metro.  Someone suggested I use the cpuclock object (as demonstrated in the Animator receipe here: https://cycling74.com/story/2006/2/17/153427/406) but it does not seem to make any difference.  When I rotate a shape I get a slight judder / it pauses very briefly.  Is there some way to eliminate this?  Any techniques to manage animation more efficently to improve speed?  Or am I missing something completely in how this is done?

jitter-judder

Some jitter judder is unavoidable, but getting rid of the numberboxes 

inside your subpatches that are unnecessary (like the one before 

counter in the shape timer subpatch) will help greatly. Even a few 

numberboxes slow things down, and gui elements run at different 

scheduler rates than max control data (correct me if I'm wrong on 

Some jitter judder is unavoidable, but getting rid of the numberboxes  
inside your subpatches that are unnecessary (like the one before  
counter in the shape timer subpatch) will help greatly.  Even a few  
numberboxes slow things down, and gui elements run at different  
scheduler rates than max control data (correct me if I'm wrong on  
that for numberboxen).

sadly i've come to this conclusion as well as I've not fully resolved the issue.

>inside your subpatches that are unnecessary

yep it does indeed help but not eliminate the problem. from more testing I think the judder only seems to be there on things that are constantly moving (at a constant speed) i.e. rotation / horizontal or vertical movement.

i've also noticed that the judder seems to happen on rotation at approximately every 45 degrees, could how simple gl shapes are transformed be an issue here as well?

any other tips anyone has got to improve speed and minimise judder would be greatly appreciated.

>getting rid of the numberboxes
>inside your subpatches that are unnecessary

yep it does indeed help but not eliminate the problem.  from more testing I think the judder only seems to be there on things that are constantly moving (at a constant speed) i.e. rotation / horizontal or vertical movement.

I for one see no judder. I would recommend changing the use of

jit.gl.render's textures to a jit.gl.texture object. You'll have more

control and flexibility that way. Also, you're running your qmetry at

0.5. I don't know why, but you'll need a max of qmetro 15 and more

I for one see no judder.  I would recommend changing the use of
jit.gl.render's textures to a jit.gl.texture object.  You'll have more
control and flexibility that way.  Also, you're running your qmetry at
0.5.  I don't know why, but you'll need a max of qmetro 15 and more
han likely qmetro 25 will suffice.

>I for one see no judder. I would recommend changing the use of

>jit.gl.render's textures to a jit.gl.texture object. You'll have >more control and flexibility that way.

it is there but I'm guess different machines / graphics cards will make it less / more noticeable.

>0.5. I don't know why, but you'll need a max of qmetro 15 and more

yep but that came from that tutorial the Animator from the jitter recipes, it's there not sure why its not about 20 but it gives a much higher frame rate (50-60). when i do change it to 25 i only get a frame rate of 30.

>I for one see no judder. I would recommend changing the use of
>jit.gl.render's textures to a jit.gl.texture object. You'll have >more control and flexibility that way. 

it is there but I'm guess different machines / graphics cards will make it less / more noticeable.
are textures faster than simple colours?

>Also, you're running your qmetry at
>0.5. I don't know why, but you'll need a max of qmetro 15 and more
>han likely qmetro 25 will suffice.

yep but that came from that tutorial the Animator from the jitter recipes, it's there not sure why its not about 20 but it gives a much higher frame rate (50-60).  when i do change it to 25 i only get a frame rate of 30.

> it is there but I'm guess different machines / graphics cards will make it less / more noticeable.

> are textures faster than simple colours?

Depends. I just noticed you had some texture stuff in your patch even

> >0.5. I don't know why, but you'll need a max of qmetro 15 and more

> yep but that came from that tutorial the Animator from the jitter recipes, it's there not sure why its not about 20 but it gives a much higher frame rate (50-60). when i do change it to 25 i only get a frame rate of 30.

That doesn't sound right to me. In my experience, you will get an fps

of 1/metro_ms unless your processing is too heavy. Try adjusting your

performance settings like queuethrottle etc. and see if that helps.

So what OS/CPU/GPU are you on? Your patch is really simple, I'd be

> it is there but I'm guess different machines / graphics cards will make it less / more noticeable.
> are textures faster than simple colours?
>

Depends.  I just noticed you had some texture stuff in your patch even
though it wasn't being used.  That's all.

>
> >Also, you're running your qmetry at
> >0.5. I don't know why, but you'll need a max of qmetro 15 and more
> >han likely qmetro 25 will suffice.
>
> yep but that came from that tutorial the Animator from the jitter recipes, it's there not sure why its not about 20 but it gives a much higher frame rate (50-60).  when i do change it to 25 i only get a frame rate of 30.

That doesn't sound right to me.  In my experience, you will get an fps
of 1/metro_ms unless your processing is too heavy.  Try adjusting your
performance settings like queuethrottle etc. and see if that helps.
So what OS/CPU/GPU are you on?  Your patch is really simple, I'd be
surprised if it couldn't be made smooth.

>Depends. I just noticed you had some texture stuff in your patch >even though it wasn't being used. That's all.

ah ok, I had been testing some textures but then simplified when this issue arose - just forgot to disconnect the cord.

>That doesn't sound right to me. In my experience, you will get an >fps of 1/metro_ms unless your processing is too heavy. Try >adjusting your

>performance settings like queuethrottle etc. and see if that helps.

sorry for being thick, what's queuethrottle? - is it in the performance settings unders options? Overdrive seems to help a bit.

>So what OS/CPU/GPU are you on? Your patch is really simple, I'd be

>surprised if it couldn't be made smooth.

1.8 Gz PowerPC G5 OSX 10.4.10, 1.5 GB DDR SDRAM

my performance machine is an intel mac (same system) so that will improve things as well - need to test that actually.

>That doesn't sound right to me. In my experience, you will get an >fps of 1/metro_ms unless your processing is too heavy. Try >adjusting your
>performance settings like queuethrottle etc. and see if that helps.

sorry for being thick, what's queuethrottle? - is it in the performance settings unders options?  Overdrive seems to help a bit.

>So what OS/CPU/GPU are you on? Your patch is really simple, I'd be
>surprised if it couldn't be made smooth.

1.8 Gz PowerPC G5 OSX 10.4.10, 1.5 GB DDR SDRAM
my performance machine is an intel mac (same system) so that will improve things as well - need to test that actually.

> >That doesn't sound right to me. In my experience, you will get an >fps of 1/metro_ms unless your processing is too heavy. Try >adjusting your

> >performance settings like queuethrottle etc. and see if that helps.

> sorry for being thick, what's queuethrottle? - is it in the performance settings unders options? Overdrive seems to help a bit.

> >That doesn't sound right to me. In my experience, you will get an >fps of 1/metro_ms unless your processing is too heavy. Try >adjusting your
> >performance settings like queuethrottle etc. and see if that helps.
>
> sorry for being thick, what's queuethrottle? - is it in the performance settings unders options?  Overdrive seems to help a bit.
>
>