02-19-2020, 01:39 AM
I'm having inconsistent problems with the timing of triggers and CV/Mod out from channels when i'm triggering samples on my assimil8or—so i'm trying to make sure i've got all the info i need to make everything work together properly before I actually whine 
Essentially i've got a breakbeat (amen, think, etc) loaded up on a channel of my assimil8or, and i'm trying to trigger it like I would in renoise or an oldschool tracker with the sample offset command (like drum n bass, chopping up breakbeats, etc). With the way the assimil8or works, it makes the most sense to me to run my samples in "gated" playback mode—meaning the sample will play as long as a gate is high. I've looked at the trigger and CV (and Mod) outs on a scope and it seems like the autogate function doesn't go low long enough for the assimil8tor to register the new rising edge for the next note's gate. So i've been experimenting with triggers, trigger delay on tracks, and the kill command to make nerdseq generate the longest gate i can but still have it reset with enough time before the next rising edge that the assimil8or will register another gate.
So after all that explanation, what do the numbers next to the "trigger delay" track option mean? you can set it from 0 to 31, but is that in ms? Also, with regards to the kill command, I've noticed that sometimes it'll kill later than the next line at higher values, but only during faster tempi—what are the values for the kill command measured in? I'm assuming ms but when kill is set to 100, how many ms, or is it like 1 tick per KILL 100?
I'd love to understand the timing relationships between ticks, ms, trigger delays, and the kill command, so I can have the control over trigger and gate length that i'm looking for
Essentially i've got a breakbeat (amen, think, etc) loaded up on a channel of my assimil8or, and i'm trying to trigger it like I would in renoise or an oldschool tracker with the sample offset command (like drum n bass, chopping up breakbeats, etc). With the way the assimil8or works, it makes the most sense to me to run my samples in "gated" playback mode—meaning the sample will play as long as a gate is high. I've looked at the trigger and CV (and Mod) outs on a scope and it seems like the autogate function doesn't go low long enough for the assimil8tor to register the new rising edge for the next note's gate. So i've been experimenting with triggers, trigger delay on tracks, and the kill command to make nerdseq generate the longest gate i can but still have it reset with enough time before the next rising edge that the assimil8or will register another gate.
So after all that explanation, what do the numbers next to the "trigger delay" track option mean? you can set it from 0 to 31, but is that in ms? Also, with regards to the kill command, I've noticed that sometimes it'll kill later than the next line at higher values, but only during faster tempi—what are the values for the kill command measured in? I'm assuming ms but when kill is set to 100, how many ms, or is it like 1 tick per KILL 100?
I'd love to understand the timing relationships between ticks, ms, trigger delays, and the kill command, so I can have the control over trigger and gate length that i'm looking for