# Do mapped MIDI controllers bypass the earlier MIDI chain?

**URL:** <https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844>\
**Category:** Using Zynthian\
**Tags:** midi\
**Created:** [February 20, 2026, 4:59pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844 "2026-02-20T16:59:50Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![wyleu](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/wyleu/32/514_2.png) [@wyleu](https://discourse.zynthian.org/u/wyleu)\
**Post date:** [February 28, 2026, 11:08am UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/41 "2026-02-28T11:08:58Z")

</div>

I’m really looking forward to the first main market piece of kit that offers this capture workflow feature . . .

---

<div class="post-metadata">

**Author:** ![emuse](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/e/b782af/32.png) [@emuse](https://discourse.zynthian.org/u/emuse)\
**Post date:** [February 28, 2026, 11:29am UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/42 "2026-02-28T11:29:52Z")

</div>

Hi @jofemodo

Following your post I went back to record that issue, switched it on and… everything works fine as expected. Maybe the reboot solved something that was screwed up….

Thanks and… Sorry for the noise!

Best

---

<div class="post-metadata">

**Author:** ![jofemodo](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jofemodo/32/2_2.png) [@jofemodo](https://discourse.zynthian.org/u/jofemodo)\
**Post date:** [February 28, 2026, 11:32am UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/43 "2026-02-28T11:32:23Z")

</div>

> [@wyleu](#):
>
> I’m really looking forward to the first main market piece of kit that offers this capture workflow feature . . .

Keep looking for it, but you won’t find it 😎

---

<div class="post-metadata">

**Author:** ![ToFF](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/toff/32/5532_2.png) [@ToFF](https://discourse.zynthian.org/u/ToFF)\
**Post date:** [February 28, 2026, 11:49am UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/44 "2026-02-28T11:49:36Z")

</div>

And what about a mainstream device that offers a capture workflow **and** lets you define per-synth CC parameter ranges (i.e., mapping a CC to a specific parameter _with a customized value range_)? It may look like a small detail, but it massively improves Zynthian’s playability and usability. I wouldn’t be afraid to call it a milestone.

It also feels like @jofemodo, @riban, and others keep hitting one milestone after another. Thanks, guys!

---

<div class="post-metadata">

**Author:** ![wyleu](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/wyleu/32/514_2.png) [@wyleu](https://discourse.zynthian.org/u/wyleu)\
**Post date:** [February 28, 2026, 1:19pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/45 "2026-02-28T13:19:53Z")

</div>

> [@jofemodo](#):
>
> Keep looking for it, but you won’t find it 😎

Yet.

---

<div class="post-metadata">

**Author:** ![wyleu](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/wyleu/32/514_2.png) [@wyleu](https://discourse.zynthian.org/u/wyleu)\
**Post date:** [February 28, 2026, 1:21pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/46 "2026-02-28T13:21:10Z")

</div>

> [@emuse](#):
>
> Sorry for the noise!

Nope, I’m not missing that [one](https://wiki.zynthian.org/index.php/Talk:Zynthian_Wiki_Home)!!!

---

<div class="post-metadata">

**Author:** ![jofemodo](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jofemodo/32/2_2.png) [@jofemodo](https://discourse.zynthian.org/u/jofemodo)\
**Post date:** [February 28, 2026, 3:11pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/47 "2026-02-28T15:11:12Z")

</div>

> [@wyleu](#):
>
> I’m really looking forward to the first main market piece of kit that offers this capture workflow feature . . .

What if we turn the “V5 mockup” in a remote interface for Zynthian. Headless zynthian owners would find it super useful. And future JFK owners would have a way to access the full zynthian power.

Don’t find the raw VNC UI too austere? I’m really surprised nobody has asked for this. It’s so evident … and we are so close!! 🤓

---

<div class="post-metadata">

**Author:** ![jawn](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jawn/32/14487_2.png) [@jawn](https://discourse.zynthian.org/u/jawn)\
**Post date:** [February 28, 2026, 3:38pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/48 "2026-02-28T15:38:53Z")

</div>

Excellent idea, especially to solve the missing encoder issue for starters or external audio interface setups. The encoders could support click/tap and drag up/down.

---

<div class="post-metadata">

**Author:** ![ToFF](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/toff/32/5532_2.png) [@ToFF](https://discourse.zynthian.org/u/ToFF)\
**Post date:** [February 28, 2026, 10:47pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/49 "2026-02-28T22:47:39Z")

</div>

In VNC mode on TouchOnly Wiring and Customization Profile V5 drag up/down is working. But click/tap not.

---

<div class="post-metadata">

**Author:** ![jawn](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jawn/32/14487_2.png) [@jawn](https://discourse.zynthian.org/u/jawn)\
**Post date:** [March 1, 2026, 6:31am UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/50 "2026-03-01T06:31:12Z")

</div>

And if it would have 4 extra virtual encoders it would almost be there.

---

<div class="post-metadata">

**Author:** ![emuse](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/e/b782af/32.png) [@emuse](https://discourse.zynthian.org/u/emuse)\
**Post date:** [March 1, 2026, 5:16pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/51 "2026-03-01T17:16:15Z")

</div>

I got a bit further with the mapping issues I had. When saving and recalling these controller mapping ranges in zs3 states they are not properly restored (and/or updated in the chain). Graph display, values used by the plugin and values shown in the control ranges dialog differ after restoring a ZS3. I think this is how I got what I called strange graph ranges. Try to repeat saving and recalling ZS3s with different settings for controller mappings. This time I’m attaching a capture. Not a complaint, this is Vangelis and recent stuff, but maybe helpful to go on 🙂

Best

---

<div class="post-metadata">

**Author:** ![jlearman](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/j/a698b9/32.png) [@jlearman](https://discourse.zynthian.org/u/jlearman)\
**Post date:** [March 1, 2026, 8:19pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/52 "2026-03-01T20:19:32Z")

</div>

> [@jofemodo](#):
>
> This is implemented now in Vangelis

I just upgraded Oram stable (installed from stable a couple weeks ago) to Vangelis.

I can’t edit chains! When I go to a chain and click the chain name at the top of the screen, the UI locks up, and I have to `systemd restart zynthian` to recover. This happens on any configured chain.

I don’t have zynth hardware, just an RPi 4, with screen and mouse.

I opened an issue: [Clicking on chain name locks up UI · Issue #1585 · zynthian/zynthian-issue-tracking · GitHub](https://github.com/zynthian/zynthian-issue-tracking/issues/1585)

(PS: how can I revert back to Oram?)

---

<div class="post-metadata">

**Author:** ![jofemodo](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jofemodo/32/2_2.png) [@jofemodo](https://discourse.zynthian.org/u/jofemodo)\
**Post date:** [March 2, 2026, 9:03am UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/53 "2026-03-02T09:03:52Z")

</div>

> [@jlearman](#):
>
> (PS: how can I revert back to Oram?)

It’s not recommended. Going back from Vangelis to Oram is not a tested path. Anyway you could try and see what happen.

Please, read this:

> [@Zynbleton Vangelis - READ ME](https://discourse.zynthian.org/t/zynbleton-vangelis-read-me/12619):
>
> Hi there, is zynbleton in vangelis now? Tried finding out myself, but did not succeed wink Regards

We warned about it.

> **PLEASE TAKE NOTE**
> 
> Within the next few days we will be merging our bleeding-edge development into vangelis (testing) branch. This will make vangelis a development branch that **should not** be used for production. (Not that you should have been anyway!)
> 
> Please move to oram to continue to experience a (relatively) stable workflow. Vangelis may be broken at any point (hopefully for not too long!) and should only be used to test the latest bleeding-edge developments. We strongly recommend using a dedicated device (or boot media) for vangelis, separate to your normal, day-to-day zynthian usage (which should use oram).
> 
> There are many changes in this development version and full forward / backward compatibility is not guaranteed. Indeed, you are unlikely to be able to move between oram and vangelis without a degree of hurt.
> 
> **Please heed this warning!** Move from vangelis to oram and / or do not update vangelis unless you want to feel the same hurt that we developers experience.

Regards

---

<div class="post-metadata">

**Author:** ![jlearman](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/j/a698b9/32.png) [@jlearman](https://discourse.zynthian.org/u/jlearman)\
**Post date:** [March 2, 2026, 8:28pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/54 "2026-03-02T20:28:48Z")

</div>

> [@jofemodo](#):
>
> It’s not recommended

Thanks, noted. Fortunately I backed up, so I can just load another SD card.

---

<div class="post-metadata">

**Author:** ![jlearman](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/j/a698b9/32.png) [@jlearman](https://discourse.zynthian.org/u/jlearman)\
**Post date:** [March 10, 2026, 1:51pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/55 "2026-03-10T13:51:17Z")

</div>

I’d really like to try this, but I can’t because I can’t upgrade from Oram to Vangelis. When I try, anytime I click in the title bar (for example, where the chain name appears) the UI locks up.

I reported this as [Clicking on chain name locks up UI · Issue #1585 · zynthian/zynthian-issue-tracking · GitHub](https://github.com/zynthian/zynthian-issue-tracking/issues/1585) . @riban was unable to reproduce it and marked it as unreproducible, but I can do it, and have done it on both Pi4 and Pi5, from two different stable Oram versions.

Note that I’m using HDMI monitor and USB mouse & keyboard, with no Zynth hardware, and that might be a factor.

---

<div class="post-metadata">

**Author:** ![jofemodo](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/jofemodo/32/2_2.png) [@jofemodo](https://discourse.zynthian.org/u/jofemodo)\
**Post date:** [March 10, 2026, 2:29pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/56 "2026-03-10T14:29:43Z")

</div>

Please, send the UI logs to see the error that blocks the UI.

Regards,

---

<div class="post-metadata">

**Author:** ![jlearman](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/j/a698b9/32.png) [@jlearman](https://discourse.zynthian.org/u/jlearman)\
**Post date:** [March 10, 2026, 9:31pm UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/57 "2026-03-10T21:31:09Z")

</div>

Just tell me where to get them. I did UI log from webconf, in debug mode, and it’s posted in the issue (with nothing other than the startup.)

---

<div class="post-metadata">

**Author:** ![melodikadi](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/m/c5a1d2/32.png) [@melodikadi](https://discourse.zynthian.org/u/melodikadi)\
**Post date:** [March 27, 2026, 10:46am UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/58 "2026-03-27T10:46:00Z")

</div>

Just tested this lovely feature! Works well. However, I have one suggestion for my use case, which is as follows:

1. Currently I have a instrument chain with an instrument followed by Calf Filter. I have mapped channel pressure to control the filter frequency. Works super well, especially now that the range can be set.

2. What I want to do next: I’m using an external USB MIDI controller with knobs and buttons. I would like to assign this MIDI controller knobs to control Value at Min min and Value at max. This would give me a quick access to use my MIDI controller to adjust how aftertouch affects the filter. However, it seems these controls cannot currently be mapped to a CC. So my small suggestion is to make these two controls learnable 🙂

---

<div class="post-metadata">

**Author:** ![riban](https://discourse.zynthian.org/user_avatar/discourse.zynthian.org/riban/32/2331_2.png) [@riban](https://discourse.zynthian.org/u/riban)\
**Post date:** [March 27, 2026, 11:03am UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/59 "2026-03-27T11:03:15Z")

</div>

That sounds like a reasonable [feature request](https://github.com/zynthian/zynthian-issue-tracking/issues/new?template=feature_request.md). Please add a ticket to the [issue tracker](https://github.com/zynthian/zynthian-issue-tracking).

---

<div class="post-metadata">

**Author:** ![melodikadi](https://discourse.zynthian.org/letter_avatar_proxy/v4/letter/m/c5a1d2/32.png) [@melodikadi](https://discourse.zynthian.org/u/melodikadi)\
**Post date:** [March 27, 2026, 11:13am UTC](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844/60 "2026-03-27T11:13:04Z")

</div>

Done! [Control options: Make Value at Min and Value at max MIDI learnable · Issue #1613 · zynthian/zynthian-issue-tracking · GitHub](https://github.com/zynthian/zynthian-issue-tracking/issues/1613)

[Previous page](https://discourse.zynthian.org/t/do-mapped-midi-controllers-bypass-the-earlier-midi-chain/12844.md?page=2)