skrasms

I've searched every post I could find, but there isn't much detail on using Jitter inside of plug-ins and what does/doesn't work. Right now I'm trying to run the simple patch at the end of this message. So far I have had to include the following files into each build (I am on WinXP SP2):

After including all those files I no longer get any error messages when running the patch as a plug-in, but it does not work properly when the speedlim (or qlim) object is used to slow down the graphic updates. When I run it inside a VST host the jit.pwindow object freezes to a single frame. If I remove the qlim/speedlim object from the chain it runs fine but uses more CPU than I'd like. If anyone can help it would be greatly appreciated.

Here is my patch with the speedlim object bypassed:

cg.dll
cgGL.dll
jitlib.dll
all .mxe Jitter externs used

jitter-inside-pluggo-qlimspeedlim-problem

i enjoy seeing i not the only man who use jitter in pluggo !

first question : which version of Max/MSP, Jitter, and Pluggo do you use ?

i use Max 4.5.5, Jitter 1.5.2 and pluggo 3.5.4 (waiting for an update from my administrator...)

then i add the jit.fpsgui to see the refresh rate

i saw that without the qlim i reach 60fps inside the VST host ! (cubase SX) but with the qlim i couldn't go above 21,5fps...

you can also draw directly in the jit.pwindow but i've got a bug with this, the pwindow shows the right things but i can saw it in the parameter, in the pluggo info and in the message pages...

i enjoy seeing i not the only man who use jitter in pluggo !
so thanks !

first question : which version of Max/MSP, Jitter, and Pluggo do you use ?
i use Max 4.5.5, Jitter 1.5.2 and pluggo 3.5.4 (waiting for an update from my administrator...)

i tried your patch and added something.
first i've tried without adding any box.
then i add the jit.fpsgui to see the refresh rate
and then i added the qlim

you can also draw directly in the jit.pwindow but i've got a bug with this, the pwindow shows the right things but i can saw it in the parameter, in the pluggo info and in the message pages...
i hope it was fixed now...

Jitter inside Pluggo (qlim/speedlim problem)