![]() |
|
Stop all patterns without stopping clock - 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: General Questions (https://forum.xor.eu/forumdisplay.php?fid=17) +---- Thread: Stop all patterns without stopping clock (/showthread.php?tid=2018) |
Stop all patterns without stopping clock - grib - 11-07-2025 For extra drama in live performance I like to sometimes stop all the Nerdseq patterns that are playing. I have 2 ways to do this, both of which are not that great: * SHIFT + STOP to stop all, then SHIFT + START to restart a row. This can get out of sync with my other sequencers, which all share a clock. * Create a 00 "mute pattern" (empty) and make a row full of 00. SHIFT+START on that row to silence at the end of pattern, SHIFT + START on a different row to restart. This keeps the clock in sync, but I can't stop in the middle of a pattern and I don't always want to restart a whole row. I may have had a random selection of patterns in different columns playing and I would love to restart the patterns that were previously running. Is there a "global mute/unmute" (best) or an "all stop" that stops all patterns but doesn't stop the clock running? Preferably easy to access with a front panel key combo? Oh hai I just discovered "SOLO" mode (SHIFT + UP + START). At least in my current proj I have one unused sampler track, and cursoring to that track and hitting SOLO does exactly what I want. I can probably make this work in most situations. RE: Stop all patterns without stopping clock - XORadmin - 11-07-2025 This is not a standard implemented function, but this is possible using the mappings. (slightly more complex than usual due to a little bug in the used mapping destinations, but it does work!) Lets say you want to use the button combo 'STOP+CURSOR UP' to stop all now but keep the sequencer running. Your mapping would look like this: Code: 00 EXT BUTN STOP > ---- ---- ---- Check if button STOP is pressed (pressed = true)In fact this is one possibility and the CALC FORC is needed due to the mini-bug. However it works perfectly. |