Page 1 of 1

Quantize/Snap custom tuplet syntax

Posted: Mon May 13, 2019 4:20 pm
by stubbsonic
Are there some basic rules for the syntax of setting custom tuplets?

"x in y/z"

So, presumably there's a range for X. It is unclear what range y has, and what value z must be. We can assume that the final value of y/z is in "4 beat" units (based on whole notes-- which are 4 beats). I find that tradition to be pointlessly complicated. If we are in 6/8, a dotted-quarter is one beat, and a whole note has no relevance. It is the same with other non-4/4 time sigs. The whole note is just an arbitrary symbol with no intrinsic value.

A simpler formula would be X:Y (steps:beats)

Y beats are defined by whatever beat is defined in the BPM tempo.

So if you set the time-signature such that the beat definition is ambiguous, 3/2, or 6/8, or 5/8-- however the DAW interprets this to define the BPM, the same beat definition is used for the step:beat ratio.

Re: Quantize/Snap custom tuplet syntax

Posted: Mon May 20, 2019 5:15 pm
by Colrik
As far as I know, a tuplet is an irregular division relatively to the meter. So it is an odd division in a binary meter and an even division in a ternary meter.

Re: Quantize/Snap custom tuplet syntax

Posted: Thu May 23, 2019 4:31 am
by stubbsonic
I have tried to enter values into those three slots where it would not work.

It wasn't clear what values it is expecting to see, and what is illegal.

It's not clear if there are limitations for what X or Y can be. I can understand if Z needs to be 1, 2, 4, 8 or 16.

Re: Quantize/Snap custom tuplet syntax

Posted: Thu May 23, 2019 8:09 am
by Support
x = 1..32
y = 1
z = 1, 2, 4, 8, 16, 32


Giel Bremmers

Re: Quantize/Snap custom tuplet syntax

Posted: Thu May 23, 2019 3:38 pm
by stubbsonic
Thanks. That's exactly what I needed.

Y=1

That's where I was breaking the law.

Re: Quantize/Snap custom tuplet syntax

Posted: Tue May 28, 2019 12:25 am
by stubbsonic
It would blow open some doors if Y was able to be some other numbers even just 1-8. But yea, I could see how that is easier said than done.