search

anzbert / beat_pads

USB MPE Midi Pad Controller App for Android, iPad and iPhone. Made with Flutter.
GNU General Public License v3.0
46 stars 7 forks source link

Allow latching (hold back Note Off messages) instead of Sustain (CC64) #35

Open mark-orion opened 7 months ago

mark-orion commented 7 months ago

The problem is that many (hardware) synthesizers do not process CC64 (Sustain) messages. This means that the sustain function is not working with these devices. This can be avoided by using latching instead: Here the pad/key is simply held in a pressed state. As a result no Note Off message is sent until the pad/key is released again. It would be good if this fantastic app would support latching.

anzbert commented 7 months ago

Thanks for the hint. I think currently that would require quite the rewrite of how the note buffers work. But maybe I could hijack the note release delay function somehow for that.

Either way, I'll think about how to do it. To be honest, the Push-Style MPE function is a higher priority right now. So when that is at a stage that I am happy with I can look into this issue.

Thanks for the suggestion and the kind words!

mark-orion commented 7 months ago

Thanks for the quick response. I would tackle the problem at the UI level and implement a toggle function for the pads. No need to mess with buffers and Midi code. But being a developer myself I understand that you need to set priorities.

On 13 April 2024 04:07:51 BST, anzbert @.***> wrote:

Thanks for the hint. I think currently that would require quite the rewrite of how the note buffers work. But maybe I could hijack the note release delay function somehow for that.

Either way, I'll think about how to do it. To be honest, the Push-Style MPE function is a higher priority right now. So when that is at a stage that I am happy with I can look into this issue.

Thanks for the suggestion and the kind words!

-- Reply to this email directly or view it on GitHub: https://github.com/anzbert/beat_pads/issues/35#issuecomment-2053137263 You are receiving this because you authored the thread.

Message ID: @.***>