+- 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: Some Trigger16 ideas (/showthread.php?tid=814)
Some Trigger16 ideas - sirjpink - 08-23-2020
So far (like 9 months now) I've been using the NerdSeq almost exclusively as a euclidean trigger generator. I mean, 16 trigger channels in such a small package with great visual feedback, what's not to like? Whilst playing I got some ideas that I hope might be useful for this expander. For reference I using firmware V1.21A.
1) Visual indication of the starting point of the euclidean pattern in the drum matrix
Knowing the right cursor position is (currently) necessary because changing the euclidean fill of a pattern overwrites the offset to the current cursor position (which makes absolute sense). This means you have to remember the offset of your pattern if you just want to change the fill, but keep the offset. This is kind of a lot of information to hold in your head if you have 4 or more columns going on (not counting whatever else is going on in your system).
Denoting the first beat/offset of the pattern helps placing the cursor at the right row when you want to change the pattern. Perhaps something like an open square instead of a filled one would already do the trick.
2) Visual indication of the drum matrix triggers in the trigger column view (page 1)
My use case for the trigger column view is to augment generated trigger patterns by, for example, adding ratchets or extra beats on the fly. Currently I have to remember the relevant row number for adding these things (especially when scrolling down, I tend forget the exact number).
It is not a really big issue, since the cursor's row position is maintained when navigating between matrix and trigger views, but that does add a lot of extra back-and-forth going between the pages to make sure you are adding stuff at the right position. Adding some form of visual feedback would really help with maintaining your bearings whilst navigating the columns.
I get that this would be a challenge UI-wise as the column view is already quite packed; perhaps something like a lighter background for the empty cells that have a trigger in the drum matrix or a different symbol (like '==' or '++' instead of '--' for empty cells with drum matrix triggers) could be done?
3) Being able to send the Trigger16 triggers over MIDI
I assume that this request is a bigger one to implement, but this would allow the NerdSeq to easily sequence other equipment over MIDI (stuff like the Roland TR8S, MPC's, or who knows) using the drum matrix and trigger column (I find these way easier to use for triggers than a dedicated MIDI track). It would also allow easy patching to modules with MIDI in (such as the Squarp Rample or 1010music Bitbox) as you would require just 1 MIDI cable rather than 4 to 16 (if you go all out with a Bitbox) regular patch cables which also frees up the Trigger16 output for triggering other stuff in the system (in the same pattern of course).
Perhaps something like being able to assign a MIDI output channel to and (optionally) basenote (like the current PR setting; eg. TR1 being C-0, TR2 C#0 etc.) would be possible?
Thank you for entertaining these suggestions and keep up the good work; I am massively enjoying my NerdSeq!
PS. Just realized this is my first post! Hi, everyone!
RE: Some Trigger16 ideas - XORadmin - 08-24-2020
Hi there,
thanks for the ideas. Let me get into the possibilities:
1) It is actually not possible to mark a starting point for the euclidean beats. Mostly because there is no starting point. At the moment an euclidean part is filled in, it is blindly filled in into the sequence. The only thing that is being remembered is the current number of the euclidean. Saving for all patterns and all columns the point where the euclidean has been filled in would be quite a overhead (and in my opinion a waste of memory). It is only meant to be another possibility to fill in sequences.
2) I think something like this could be easily possible and makes sense. Will add it to my list but not top prio.
3) There is another topic where i already describe my plans for euclidean -> Midi. I will not include this with the trigger expander as it doesn't really make sense there, but with the midi tracks it is definitely on my 2do list.
RE: Some Trigger16 ideas - sirjpink - 08-24-2020
(08-24-2020, 09:33 AM)XORadmin Wrote: Hi there,
thanks for the ideas. Let me get into the possibilities:
1) It is actually not possible to mark a starting point for the euclidean beats. Mostly because there is no starting point. At the moment an euclidean part is filled in, it is blindly filled in into the sequence. The only thing that is being remembered is the current number of the euclidean. Saving for all patterns and all columns the point where the euclidean has been filled in would be quite a overhead (and in my opinion a waste of memory). It is only meant to be another possibility to fill in sequences.
2) I think something like this could be easily possible and makes sense. Will add it to my list but not top prio.
3) There is another topic where i already describe my plans for euclidean -> Midi. I will not include this with the trigger expander as it doesn't really make sense there, but with the midi tracks it is definitely on my 2do list.
Thanks for getting back!
Seems I missed the MIDI plan update, but that way it is even better; many more trigger options (with midi going to the sampler, it keeps the Trigger16 patterns free for other duties).