Latching notes is weird

Bug Description

The core of the feedback is this:

When I’m holding down a note, tapping the shift button should latch or unlatch that note and playback should follow suit.

Now I have to hold the shift first then play the note to latch it. I think it would make more sense to allow this in any order. It shouldn’t matter if I press shift or the note first.

Also, and this might be the big part. When synced to an external clock, I have to latch before the clock starts or the internal sequencer is not aligned. I don’t think it knows about the position pointer. If I end a song with external clock and notes are latched they appear to still be latched, but do not play if the clock is restarted.

On/illuminated should always mean it’s going to play, and the order in which I selected the shift or note shouldn’t matter. I often find myself on something cool, I want to lock that in and move to another device, but I have to lift my hands, hold shift, and repress the same pads.

Expected Behavior:
• Tapping [Shift] and any [Pad] in any order should latch/unlatch the pad.
• Playback behavior should follow the latched state immediately.
• The [Shift] key should act as a modifier regardless of press order.

Actual Behavior:
• You must press and hold [Shift] before tapping a [Pad] to latch it.
• If the pad is pressed first, then Shift, the latch action is ignored.
• This causes workflow friction, especially during live sessions or spontaneous ideas.

—-
Expected Behavior:
• When synced to an external clock (e.g., from a DAW), latched pads should resume playback when the external clock restarts.
• If a note is latched (on/illuminated), it should play on next clock start regardless of when it was latched.

Actual Behavior:
• If pads are latched after the external clock has started, playback may be misaligned or ignored.
• If playback ends and clock is stopped, then restarted, the pads appear latched (still illuminated) but do not play.
• Device seems unaware of the external position pointer or clock phase.

Steps to Reproduce

  1. Select a Synth track and load a playable sound.
    2. Press a [Pad] first (do not hold Shift).
    3. While holding the Pad, press [Shift].
    4. Observe that the note plays but is not latched.
    5. Now try: Hold [Shift] first, then tap the same [Pad].
    6. Observe that the note is latched (expected behavior).

Workaround: Always remember to press [Shift] first — but this limits intuitive live performance.
Steps to Reproduce (External Clock Sync Issue)
1. Connect Polyend Play to a DAW or hardware clock source.
2. Enable external sync (MIDI Clock In).
3. Latch a note before starting the external clock – it plays correctly.
4. Stop the external clock.
5. Restart the external clock – latched notes are still lit, but do not play.
6. Unlatch and re-latch – only then do they play again.

Occurrence / Frequency

Always

Found in Firmware

  • Version: 1.2.0
  • Build: 1663

Attachments

1 Like

My experience is the same. This write up perfectly describes the behavior and what interrupts the intuitive workflow.

Thanks for the bug report @charles.soderlund! Going to test your issue w/ the external clock :slight_smile:

Regarding the first part;

In this scenario, the Note does latch if you let go of the pad first and then Shift.

1 Like

Hi @charles.soderlund , thanks for logging the problems you found.

First of all, please read How to report bugs and do not report several issues in one report.

This is not true: releasing a pad while Shift is held will latch it.

We’ll consider improving the other behaviours you describe in future updates, but I will close this bug report as invalid because it doesn’t follow the guideline, sorry about that. Feel free to log them separately and we can provide feedback for each. Thanks for your support!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.