BrainModular

hi,, cpu usage is spiking from panning or scrolling around in ib,, spikes to 40-60% sometimes,
anybody else noticing cpu spikes when navigating? "disabling best graphics helps a little but garbles image badly, inertia off too helps a little but not enough,,
i think this is my patch, is there a general limit using ib on how many objects or how big it is?
also is there any optimization tips for reducing these spikes? finishing up one of my projects but now noticing i cant use it because it makes audio drop out when spikes get bad

normally, those 'spikes' aren't significants because the graphic engine as a low priority.
try to reduce the /setup/refresh speed?

ps:there is no object limit in the IB

will try that and report back, thanks!

tried changing those settings, didnt really help out,, still seeing spikes of up to 60-70% when scrolling, cpu idle's at 15-20% once it goes past 60 or so audio drop outs,, pretty much drops everytime if im below 256 or 512 buffer on my soundcard,

loading demo workspaces included with demo i noticed much less actvity scrolling,, maybe 5- 10% extra and no drop outs,, just my own custom workspaces with lots of faders, knobs ect will do this,,

you think it might be something wrong im doing in my patch?

"ps:there is no object limit in the IB" please clarify,, there's no limit on how much i can add but depending on what cpu can handle? or there's no limit meaning more faders and knobs sending osc or midi shouldnt have add a heavy footprint on cpu like im seeing?

using a gma 4500 gpu on 2ghz penryn laptop, 4 gb ram, fireface 400,, set to 128 buffer,, have to relax to 256 buffer but still slight drop outs,,
any help hints or tips on optmizing my setup for performance would be greatly appreciated,,

Are you using OSC to send data between patches/software? I've noticed that OSC seems to be heavy on CPU on my system, but I could be wrong...

i have 2 patches im working on,, maybe i should post if would help and see if it does the same on other setups,,
ive also just rebuilt the win7 boot on my computer but have tested on xp pro and w7 64 so far with same results,,
both patches are basically ableton live control surfaces built for an 8" touchscreen monitor,,one's osc and other is midi
they both show the same spikes,,

first one uses midi yoke and mackie control emulation along with some midi learns and custom user script,,

second one is unfinished but is osc with lots more going on,,
good to know that osc has a heavy cpu load,, will keep that in mind

im going to build a quick one with just the faders and knobs buttons ect,, no connections and see if that spikes the same out of process of elimination...
if this behaviour can be confirmed as "not normal" seeing as i have tested on 2 builds and if can scratch out the data communication being the culprit i would then be looking somewhere betwheen the gpu on my laptop and or the touchscreen monitor itself causing this,, what you guys think?

maybe an intensive use of "rounded" function of items that refresh often use more cpu, when scrolling, have to check...
personnally i never had such dropouts onscrolling.

once i had some dropouts, i run some DCP checker found on the net, like:
http://www.tcelectronic.com/files/forum ... ol_103.zip
helped to identify audio dropouts pb.
mines where coming from wifi/bluetooth devices. killing any net activity solved my pb, but it seems you identified pb coming from
graphic part, so, still worth trying debugging killing one after the other any bg running pgm..

what's your Cpu and graphic card? also maybe try a different multithread strategy in global setup..

thanks again 23fx, i owe u beer lol!
im aware of dpc latency and doesnt seem to be the prob,, latency of 80-90 on xp (striped down version) 100-200 on windows 7,
i havent tweaked win7 too much,, fresh install,, xp is very slimed down though and does the same thing, no spikes in dpc latency when scrolling, seeing the performance from task manager,
cpu is penryn 2ghz,, 6400,, 4 gb ram, graphics is intel hd4500

gonna flip through the multithreading options and see if any magic fixes,
also just noticed the new beta uploaded! woot woot,, i guess that means some new osc features for us 23fx?
will test out that 3x module and see what else can get working,
my patch is getting so large it lags everytime i connect anything now,, normal behaviour? or maybe something related to usine on my setup