Anna

I'm very new to jitter, trying to work my way through tutorials and such. I've been working on a video patch for a few months, trying to combine math op/crossfading and chromakeying, as well as some pixelation and looping techniques. Anyways, though this patch works just fine, my macbook can't handle all these processes. Is there a way to increase the efficiency of this patch and decrease how intensive it becomes on my computer? I really appreciate any help people can provide me, as well as your patience with my inexperience!

Here's the patch: (ignore the midi info and video names)

I'm very new to jitter, trying to work my way through tutorials and such.  I've been working on a video patch for a few months, trying to combine math op/crossfading and chromakeying, as well as some pixelation and looping techniques.  Anyways, though this patch works just fine, my macbook can't handle all these processes.  Is there a way to increase the efficiency of this patch and decrease how intensive it becomes on my computer?  I really appreciate any help people can provide me, as well as your patience with my inexperience!
Here's the patch:  (ignore the midi info and video names)

newbie-help-2

You have a lot of updating number boxes, which are very bad for your 

framerate (any frequently updating UI objects are). Get rid of them 

or use [qlim] if you need them for display. The same thing goes for 

your jit.pwindows -- eliminate them or [qlim] them. Use only 1 metro 

and [trigger b b] to drive all your processing. You may have other 

performance issues in your abstractions (e.g., [briconsat2]) so 

remove those and simplify the patch if you'd like us to have a look.

Also, you might want to try an [ubumenu] to select your movies, too 

You have a lot of updating number boxes, which are very bad for your  
framerate (any frequently updating UI objects are).  Get rid of them  
or use [qlim] if you need them for display.  The same thing goes for  
your jit.pwindows -- eliminate them or [qlim] them.  Use only 1 metro  
and [trigger b b] to drive all your processing.  You may have other  
performance issues in your abstractions (e.g., [briconsat2]) so  
remove those and simplify the patch if you'd like us to have a look.

Also, you might want to try an [ubumenu] to select your movies, too  
-- it would simplify things.

scuse me I have kind the same problem, i mean low frame rate, the patch it's not so complicated (i think) but i get a framerate around 12 13 fps, that is low for what i need and considering that i'd like to implement some effect like color filter or something

i work with a powerbook g4 512mb RAM, do you think that will consioderably change with 2 giga? i'm buying it 

and working with MOV file with jpeg compression. I've noticed that till now is the compression that works best.

I've tryed with the qlim as you told but i don't see particular chenge, maybe i've used it worng

here's my patch, PLEASE if you have 5 minute could you give it a look?

i work with a powerbook g4 512mb RAM, do you think that will consioderably change with 2 giga? i'm buying it 
and working with MOV file with jpeg compression. I've noticed that till now is the compression that works best.

newbie help