Gate lengths in ticks

[BillyAB]

Is there any possibility to change the gate lengths from 5ms, 10ms, 15ms, etc to 1ms, 1 tick, 2 ticks, 3 ticks, 4 ticks, etc.
This would be so, so useful.

[XORadmin]

You could partly achieve this using the ratchet functions. And else you can do this for sure with tables.

[BillyAB]

Neither of those solutions are satisfactory. What is the point of gate lengths with 5ms increments? There is hardly any difference between 5-30ms... Ticks just seems like the obvious choice here, it would give a more useful range of gate lengths. Half a step is a standard gate length which you currently don't have quick access to. With ticks you could also quickly extend beyond one step, without the need for an extra "end" point. It would make it much faster to achieve a lot of variation with the inbuilt envelopes.
If ticks are not possible, please consider changing the arbitrary values so they cover a broader range: 1ms, 5ms, 20ms, 40ms, 60ms, 80ms, etc.. I dont see why so much detail is needed between 5-65ms

[mgd]

If ticks are not possible, please consider changing the arbitrary values so they cover a broader range: 1ms, 5ms, 20ms, 40ms, 60ms, 80ms, etc.. I dont see why so much detail is needed between 5-65ms

That seems a valid point to me. In that sense I would propose something like:
1ms, 5ms, 10ms, 20ms, 50ms, 100ms, 200ms, 500ms, etc. (may be insert 2ms).

But for envelopes I'd rather see ticks as well. Currently I'm adjusting attack and release depending on BPM.

[geremy]

If ticks are not possible, please consider changing the arbitrary values so they cover a broader range: 1ms, 5ms, 20ms, 40ms, 60ms, 80ms, etc.. I dont see why so much detail is needed between 5-65ms

That seems a valid point to me. In that sense I would propose something like:
1ms, 5ms, 10ms, 20ms, 50ms, 100ms, 200ms, 500ms, etc. (may be insert 2ms).

But for envelopes I'd rather see ticks as well. Currently I'm adjusting attack and release depending on BPM.

I have previously asked for % of step length, but ticks would also work!

[XORadmin]

Trigger E1 is half a gate length (eg 3 ticks)  And with tables you can create gates from 1 to 16 ticks and even more when you chain them.
Please get a bit mote into the possibilities that are already there.

[mgd]

I'd love to use tables...on CV16

[BillyAB]

I don't want to use tables every time I set gate lengths. It's about workflow.

[XORadmin]

I don't want to use tables every time I set gate lengths. It's about workflow.

Once you set them up (which takes probably a minute) there is no difference of either put a number in the table column or in the trigger column. However, did you use E1 now for 3 ticks? You surely know then also already about E0 for 6 ticks. Then you got 2 covered already. 
They are no numbers left currently which I could use without breaking any old projects.

[mvdirty]

Doing so would preclude the running of any other table on that track, would it not? That would strike me as an even larger issue than workflow convenience (not that I have any good suggestions off the top of my head to address what Thomas said about being out of numbers.)