Feature idea: MIDI CCs from external controller

[robman84]

Unless I'm mistaken, the current version doesn't respond to MIDI CCs other than mod wheel, hold, aftertouch and expression. It would be fantastic if it could respond to all of the relevant (standard) CC numbers and map them accordingly. So things like ADSR, cutoff, resonance, reverb, chorus, portamento, pan etc. Then the others (e.g. breath, soft and the rest of the general ones) could be part of the mod matrix.

Also helpful would be responding to program change (0...127) and MMC messages (start/stop/record/ff/rw)

[kurogedelic]

Good idea. Right now Felucca responds to pitch bend, the sustain pedal (CC64), the mod wheel (CC1), expression (CC11) and aftertouch, the last three as sources in the MOD matrix. A fixed map for the standard CCs (cutoff 74, resonance 71, attack 73, release 72, pan 10, reverb 91, chorus 93, portamento) is noted for 1.1.

[abelnation]

It would be rad if some N cc values were reserved for the synth engine, with each synth engine mapping that range to it's own engine-specific params. the midi cc handling logic would look at the ch to determine the engine, then route it to the appropriate engine param.

[planist79]

+1

First: Standard CCs
Then: Free assignable CCs so we can use external MIDI Controllers to control the parameters of the various engines

this would be great!

[kurogedelic]

A fixed CC map is in Felucca 1.1.5: https://github.com/hugelton/Felucca/releases/tag/v1.1.5

It's always on and follows ROUT like notes: 5 GLIDE, 7 LEVEL, 10 PAN, 71 resonance, 72 release, 73 attack, 74 brightness (the cutoff, or the closest thing the engine has), 75 decay, and 91 / 93 / 94 for the reverb, chorus and delay sends. A CC moves the value just like its knob, and while the track is selected, armed and playing, AUTOMATION records it.

Thanks @robman84 (and @planist79 for the +1)! Freely assignable CCs are still on my list. I'll close this one for the standard map.