Re: [chuck-users] Machine.add() (.yield) from mike clemow

Depending on how HUGE the SndBuf files are, I have often loaded all of the files sequentially at the beginning, before I make any sound at all, into a single SndBuf, not to play them, but to get them into the cache. Then when the time comes to truly load them, they can be zero-disk loads. If they’re too big, this won’t work of course because you’ll exhaust your cache. PRC

Hi Perry,
I thought about doing this but wanted the solution to scale in case the
files were really huge or there was an overwhelming number of them. I've
noticed that this is a great approach when you need things to happen
immediately when they are called, however, the timing in this application
is loose so, I'd rather buy the time I need to load the files from the disk
on demand than be limited by the size of the cache.
I'm assuming that this "cache" is in memory... what are the effective
limitations here? Assuming a 64bit OS for now, are we basically just
limited by the availability of RAM on the system? Or is are there limits
set in the Chuck executable?
Best,
Mike
--
Michael Clemow
Artist/Composer/Sound Designer
http://michaelclemow.com
(he/him)
On Thu, Jul 2, 2020 at 6:48 PM Perry Cook
participants (2)
-
mike clemow
-
Perry Cook