Light Pads to display the MIDI Notes and Velocity recieved

[Aisjam]

What is the problem?

Currently, the Polyend Synth appears static when receiving MIDI input from external gear. Unlike when users interact with the pads directly, there’s no visual indication of incoming MIDI activity. This lack of feedback makes it harder to monitor what the synth is doing in real-time and detracts from the intuitive, performance-friendly experience.

What should this feature achieve?

1. Light up the pads to correspond with incoming MIDI notes and velocities.

2. Use the appropriate MIDI channel for correct synth visualisation, ensuring the pads reflect what is being played externally.

3. Provide an engaging, visually responsive interface that aligns with the tactile feedback users expect when using the Synth’s pads live.

This feature would enable the Polyend Synth to visually display incoming MIDI notes and their velocity on the pads, offering dynamic feedback for users playing the synth via external gear. Similar to how the pads light up when played live, this enhancement would allow users to see the synth’s activity, making it more engaging and informative during live performances or studio sessions.

Are there any workarounds?

–

Any links to related discussions?

Discord - Group Chat That’s All Fun & Games

here is an experiment connecting the synth to a unity visualization, Showing sorting algorithms to make music. the sound is coming from the synth, however is static and is difficult to see the connection to external gear. It would be nice to build the Audio/Visual connection between the two

Any references to other products?

The Polyend Tracker when you light up the pads to what is happening on the screen and Play with its grid layout. they give more information outside of the screen

[Mitch]

open for voting, rephrased title for clarity, feel free to edit!

[krizz79]

Voted. This is an absolute must-have.

[Sandroid]

@here , since of Firmware 1.0.3 you can technically have the pads light up, if you use the new Pad mapping feature.

Have a look at the video here and let me know if we could consider this request completed/implemented:

How Pad Mapping works on the Polyend Synth

Since i’ve seen this come up in a couple conversations, i figured i might as well make a little video for it. Since Firmware 1.0.3 of the Polyend Synth there is a featured called Pad Mapping. This video should give you a quick overview of what it is and how it works: [Polyend Synth 1.0.3 - Pad Mapping] i’ve specfically added the Tracker as well, since the Middle C setting on the Tracker may cause some headscratches if you aren’t careful If you got any questions, feel fre…

[krizz79]

Hi,

Thanks for this tip. I find it working well when using external MIDI controller just like the video shows, but… it’s not working correctly when Synth is used as MIDI controller for itself (therefore local mode is disabled). My typical setup is: Synth connected to DAW (MIDI OUT), in DAW a BlueARP is doing its stuff and sends it back to Synth via its MIDI IN. Works great until you enable pad mapping - then, it ceases to play any sound. I’ve discovered that it is because local mode must be enabled for pad mapping to work, yet when it’s enabled, any incoming notes via MIDI IN is sent back to MIDI OUT again, as if highlighted pad generated extra note itself! This way whole setup is trapped in loop when BlueARP is being constantly fed with incoming ever-changing notes completely disrupting whatever it was supposed to play. So no, unfortunately I personally cannot accept this solution. Pad highlighting cannot require local mode to be enabled as well as it cannot generate notes. I’d expect that Synth simply highlights whatever it gets via MIDI IN and that’s it.