Please familiarise yourself with the forum, including policy on feature requests, rules & guidelines
Midi! Midi! MIDI! (ProgramChange, access to Instant/Quantized launch/solo/mute via midi, cc ....)
jurgis
vilniusBeta Tester Posts: 31
I'm absolutely delighted with the power, versatility and playfulness of the Deluge (WOW!), but rather frustrated with the limitations concerning MIDI access to essential functions through external midi gear. Here are some key recommendations which I think are essential:
- Midi Program change receive!: vital for those of us who use pedals (or other interfaces) to toggle through songs/programs during live setups.
- Access to both quantized and instant mute, solo, and launch of tracks in song mode. AN ABSOLUTE MUST for useful/musical external mdi control
- CC button support!
- More standardized midi implementation: this one has come up in the forums already, but is very important to ease workflow and save time. Saving songs as midi templates only partially solves the problem. I believe this is a conversation worth having again, and more in depth with the community.
Comments
Fully agree. As well the strange and limited 50 steps parameter change of all effects and filters instead of 127.
And MIDI 2.0 is comming https://www.midi.org/articles-old/details-about-midi-2-0-midi-ci-profiles-and-property-exchange
Odo Sendaidokai from Berlin
I did several similar suggestions long ago but in the preview of vs. 3.0 no changes in the midi implementation seem to be made? For me one of the biggest problems is that the cc-learning is sound-specific. Each sound has its own cc-table which is a no-go for working in a setup with ext. controllers. In my actual setup i work with 36 midi-ccs. When i change the sound all learings are gone and have do be made from scratch. Thats why i havn't worked with the Deluge since months. And indeed - 50 steps instead of 127 also sucks.
yeah, midi 2.0 will be a gamechanger, cant wait, hope there will be 2.0 hardware in the next years. not in 40 years again 😄
about the parameter step thing. really hope rohan could shed some light on this. in the xml files the hex values allow more than the displayed values as jamie and others pointed out. quickly tried before, hard to say by ear if Deluge maps every value between 0-127 to another internal value or if 0-127 gets remapped to 0-50. however, this is a good point and i really wish every non-list param simply gets a 0-127, or -63 to 63 range (and widens for env, distortion, bitcrush!). dont see a reason for these range limits.
Yeah... its a pain in the a$$..
To start to dig into the 50 vs 127 vs finer possible resolutions question, I just spent a while with a self-resonating filter (over noise) sound, external MIDI controller, gold parameter knob, black settings knob, some analysis software in VCV Rack, and a guitar tuner. I was only messing with the LPF cutoff.
My preliminary conclusion is that an external MIDI controller and a gold parameter knob yield the exact same resolution, which is 128 distinct values. The black settings knob, as is pretty obvious, yields only 50 distinct values, corresponding to the displayed 0-50 (or actually "off" for the LPF), which are evenly spread out through the 0-127 range. The settings knob's 50 values are absolute, so any "fine-tuning" to a value "between" the displayed numbers get undone by ticking the settings knob up or down by one and then back again.
In the past I thought I had heard more distinct stair-step changes when sweeping an external MIDI controller knob vs sweeping a gold parameter knob, but I couldn't find any evidence of this today.
thanks for checking out @duelinmarkers
yeah, the gold knobs are stepped for sure. as for midi control did another test with lfo speed mapped to a CC, havent compared files in an audio editor, but most certainly CCs are remapped to 50 values.
thus using the mod matrix, for example lfo to cutoff i can hear there are more values, means it doesnt “hard step”. so in general the Deluge is capable of applying more values than 0-50 to e.g. cutoff. there should be a top rated request to remove these range limitations. so interesting if rohan could explain why he has made these range limits - there might be computational reasons, maybe it was just an assumption of what users want to do, or something else. seems to me at least midi CCs really shouldnt be remapped from 128 to 51 internal values.
I want to add:
And Global Too!!!
Important to note, though, that the mapping is only in the displayed value. There really are 128 values reachable from a gold knob or MIDI CC, at least for filter cutoff, but I suspect many or maybe all learnable params.
PRETTY PLEASE!
+1 yes!
If it ever comes to complete standardised midi mapping of the deluge (which is because not existing fixed mapping is kind of a feature making the work flexible to map) i'd love if the cc numbering would be oriented on the knob matrix of the deluge.. So 'wavetable' would be cc99 counting the rows from left to right upward.
osc1 would be cc3, osc2 would be cc4 and so on..
Little problems then with cc123 which is "all-note-off" and can not be turned off to be send from (not only) Ableton while it would be TREBLE FREQ on the Deluge.
+1
I’d like to have pgm change receive option for integrating DAW projects with it as well. So when I open up a DAW project, it will send a pgm change to the Deluge, which in turn will send pgm changes to all my external gear upon loaded. This will make total recall much more easily.
👍 yeah pgm receive would make the midi implementation chart complete (let alone MTC)
allow recording and playing back sysex via a Deluge midi track.
nice idea, never thought about coupling daw and hardware like that.
though i prefer to recall hardware with sysex dumps rather than pgm. which leads to another (slightly exotic) suggestion
loved to record single patch dumps on my old MPC and never care about overwriting patches on my synths.
Also, anti echo option per track would be great!
Now I have some synths that make double notes or “stuttering” parameter sweeps upon tweaking a knob. This is because I have its midi learned to the midi clip that is instantaneously sending its midi back to the synth. These synths do not have a Local off option, or have other problems by activating it.
+1
Especially for the "entire" mode indeed, also to keep relative volumes of drums
This is the ABSOLUTE must!
more midi learns is a must, yeah. instant launch via midi would be cool. probably with quantized input because very fast multiple instant launches could cripple the cpu.
MIDI MIDI MIDI!!!
Possibility of outputting MIDI in Synth/Kit clips. For those who trigger image, light, motion, etc. and want to sync in realtime.
and/or the SHIFT key on the Deluge being Midi Mappable to midi note. This could open up a lot of these things.
This is the absolute MUST. At the moment it does not seem possible to midi-map instant launch of a clip, which is an obvious function - I believe. “Mappability” of Shift does not necessarily solve this in a convenient manner, bet anyway, upvoting Shift and begging for the ability to midi-map instant launch of a clip without cueing.
+1
MIdi improvements are a big ask from a lot of folks. Probably my biggest as well as tap to copy kit rows like we do in song mode. +1 Again for settable scaling values for cc controls. would be nice to be able to invert and set ranges with the min/max value like ableton. +++1000 for custom curves.
Dat MPE tho!
Well, midi (out) velocity would be do-able, I think.
I'd love to be able to clear a clip with the press of a foot pedal, especially since it's not currently possible to clear a clip while in the piano roll.
+1. I would love to have instant mute or track launch midi learnable. It would make the deluge work so perfectly with my other sequencer.