+- XOR Userforum (https://forum.xor.eu)
+-- Forum: Products (https://forum.xor.eu/forumdisplay.php?fid=3)
+--- Forum: NerdSEQ (https://forum.xor.eu/forumdisplay.php?fid=6)
+---- Forum: General Questions (https://forum.xor.eu/forumdisplay.php?fid=17)
+---- Thread: Timing Resolution, Ticks, ppqn, track clock multipliers and groove (/showthread.php?tid=1442)
Timing Resolution, Ticks, ppqn, track clock multipliers and groove - misk - 09-07-2022
I come from a background in Renoise and one thing I love about Renoise is the ability to adjust the lines per beat (LPB) to achieve higher resolution at the expense of faster patterns (shorter length as well). I would usually use 8 lines per beat, and the default tick value (12 ticks per line). I understand that Nerdseq uses a default value of 6 ticks per line, and that is EXCELLENT for modular, as well as standard for MIDI (24ppqn is great for clocking!).
But what is the best way to properly run Nerdseq's modular tracks at double the resolution? I read an old post a while back that mentioned you could run the track clock at 2x to get a higher resolution but that the way XOR implemented that double-time speed was by multiplying the ticks per line in the background or something?
I'm not interested in *actually* outputting proper 48ppqn clock from Nerdseq, but I am interested in twice the resolution for sequencing.
If I run say, all tracks clock at 2x and set the Default Groove Ticks to 0C (12) will I actually have the resolution of 12 ticks per line in a table? will I have finer control of the groove column to adjust swing on a per-line basis, or is it still calculated behind the scenes as 6 ticks * 2 even though it's presented to me as 0C? was that ever changed?
effectively i'd like to know whether i'm actually increasing my tick resolution when I combine a 2x track clock multiplier with 12 ticks per line, in a way similar to doubling the LPB function in renoise, without having to double my bpm.
kinda like this:
RE: Timing Resolution, Ticks, ppqn, track clock multipliers and groove - mgd - 09-08-2022
(09-07-2022, 02:50 AM)misk Wrote: If I run say, all tracks clock at 2x and set the Default Groove Ticks to 0C (12) will I actually have the resolution of 12 ticks per line in a table? will I have finer control of the groove column to adjust swing on a per-line basis, or is it still calculated behind the scenes as 6 ticks * 2 even though it's presented to me as 0C? was that ever changed?
effectively i'd like to know whether i'm actually increasing my tick resolution when I combine a 2x track clock multiplier with 12 ticks per line, in a way similar to doubling the LPB function in renoise, without having to double my bpm.
Hi misk,
why don't you just try?
It is simple enough to do so
...you'd have to do it anyway, assuming I'd say something like "doubling the track clock and the groove ticks will give you twice as many ticks at the same effective BPM"
Kind regards,
Michael
RE: Timing Resolution, Ticks, ppqn, track clock multipliers and groove - misk - 09-09-2022
Haha, that's kind of a good point you have there Michael!
I would *LOVE* if there was some sort of tempo feedback when I adjust the ticks per line default value, so at least I'd know where about my tempo is if I wanted to say, get crazy and shift it to 1 tick per line. I know you can just multiply the bpm by ..uh 6 right? but typically even basic math isn't part of my workflow
I'll do some experiments with ticks per line on the nerdseq at a slow tempo next time I get the chance & report back. In the meantime yeah, I've just been running my tracks at 2x across the board.