[chuck-users] Raspberry pi and ChucK and performance

[Perry Cook]

Thoughts from the battlefield:

One nice thing about the Pi is that it supports many 
sample rates.  So if you can run at 22.05k or even 
16k or less, then you'll get much more bang for 
your buck.  

Also, you might look into using WvIn (non looping)
or WavLoop (looping), rather than SndBuf, because
I think I remember that these are slightly more 
efficient.

Look into using some long delay lines (non-interpolating),
with feedback.  These can really fatten up a texture without
requiring much CPU.

Also be judicious about your efx, some will take more
CPU than others.

Finally, if a wave is not playing sound, unchuck it at the
end of the chain, and it won't use any CPU while muted.
Keeping track of what's actually sounding, and muting 
the rest (by unchuck) can really help.

Prc

Sent from my iPad :-)

> On Jan 11, 2014, at 3:03 PM, chuck-users-request at lists.cs.princeton.edu wrote:
> 
> Raspberry pi and ChucK and performance