Notifications
Clear all
Topic starter
December 24, 2022 7:30 pm
So I'm working on a Library for windcontrollers and I sent my first beta to my first beta tester. 🙂 The first thing we noticed is that his Knob CC assignments were different than mine. I sent him a preset of my CC Assignments and that worked. But it made me wonder if there were a way to save the Knob's CC assignments to each Preset or maybe even to a whole Library? That would mitigate the problem that very user would have their own knob CCs. Or should I just include the CC Assignment Preset and have them load it after loading the Library?
thanks,
robo
Â
December 24, 2022 8:08 pm
You should create one or more CC Assignments Preset, one for each distinct wind controller that you want to support. (I don't know anything about wind controllers. If every single one on the market uses the identical set of CC's, you would only need one preset.)
Since Unify remembers the knob/CC assignments from one session to the next, most users would only need to load the appropriate preset for their controller once, and would only need to re-load it if they change the knob/CC assignments (e.g. to use another kind of MIDI controller).
When you get to the stage where you're ready to make a .guru file for your library, I can advise you on how to include these preset(s).
Topic starter
December 24, 2022 9:07 pm
Yeah, a Windcontroller Knobs Preset is the way to go. Every windcontroller sends Breath, but each one has various other CCs they send. I'm making one bank of Knobs to cover all the bases for every windcontroller. For example, one windcontroller sends Mod, another sends CC4, and a 3rd sends AT. Each of the different Knobs would do the same thing (i.e. growl) and it won't matter which windcontroller is played because all will be assigned in that one CC Assignment Preset.
Thanks again, Shane!
robo
getdunne reacted
