matteopennese

crazy cpu if I open storagewindow during preset interpolation:

this behaviour freezed my pather while running about 34% cpu (activity monitor, not max dsp window).

So I created a simple patcher to test it and these are the result:

no interpolation: cpu (activity monitor) 4,3%

if I open storagewindow during interpolation (or just opened): cpu about 46% !!!

with storagewindow and clientwindow opened during interpolation: cpu about 60,5%

A little bit more complicated patcher kills the cpu, of course. 

A little bit more complicated patcher kills the cpu, of course. 
I suppose that isn't normal...

maxmsp 5.0.5
jitter 1.7
Imac Intel Core 2 Duo 3.06 GHz
OsX 10.5.5
Ram 4G

crazy-cpu-if-i-open-storagewindow-during-preset-interpolation

mmmh... no answer (also by support@cycling).

- without storagewindow open at interpolation: cpu at 8-9%

- storagewindow open at interpolation: Max-FREEZE

18 presets (20 params stored).
- without storagewindow open at interpolation: cpu at 8-9%
- storagewindow open at interpolation: Max-FREEZE

I can confirm the CPU usage issue. But this isn't probably going to change any time soon, so i'd strongly recommend making sure that your client and storage windows are closed while changing client object values.

I can confirm the CPU usage issue.  But this isn't probably going to change any time soon, so i'd strongly recommend making sure that your client and storage windows are closed while changing client object values.

I've always found having storagewindows open to slow down Max 

incredibly -- I always just keep 'em closed unless I'm desperate....

On Nov 17, 2008, at 15:16, Ben Bracken wrote:

> I can confirm the CPU usage issue. But this isn't probably going to 

> change any time soon, so i'd strongly recommend making sure that 

> your client and storage windows are closed while changing client 

I've always found having storagewindows open to slow down Max  
incredibly -- I always just keep 'em closed unless I'm desperate....

>
> I can confirm the CPU usage issue.  But this isn't probably going to  
> change any time soon, so i'd strongly recommend making sure that  
> your client and storage windows are closed while changing client  
> object values.
>
> -Ben
>
>


Some of you may recall that scene in Star Wars IV where Obi-Wan Kenobi initiates Luke Skywalker's training with a lightsaber by using a blast shield helmet as a blindfold, urging him to learn to "feel the force flow through you."

"The true Jedi is not seduced by Max eye candy. As she becomes more adept at sensing The Force, the UI object gradually disappear from her performance patch; controls move from the screen to your fingers on the external controller of your choice, and the feedback loop moves from your screen to your eyes to your ears. What is not essential withers away, and while the subspace ethers ebb and flow with whingeing from the Death Star staff about blinky lights, the Jedi just *plays.*"

I have experienced this problem as well...

Solution: close storage windows when performing or when not needed.

> "The true Jedi is not seduced by Max eye candy. As she becomes more

> adept at sensing The Force, the UI object gradually disappear from

> her performance patch; controls move from the screen to your fingers

> on the external controller of your choice, and the feedback loop

> moves from your screen to your eyes to your ears. What is not

> essential withers away, and while the subspace ethers ebb and flow

> with whingeing from the Death Star staff about blinky lights, the

Gregory Taylor schrieb:
> "The true Jedi is not seduced by Max eye candy. As she becomes more
> adept at sensing The Force, the UI object gradually disappear from
> her performance patch; controls move from the screen to your fingers
> on the external controller of your choice, and the feedback loop
> moves from your screen to your eyes to your ears. What is not
> essential withers away, and while the subspace ethers ebb and flow
> with whingeing from the Death Star staff about blinky lights, the
> Jedi just *plays.*"

-- 
Les Ondes Memorielles----x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()----------TJ Shredder


exactly same here. opening the storage window when playing a movie and the fps fall to 4 !!!

> exactly same here. opening the storage window when playing a movie and the fps

Pattr Rule Number 1: never open the storage or client window when your patch

is running (DSP on or metro->processing...).

> exactly same here. opening the storage window when playing a movie and the fps
> fall to 4 !!!

Sounds OK. 
Pattr Rule Number 1: never open the storage or client window when your patch
is running (DSP on or metro->processing...).
J-F.