On Dec 31, 2013 2:22 AM, "Philip Galanter" <list@xxxxxxxxxxxxxxxxxx> wrote:
>
> Thanks for the response James. Unfortunately this project has lots of moving parts and Supercollider is just one of them. I have to just use it as it's bundled into CRRMA's Satellite distribution (https://ccrma.stanford.edu/~eberdahl/satellite/) and not get into activities lower than the user level.
Hm... at user level, you could make another copy of the SC class library under the user's directory (anywhere) and then use LanguageConfig to tell SC to use the copy, not the packaged one. I guess that's not too helpful if you need to make a lot of the devices and other people are involved. But, it's worth pointing out that SC already has an option to use a class library location not owned by root.
> I'll make do. But please consider making this apparently one line fix in a future release.
A one-line tweak in one user's environment is trivial. The wrong one-line fix forced on all users may be worse. (It's a one-line "fix" that broke variants in events, after all.)
So here are the options:
1. Specify variants using ==\instrument, "defname.variant"== only. Much more convenient if the pattern should always use the same variant; much less convenient if you want to choose a different variant per event. So I don't like this idea if it's going to replace #2 or #3.
2. If \variant is given in the event, append it to the instrument name in all cases, even if the SynthDef has no variants. Drawback: 'variant' would become a reserved word, unavailable for SynthDef argument names.
3. Check the SynthDesc to see if the def has variants before appending to the instrument name. Then you can use variant as an argument name if the def doesn't have variants. Drawback: A bit more complex.
I don't think we quite reached consensus, but I'll reread the latest thread in a few days (after a performance is over and my grades are in) and try to do something.
hjh