[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [sc-dev] Towards SC 4
On 12.11.2013, at 05:39, James Harkins <jamshark70@xxxxxxxxx> wrote:
> Sure. In a ProxySpace, you can plug and play bits of the synthesis graph more or less at will. Now, if you want to play an arbitrary number of copies of a ProxySpace configuration, you have to figure out the instructions that led to that state and replay them in a new ProxySpace. And I believe you'll be responsible for tracking the end of that event and releasing the structure manually.
>
> What I'm dreaming of is a way to play patterns with overlapping synthesis events and have the option to switch around parts of the graph (as is easy, monophonically, in jitlib now), but *per event*, and as transparently to the user as playing overlapping events with a simple SynthDef. A component-ized SynthDef, if you will.
>
> I have a custom event type that does this in a limited way for control inputs, but it's far from a general solution, a bit cumbersome, and not NRT friendly.
>
I've thought about this often, too. One thing that has stopped me was actually the question of how to specify such things in code (from a "user" side) concisely. Do you have ideas about that?
I am sure you know that you can use patterns in NodeProxy as well as spawn any number of synths in it. NodeProxies in themselves are fairly lightweight objects, so there is no reason one shouldn't create them on a note by note basis. But what you are getting at is a different way of expressing polyphony.
_______________________________________________
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/