|
From: Josh G. <jg...@us...> - 2003-01-21 19:48:48
|
On Tue, 2003-01-21 at 07:45, David Olofson wrote: > On Tuesday 21 January 2003 13.41, M. Nentwig wrote: > > Moi, > > > > I don't think that there are any restrictions concerning velocity > > mapping with Swami. You can assign samples to arbitrary note and / > > or velocity 'windows'. In theory it's possible to have a different > > sample for each key / velocity combination (but I'd bet nobody has > > tried that yet :) > > <plug qualifier="shameless"> > How about being able to write C-like code that calculates or > otherwise determines mapping when a note is started? > > Well, whether or not it's really useful, this is where Audiality is > going. Processing timestamped events in C is a bit hairy, so I'd > prefer using a custom higher level language for that. Another point > is that strapping on a scripting engine eliminates lots of hardcoded > logic, and the restrictions that come with it. > </plug> > > <plug qualifier="also shameless"> Yes, I can envision Python being a nice language for this type of thing. A project for the future of Swami as well. As things stand now modulators can be used with MIDI velocity source controls to do weired mappings with velocity (can even control other effects, say Filter Cutoff for instance :) </plug> |