The early beta version after I learned how Ctrlr handles the dataflows:
/Update: The panel can be downloaded from this location: http://www.ucapps.de...FM_V1_5.bpanelz
(Note: the panel located in the Ctrlr Device Database is expired! It will be updated once the new repository system is available)
Please note that the panel will only work with Ctrlr r1209 or higher!
I've hosted "known good version" on the uCApps server:
/Update2: Drum edit panel:
A complete implementation with access to all parameters is feasible, especially since Ctrlr supports LUA as a scripting language.
Example: following code handles the OPx flags, which are located in a single parameter at different bit positions:
OP1Flags = function(modulator, newValue) op = "OP1" flagSustain = panel:getModulatorByName(op .. "SustainFlag") flagVibrato = panel:getModulatorByName(op .. "VibratoFlag") flagTremolo = panel:getModulatorByName(op .. "TremoloFlag") if flagSustain ~= nil and flagTremolo ~= nil and flagVibrato ~= nil then value = 0 value = value + 2 * flagSustain:getModulatorValue() value = value + 4 * flagVibrato:getModulatorValue() value = value + 8 * flagTremolo:getModulatorValue() sat = panel:getModulatorByName(op .. "FlagsSatellite") if sat ~= nil then notify_vst_host = false notify_midi_device = true notify_component = true sat:setModulatorValue(value, notify_vst_host, notify_midi_device, notify_component) end end end
At the end scripting the combined parameters is much less effort than writing the whole application by myself!
Especially since we will inherit all these nice Ctrlr features such as Windows/Mac/Linux compatibility, support for VST, AU and Standalone mode, etc.
The GUI design is very simple, because I'm not good at graphics.
Is anybody interested on helping with the graphics? See following page for inspirations: http://www.ctrlr.org/page.php?p=ddb
Best Regards, Thorsten.