Suggestions/enhancements for MIDI

[ac1176]

Hi @rerdavies ,

Thanks for all the hard work you're putting into this project. I'm having a lot of fun using PiPedal recently, especially with the implementation of NAM.

A couple of suggestions I thought I'd share for the MIDI side of things that you may wish to consider in future upgrades:

1. It appears that PiPedal is configured to listen to MIDI messages in omni mode; it doesn't seem possible to be able to set PiPedal to a specific MIDI channel. While that doesn't present an issue if only a single MIDI device is connected to PiPedal (eg, a foot controller), it would probably cause headaches if PiPedal was one of several devices connected within a MIDI daisy chain. As an example, if you had a sequencer controlling a few devices from a single MIDI output port, with those devices connected as MIDI in -> MIDI thru -> in -> thru...etc, any program change message intended for, say, a keyboard configured on MIDI channel 2 would also cause PiPedal to change patches unexpectedly.

2. When configuring a LV2 plugin parameter to 'listen' to a MIDI CC message within the Preset MIDI Bindings page, an improvement might be to scale the minimum and maximum values that the parameter can be swept between using the range/units specified within that plugins' TTL file, rather than 0.000 to 1.000. An example here would be using the TooB Volume plugin and adjusting it using a MIDI foot controller volume pedal. The user might require the TooB Volume range to sweep from -INF to 0dB in response to a CC range of 0 to 127. But because the TooB Volume plugin has a adjustable range of -INF to +30dB, the user needs to set the MIDI Binding max value to 0.667 to ensure the expected maximum target is 0dB in the plugin.

[rerdavies]

Both good feature requests. Please log them as Issues at https://github.com/rerdavies/pipedal/issues (two separate issues, please, and tag them as "Feature Request"s. Thanks, Robin.

…

On Sun, Apr 19, 2026 at 6:49 PM ac1176 ***@***.***> wrote: Hi @rerdavies <https://github.com/rerdavies> , Thanks for all the hard work you're putting into this project. I'm having a lot of fun using PiPedal recently, especially with the implementation of NAM. A couple of suggestions I thought I'd share for the MIDI side of things that you may wish to consider in future upgrades: 1. It appears that PiPedal is configured to listen to MIDI messages in omni mode; it doesn't seem possible to be able to set PiPedal to a specific MIDI channel. While that doesn't present an issue if only a single MIDI device is connected to PiPedal (eg, a foot controller), it would probably cause headaches if PiPedal was one of several devices connected within a MIDI daisy chain. As an example, if you had a sequencer controlling a few devices from a single MIDI output port, with those devices connected as MIDI in -> MIDI thru -> in -> thru...etc, any program change message intended for, say, a keyboard configured on MIDI channel 2 would also cause PiPedal to change patches unexpectedly. 2. When configuring a LV2 plugin parameter to 'listen' to a MIDI CC message within the Preset MIDI Bindings page, an improvement might be to scale the minimum and maximum values that the parameter can be swept between using the range/units specified within that plugins' TTL file, rather than 0.000 to 1.000. An example here would be using the TooB Volume plugin and adjusting it using a MIDI foot controller volume pedal. The user might require the TooB Volume range to sweep from -INF to 0dB in response to a CC range of 0 to 127. But because the TooB Volume plugin has a adjustable range of -INF to +30dB, the user needs to set the MIDI Binding max value to 0.667 to ensure the expected maximum target is 0dB in the plugin. — Reply to this email directly, view it on GitHub <#468?email_source=notifications&email_token=ACXK2DHLPVAWGKF6LE7E6CT4WVJWPA5CNFSNUABAM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPHE4TCMZQGQ22M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACXK2DH3XNCSDGWJHUOHAWT4WVJWPAVCNFSM6AAAAACX63XDO6VHI2DSMVQWIX3LMV43ERDJONRXK43TNFXW4OZZHEYTGMBUGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ac1176]

Done :)