Michael Hastings

Now I don't know how to really go about asking this, so bare with me (and feel free to ask for clarification!)

I have a large patch to load (e.g. lots of .aiff files getting "replaced" into buffers), and while it's loading, I would love to have a much smaller patch be able to be loaded first that says "loading..." (cute, huh?) I eventually would have this whole deal boiled down to an app. You know? 

The problem I'm having, of couse, is that all the computer's thinking power is being used to load the really big patcher file. Is there a way to limit the cpu allowed to load a patcher file on first start up of that file, or at least let the smaller one run smoothly while the big one loads?

Thanks for any help or at least stopping to look.

Hello Cycling 74 Community! 
Now I don't know how to really go about asking this, so bare with me (and feel free to ask for clarification!) 

I have a large patch to load (e.g. lots of .aiff files getting "replaced" into buffers), and while it's loading, I would love to have a much smaller patch be able to be loaded first that says "loading..." (cute, huh?) I eventually would have this whole deal boiled down to an app. You know? 
The problem I'm having, of couse, is that all the computer's thinking power is being used to load the really big patcher file. Is there a way to limit the cpu allowed to load a patcher file on first start up of that file, or at least let the smaller one run smoothly while the big one loads?

Thanks for any help or at least stopping to look.


limiting-cpu-while-loading-patch

On Dec 20, 2006, at 9:05 PM, Michael Hastings wrote:

> I have a large patch to load (e.g. lots of .aiff files getting 

> "replaced" into buffers), and while it's loading, I would love to 

> have a much smaller patch be able to be loaded first that says 

> "loading..." (cute, huh?) I eventually would have this whole deal 

> The problem I'm having, of couse, is that all the computer's 

> thinking power is being used to load the really big patcher file. 

> Is there a way to limit the cpu allowed to load a patcher file on 

> first start up of that file, or at least let the smaller one run 

I don't know of any ways to selectively throttle the CPU use, but 

here are a couple alternatives that might work:

- use the smaller "loading" patch as a wrapper for the larger patch 

in a [p largepatch], then automatically open the larger patch in the 

- go only with the larger patch but pace your buffer loads 

sequentially, updating a progress meter of some sort as they roll 

along. The right outlet bang when [buffer~] finishes a read is a big 

help here. I've used this approach to give visual feedback in 

several apps that needed to load lots of audio files.

> I have a large patch to load (e.g. lots of .aiff files getting  
> "replaced" into buffers), and while it's loading, I would love to  
> have a much smaller patch be able to be loaded first that says  
> "loading..." (cute, huh?) I eventually would have this whole deal  
> boiled down to an app. You know?
> The problem I'm having, of couse, is that all the computer's  
> thinking power is being used to load the really big patcher file.  
> Is there a way to limit the cpu allowed to load a patcher file on  
> first start up of that file, or at least let the smaller one run  
> smoothly while the big one loads?

I don't know of any ways to selectively throttle the CPU use, but  
here are a couple alternatives that might work:

- use the smaller "loading" patch as a wrapper for the larger patch  
in a [p largepatch], then automatically open the larger patch in the  
foreground once it is fully loaded.

- go only with the larger patch but pace your buffer loads  
sequentially, updating a progress meter of some sort as they roll  
along.  The right outlet bang when [buffer~] finishes a read is a big  
help here.  I've used this approach to give visual feedback in  
several apps that needed to load lots of audio files.

http://www.daevlmakr.com
http://www.2secondfuse.com


Limiting cpu while loading patch?