Send PC always pre for queued patterns - Printable Version +- XOR Userforum (https://forum.xor.eu) +-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3) +--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6) +---- Forum: Feature requests (https://forum.xor.eu/forumdisplay.php?fid=12) +---- Thread: Send PC always pre for queued patterns (/showthread.php?tid=2051)

Send PC always pre for queued patterns - PfoRsten - 01-18-2026 Hi, I’ve noticed a few things while using MIDI Program Changes with my Elektron Analog Rytm MK1. First of all, the “always pre” MIDI Program Change behavior is extremely useful when working with Elektron machines — thanks a lot for that! Current behavior Nerdseq can send MIDI Program Change messages always pre, as described in the manual. The Program Change is sent roughly 5 steps in advance. This allows pattern changes on Elektron gear to happen reliably on the next pattern boundary, as long as there is a pattern already playing. In most cases this works perfectly, but I’ve noticed a few edge cases where this behavior could potentially be improved. Issue 1: No previously playing pattern If there is no pattern currently playing before a pattern that contains a Program Change: The Program Change is not sent early As a result, the Elektron machine switches patterns one pattern late I know there’s no way (yet) for Nerdseq to read minds, but… ? Feature request Send the Program Change as soon as a queued pattern contains a Program Change, even if no pattern was playing before. If the user queues the next pattern before the “always pre” step is reached, the Program Change would still be sent in time and result in the expected behavior on the Elektron machine. Issue 2: FX BRK jump to step 0 When BRK is set to jump to step 0 in the FX section: The Program Change is still sent This causes the Elektron pattern to switch back and forth While this behavior is understandable (because of the always pre setting), it can be a bit annoying in practice. I understand that it’s probably not possible to look far enough ahead to detect an upcoming BRK jump in advance. However, maybe there could be: A way to ignore Program Changes in this specific case, or An option to disable “always pre” for Program Changes triggered via the FX section …though ideally, Program Changes should still be sent if I queue up the next pattern. So maybe an option to suppress or better handle Program Changes in this specific situation could help. Thanks for considering this request, and thanks again for your continued support of Nerdseq — it’s an amazing sequencer! Best regards