Supercollider front end

[Marc Nostromo [M-.-n]]

Actually, for managing the sources of data, I've got quite an elegant system
that uses something I call "Controller sources"

Typically you use it like this:

Channel *c=ControllerService::Instance()->GetChannel("midi:all:0:cc:14") ;
assert(c) ;
synth_.AttachParameter(SQ_OSC_START,c) ;

the string is simply describing the source of the data. Can be joystick,
midi, keyboard, osc.. pretty much anything. It's also very handy to be able
to design variable mapping, midi learn etc :)


2011/8/29 Joost Schuttelaar <joost at joostschuttelaar.nl>

> On Aug 29, 2011, at 16:35 , Marc Nostromo [M-.-n] wrote:
>
> > My biggest challenge (beside writing the modules of course) left is to
> tackle parameter access. First of all module can have a large set of them
> but then the "synth" might want to expose only some of them to map to MIDI
> for example. I haven't really spent the time to do a proper desing for that.
>
> I've struggled with this one too. My model is something like below:
>
> MGEPiggyOsc implements Tweakable {
>
>        void oscFloatMessage(char * message, float value); // values in
> 'real-world'
>        void midiMessage(int param, byte val); // values mapped nicely to
> MIDI bytes where 0 makes sonic sense and 127 too
>        void midiFloatMessage(int param, float val); // values mapped to
> real-world again, can be very non-musical
>        void char * describe(); // returns an xml description of
> parameters/values
> }
>
> --
>
> Joost Schuttelaar
> The Hague, NL
>
> _______________________________________________
> music-bar mailing list
> music-bar at lists.music-bar.org
> http://lists.music-bar.org/cgi-bin/mailman/listinfo/music-bar
>



-- 
http://nostromo.noisepages.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.music-bar.org/pipermail/music-bar/attachments/20110829/4c98bc79/attachment-0002.html>