Kill FX parameter - MOD track

[originaljimdandy]

I have been trying to understand the Kill FX in the modular tracks. I get that KILL 000 prevents the gate/trigger for that note. The manual says kill can create "really short gates/triggers or every possible gate timing." So is the timing absolute (mS ??) or relative to the next note (% of a step?) What exactly are the units for kill?

For example, I am working with a sequence with a fairly fat ASR envelope out of Maths and the default trigger gap (?? ms) slurs the notes. I worked it out with GROOVE and [] but it is cumbersome since I have to keep track of pairs of lines like so:

Note           Groove
C#4             6 
---                A   <<<
[]                 1   <<<
A                 6

I would much rather do:

Note           FX
C#4            --- 
---               ---  
---               KILL ???
A                ---

I am not sure about the timing but @100 BPM it is maybe 100 mS gap I am looking for? How would that translate into KILL parameter?

Thanks,

-james

[XORadmin]

I have been trying to understand the Kill FX in the modular tracks. I get that KILL 000 prevents the gate/trigger for that note. The manual says kill can create "really short gates/triggers or every possible gate timing." So is the timing absolute (mS ??) or relative to the next note (% of a step?) What exactly are the units for kill?

For example, I am working with a sequence with a fairly fat ASR envelope out of Maths and the default trigger gap (?? ms) slurs the notes. I worked it out with GROOVE and [] but it is cumbersome since I have to keep track of pairs of lines like so:

Note           Groove
C#4             6 
---                A   <<<
[]                 1   <<<
A                 6

I would much rather do:

Note           FX
C#4            --- 
---               ---  
---               KILL ???
A                ---

I am not sure about the timing but @100 BPM it is maybe 100 mS gap I am looking for? How would that translate into KILL parameter?

Thanks,

-james

Kill is absolute. I don’t know the timings now out of my head.
If you need a longer gate then you either use note on/off only(either with auto gate and [ ] on another step of a trigger FE and 00 on another step.. Or if it should be relative to the bpm it would be a trigger with D0 to DF. I would use the kill personally only for very short absolute stuff or if you want to have a sub-step note off. A ratcheting with E0 which lasts exactly 1 step would also be a possibility.
The groove for this is probably not a good idea since it changes also your pattern timing (if not equal in the end to the base pattern length ticks).

[originaljimdandy]

First off I seriously appreciate the work you are doing with NerdSeq. I am a big fan (and customer, heh). Thanks for all the hard work!

I see what you mean about kill. Apologies, but I am going to dig into this a bit. Hopefully this will help explain what I am looking for. 

The problem is that note off uses a whole step. I swung the timing to get a one tick 'note off' but that is cumbersome since yes you need to have groove add up to 6 per total number of steps ( B + 1 = C = 6*2) (Haven't done this much hex in AGES)

I spent some time scoping out the behavior of the KILL FX. The argument is the _length_ of the note _duration_ starting with the current step. So KILL 000 cuts the note right away (down to zero length if it is on the note step). Higher = longer and can overlap steps if there are no intervening notes.

It appears to be an absolute time. 
For 150 BPM KILL 340 is the duration of 1 step in the pattern at x1 clock and for 100 BPM KILL 4E1 is one step (ratio of 1.5 like the BPM). 

The minimum duration appears to be 25 mS but it seems to be fairly linear after that at 0.1 mS/step. 
KILL FFF is approx 400 mS (measured 424 - 412 mS with my crappy scope depending on tempo) 

So something like this pattern at 100 BPM

00 C#4 
01 ---
02 ---  ... KILL 190
03 E4  ... etc. etc

produces a note at 150 + 150 + 40 = 340 mS since KILL is relative to the current step (measured 341 mS). It ends ~110 mS early. I will tweak the number to see what sounds best for long held notes at this tempo.

Sorry to go on so long!

Thanks,
-James

[XORadmin]

No worries.

Just to be sure. A gate for 1 tick (or a trigger in fact) is a D0 in the trigger column. It is based on the bpm and would last for exactly 1/6 step.
Trigger column used
00 C#4 FE (Or auto gate)
01 ---
02 --- D0 (Gate was already on and will last for 1 more tick)
03 E-4 ... etc. etc

I think that does exactly what you need and you don’t have to take care about absolute Kill timings etc.