# All T-Racks plugin toggles should be mappable

**URL:** <https://forum.ikmultimedia.com/t/all-t-racks-plugin-toggles-should-be-mappable/1136>\
**Category:** Feature Requests\
**Created:** [September 22, 2026, 1:04am UTC](https://forum.ikmultimedia.com/t/all-t-racks-plugin-toggles-should-be-mappable/1136 "2026-09-22T01:04:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![arendej](https://avatars.discourse-cdn.com/v4/letter/a/ecd19e/32.png) [@arendej](https://forum.ikmultimedia.com/u/arendej)\
**Post date:** [September 22, 2026, 1:04am UTC](https://forum.ikmultimedia.com/t/all-t-racks-plugin-toggles-should-be-mappable/1136/1 "2026-09-22T01:04:13Z")

</div>

**Product:**  
All T-Racks plugins/devices

**Summary:**  
Some toggles/controls cannot be mapped

**Problem / Use Case:**  
Many T-Racks devices/plugins have toggles or controls that cannot be mapped to MIDI or mapped to be controlled by Ableton Live.  
One example of this is the Mode and Main and ISPL and Dithering toggles within the Sealth Limiter. Those toggles cannot be mapped to a control in Ableton.  
The only toggle that can be mapped is the Bypass.

**Proposed Solution:**  
Make it so that all toggles/switches/controls can be mapped to MIDI.  
Make it so that all toggles/switches/controls can be mapped in the Ableton “configure” mode.

 ![image](https://canada1.discourse-cdn.com/flex034/uploads/ikmultimedia/original/1X/2c361ca379cff6d6e1263d3994068556df998cc8.jpeg)

**Priority / Impact:**  
Medium

---

<div class="post-metadata">

**Author:** ![nitrateaudio](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.ikmultimedia.com/nitrateaudio/32/505_2.png) [@nitrateaudio](https://forum.ikmultimedia.com/u/nitrateaudio)\
**Post date:** [September 22, 2026, 4:27pm UTC](https://forum.ikmultimedia.com/t/all-t-racks-plugin-toggles-should-be-mappable/1136/2 "2026-09-22T16:27:00Z")

</div>

just curious. why would you want to map some of these settings in MIDI? its not an instrument. Its a mastering limiter.

---

<div class="post-metadata">

**Author:** ![arendej](https://avatars.discourse-cdn.com/v4/letter/a/ecd19e/32.png) [@arendej](https://forum.ikmultimedia.com/u/arendej)\
**Post date:** [September 22, 2026, 4:48pm UTC](https://forum.ikmultimedia.com/t/all-t-racks-plugin-toggles-should-be-mappable/1136/3 "2026-09-22T16:48:25Z")

</div>

So that it can be mapped and manipulated by a DAW or controller that would already be controlling other parameters in the plugin.  
It’s also a case for consistency.