(02-22-2021, 02:31 PM)XORadmin Wrote: On 1.23A you use tables to get ratcheting (thats what you want). You program the ratch you want or you use one of the table presets (duplet, triplet ...).
In the new release candidate as you saw from depaffect's post you can set direct ratchets from the trigger column.
The regular triggers are not ratchets but retriggers and indeed based on fixed milliseconds.
So on release 1.23A there is no way to get subdivided triggers (related to BPM) from the FX column. Got it.
In the new release candidate how is the retriggering implemented? Selecting a subdivision or better yet, just the number of repeats per row/step (subdividied) would be AMAZING! Please tell me this coming.
I'll check the table presets, thank you.
(02-22-2021, 02:46 PM)mgd Wrote: I don't quite understand why you insist on the FX column.
Both depaffect and Thomas suggested with V1.23A you should use the table column and create an appropriate table.
The newly introduced ratchetting functions require you to upgrade to the current V1.24RC8 which is a release candidate and you may or may not want that.
Kind regards,
Michael
I'm not "insisting" I'm trying to figure out how to perform a simple ratchet. I just got the Nerdseq and my understanding is limited.
There is only 1 table column per pattern, correct?
You can't have multiple FX on row/step 00 of a table column correct?
So subsequent table with mulitple FX commands on separate rows/steps will have to wait until it reaches the row/column with that command. In other words, not instantaneously when the table is called.
Your wasting tables by turning on and off ratcheting which is accomplished by means of triggers and gates which can be controlled by the trigger column. That table can be used for pitch and other FX.