[chuck-users] increase chuck memory usage

Kassen signal.automatique at gmail.com
Thu Jan 26 19:34:38 EST 2012

On Thu, Jan 26, 2012 at 04:25:27PM -0800, Robert Poor wrote:

> Okay, the devil is in the details.  I actually had a fixed array of N of
> instruments, and would steal the oldest instrument if the limit was hit.  
> There are other strategies.  For example, you can have a soft limit that allow
> any number noteOn's, but start ramping down the oldest notes to keep the number
> of instruments at or below N.

Another possible optimisation is to first scan the array of running
notes for any that may have stopped playing on their own (because they
might be short samples) and prefer to first recycle those. The
annoying bit is that that would work nicely with a list but would be
annoying with a array as the new note would still have to go at the
end as it'd be the newest.

> Totally off topic, but did everyone see the paper on the new 'faster than fft'
> algorithms?  

I saw the summary. Looked like something that might apply to us. I was
hoping our MIR experts would be looking into this.


More information about the chuck-users mailing list