Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Mapping Discussion
I'm trying to capture one-shots from e-drum MIDI coming into the NerdSEQ, and while those notes can be read by MIDITC NOTE as well as clone a modular trigger from live input, per note on/off seems to miss the one-shots and never produces a boolean 1. I have two things I would like to achieve with this: because individual drum triggers/heads each have their own note assignments, I would like to grab particular notes and send a trigger to a particular trigger out; secondarily, I would like to start/restart a pattern immediately on the next tick (which I'm not entirely sure is possible) after a given note's one-shot.

If it's not possible to capture per-note one-shots directly, I imagine logic could be utilized as a workaround, so I'm looking for guidance on whether either of those strategies should be possible. I'm also wondering if there is a way to start/restart a pattern immediately on the next tick after a boolean 1.
Reply
(04-23-2026, 04:54 PM)RMBLRX Wrote: I'm trying to capture one-shots from e-drum MIDI coming into the NerdSEQ, and while those notes can be read by MIDITC NOTE as well as clone a modular trigger from live input, per note on/off seems to miss the one-shots and never produces a boolean 1. I have two things I would like to achieve with this: because individual drum triggers/heads each have their own note assignments, I would like to grab particular notes and send a trigger to a particular trigger out; secondarily, I would like to start/restart a pattern immediately on the next tick (which I'm not entirely sure is possible) after a given note's one-shot.

If it's not possible to capture per-note one-shots directly, I imagine logic could be utilized as a workaround, so I'm looking for guidance on whether either of those strategies should be possible. I'm also wondering if there is a way to start/restart a pattern immediately on the next tick after a boolean 1.

I guess you mean receiving the note by MIDI TC C-4N (or any other note), right? In that case I assume that the received note on and off situation arrives back to back and the 1 millisecond mapping time misses the state in between (often). It will be set but before the mapping scans it the next time it might be already off again then.
This is not really possible to detect in the way the mappings handle the midi data currently. The note-numbers themself get latched and can be read out, which you acknowledged already and the same thing would be needed for the boolean setting which is not in there (and which would come with other advantages that makes it not practical in several cases. At least as far as I can think about it right now with my morning coffee). 

Things you maybe could do:
- increase the time between the note on/off with your e-drum if that it possible in any way
- if you use a trigger16 track you can route the midi to that (in the midi setup) and different (fixed) notes can be used to trigger the outputs (and they do). Then you would need to adjust in your e-drum that it sends dedicated notes. If you further want to do something with these triggers you might want to connect these to the CV-inputs and use those with the mappings then.

If you want to start a track directly you need to use the cue functions and set it to each step. A double start would then directly start the pattern with the next step. In the mappings I think one should be able to generate a 'double start' using the (exclusive) XMAP commands (in the RC they are some new ones that would do a 1shot and can combine multiple rows to be executed once) in the mapping itself. Thats in theory and I didn't test that.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!  Smile
Reply
I'm using the mapping to sample and hold the pitch coming from a pattern in nerdseq.
I've mannaged to do that but the sampled pitch is really out of tune.. 25 cents up and down from the note i tune the osc to.
To confirm, when I output the pitch from the cv output1 (same cv that is sampled) the tunning is fine (within +-3 cents)

edit: image seems cropped here's a link for it

https://drive.google.com/file/d/13YhxSjk...sp=sharing


Attached Files Thumbnail(s)
   
Reply
(04-24-2026, 09:52 AM)XORadmin Wrote:
(04-23-2026, 04:54 PM)RMBLRX Wrote: I'm trying to capture one-shots from e-drum MIDI coming into the NerdSEQ, and while those notes can be read by MIDITC NOTE as well as clone a modular trigger from live input, per note on/off seems to miss the one-shots and never produces a boolean 1. I have two things I would like to achieve with this: because individual drum triggers/heads each have their own note assignments, I would like to grab particular notes and send a trigger to a particular trigger out; secondarily, I would like to start/restart a pattern immediately on the next tick (which I'm not entirely sure is possible) after a given note's one-shot.

If it's not possible to capture per-note one-shots directly, I imagine logic could be utilized as a workaround, so I'm looking for guidance on whether either of those strategies should be possible. I'm also wondering if there is a way to start/restart a pattern immediately on the next tick after a boolean 1.

I guess you mean receiving the note by MIDI TC C-4N (or any other note), right? In that case I assume that the received note on and off situation arrives back to back and the 1 millisecond mapping time misses the state in between (often). It will be set but before the mapping scans it the next time it might be already off again then.
This is not really possible to detect in the way the mappings handle the midi data currently. The note-numbers themself get latched and can be read out, which you acknowledged already and the same thing would be needed for the boolean setting which is not in there (and which would come with other advantages that makes it not practical in several cases. At least as far as I can think about it right now with my morning coffee). 

Things you maybe could do:
- increase the time between the note on/off with your e-drum if that it possible in any way
- if you use a trigger16 track you can route the midi to that (in the midi setup) and different (fixed) notes can be used to trigger the outputs (and they do). Then you would need to adjust in your e-drum that it sends dedicated notes. If you further want to do something with these triggers you might want to connect these to the CV-inputs and use those with the mappings then.

If you want to start a track directly you need to use the cue functions and set it to each step. A double start would then directly start the pattern with the next step. In the mappings I think one should be able to generate a 'double start' using the (exclusive) XMAP commands (in the RC they are some new ones that would do a 1shot and can combine multiple rows to be executed once) in the mapping itself. Thats in theory and I didn't test that.

Thanks for the tips. It sounds like most of what I'm after is probably within the domain of the Trigger16 addon, which I don't yet have. Incidentally, though, the closest I've gotten to my desired pattern triggering behavior is by triggering the modular clock with a one-line pattern started. I figured this would be replicable with track tick mapping but I can't seem to get behavior as consistent as with the modular clock (which is obviously too global for my purposes) -- probably I'm not understanding the tick function properly, but it seems like this could be my ticket if I can trigger a tick to play a single row consistently.

As far as Trigger16, can the MIDI note assignment for each trigger be set individually, or are they set off a basenote?
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)