@ethancrawford thank you for this. yes I meant the instance of sample, so thank you for the correction.
control offer a potential solution here? One hack could be to control playback via
amp: modification i.e. shuttle between values of off/on.
I think the way that Sam has solved the problem of concurrency is amazing. It works. I’ve programmed a version of Riley’s In C for 40 players, which is great. Still got some bits to iron out, such as knowing when to stop! What’s also amazing is that I can run the program at a tempo most musicians can’t play the piece at. Produces a whole new set of results for my own curiosity. If I had to build the whole thing in Supercollider, I think I’d be a bit less enthused. Sam has done the heavy lifting, and I am for one am highly appreciative.
In roughly four months from now, I’ll be incorporating SPi into my performance teaching work. Something I could not say, if using Supercollider. The ‘useable by a 10 year old’ philosophy works on so many levels and is one of the reasons why I feel confident to be able to use SPi with my performance students, especially where the assessment criteria require an engagement with technology to be built into their practice. A DAW is sometimes not the right solution and Live Coding opens the door to so many other discipline areas, whether building from scratch or modifying/varying values/code. SPi runs on the main platforms, on modest computers, something DAWs will find challenging.