# MIDI Learn

**URL:** <https://unity.neuraldsp.com/t/midi-learn/9577>\
**Category:** Feature Requests\
**Created:** [January 24, 2023, 10:38am UTC](https://unity.neuraldsp.com/t/midi-learn/9577 "2023-01-24T10:38:39Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![thomasotto](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/thomasotto/32/4210_2.png) [@thomasotto](https://unity.neuraldsp.com/u/thomasotto)\
**Post date:** [January 24, 2023, 10:38am UTC](https://unity.neuraldsp.com/t/midi-learn/9577/1 "2023-01-24T10:38:39Z")

</div>

Please add **MIDI learn** to the QC.  
The current MIDI CC map is very restrictive.  
I wish I could **control block parameters via MIDI** and expand usage with external MIDI expression pedals , potentiometers or switches (even sensors _à la_ Kaoss Pad)

---

<div class="post-metadata">

**Author:** ![MaxF](https://avatars.discourse-cdn.com/v4/letter/m/779978/32.png) [@MaxF](https://unity.neuraldsp.com/u/MaxF)\
**Post date:** [January 24, 2023, 10:49am UTC](https://unity.neuraldsp.com/t/midi-learn/9577/2 "2023-01-24T10:49:02Z")

</div>

Wow, just came back here to request the same! x)  
I just realised how restricted the QC is regarding remote control options.  
I’d like to assign CCs to parameters or bypass, so I can for example turn blocks on and off via MIDI.  
What good is having all that DSP and multiple FX blocks when I can’t switch them freely and am restricted to 8 scenes or footswitches. HX control, Boss midi, Axe Fx… way way ahead here.

---

<div class="post-metadata">

**Author:** ![RexRemus](https://avatars.discourse-cdn.com/v4/letter/r/e274bd/32.png) [@RexRemus](https://unity.neuraldsp.com/u/RexRemus)\
**Post date:** [January 24, 2023, 4:27pm UTC](https://unity.neuraldsp.com/t/midi-learn/9577/3 "2023-01-24T16:27:27Z")

</div>

You are able to use the MIDI EXP1/2 CCs to map to any parameter on any block pretty much - so you can control things via MIDI expression today.

You can also (for at least moderately simple use cases) use the expression CCs for bypass/toggles.

That being said, the QC has a long way to go as far as MIDI implementation but I am hoping we will see some changes in the 2.x series of releases with things like direct block access and control, and extended access to things like input and output volumes via MIDI

---

<div class="post-metadata">

**Author:** ![thomasotto](https://sea2.discourse-cdn.com/flex020/user_avatar/unity.neuraldsp.com/thomasotto/32/4210_2.png) [@thomasotto](https://unity.neuraldsp.com/u/thomasotto)\
**Post date:** [January 24, 2023, 4:50pm UTC](https://unity.neuraldsp.com/t/midi-learn/9577/4 "2023-01-24T16:50:12Z")

</div>

Hey @RexRemus ,

Thanks for your input, I did know you can already do basic MIDI implementation (via a [DIY MIDI Switcher](https://unity.neuraldsp.com/t/diy-midi-switcher/9555)).  
But so far it’s pretty limited.

I was just hoping that, with sufficient votes (ie : sufficient people needing expanded MIDI functionalities) we could see the Quad Cortex become a fully fledged gigging beast.

Imagine the simple process of long pressing a block parameter (Midi learn), then pressing your switch or expression knob on your favorite controller and… voilà ! Assigned !

---

<div class="post-metadata">

**Author:** ![RexRemus](https://avatars.discourse-cdn.com/v4/letter/r/e274bd/32.png) [@RexRemus](https://unity.neuraldsp.com/u/RexRemus)\
**Post date:** [January 24, 2023, 6:09pm UTC](https://unity.neuraldsp.com/t/midi-learn/9577/5 "2023-01-24T18:09:49Z")

</div>

Definitely agree, it has a way to go, and this is a solid feature request. Just pointing out that you can do “some” things today, even if imperfect. But I agree it can be significantly better and more powerful than it currently is

---

<div class="post-metadata">

**Author:** ![john987](https://avatars.discourse-cdn.com/v4/letter/j/c89c15/32.png) [@john987](https://unity.neuraldsp.com/u/john987)\
**Post date:** [July 18, 2023, 1:07am UTC](https://unity.neuraldsp.com/t/midi-learn/9577/6 "2023-07-18T01:07:58Z")

</div>

There should be at least 16 knobs that one can centrally map (not just 2 expression midi controllers). And then have those 16 knobs assigned in each preset across FX. So one only needs to “midi learn” 16 once.  
Also ideally there would be some support to get the names/labels of each of those knob parameters over MIDI (Sysex messages, MCU or similar)

---

<div class="post-metadata">

**Author:** ![john987](https://avatars.discourse-cdn.com/v4/letter/j/c89c15/32.png) [@john987](https://unity.neuraldsp.com/u/john987)\
**Post date:** [August 9, 2023, 9:22pm UTC](https://unity.neuraldsp.com/t/midi-learn/9577/7 "2023-08-09T21:22:46Z")

</div>

Setting MIDI channel, cc# for the existing 2 incoming expression pedal MIDI mappings would help to.  
16+ of such preset mappings would be good to have.  
Also assigning “expression pedals” to filters should takes less steps. Maybe a long press on the parameter would be more intuitive?

---

<div class="post-metadata">

**Author:** ![john987](https://avatars.discourse-cdn.com/v4/letter/j/c89c15/32.png) [@john987](https://unity.neuraldsp.com/u/john987)\
**Post date:** [August 24, 2023, 3:00am UTC](https://unity.neuraldsp.com/t/midi-learn/9577/8 "2023-08-24T03:00:52Z")

</div>

the expression pedal assignment was streamlined in Firmware 2.1… would still be nice to somehow assign expression pedals straight from the parameter when one has it in front on the screen.

Now just 16 expression parameters via MIDI CC and this would be pretty good (instead of two)… LFOs/envelopes would be great additions too.

---

<div class="post-metadata">

**Author:** ![john987](https://avatars.discourse-cdn.com/v4/letter/j/c89c15/32.png) [@john987](https://unity.neuraldsp.com/u/john987)\
**Post date:** [October 31, 2023, 5:51am UTC](https://unity.neuraldsp.com/t/midi-learn/9577/9 "2023-10-31T05:51:42Z")

</div>

Was there any update with 2.2?
