70.3 bpm. Otherwise you can’t make music with OT. ![]()
@Bryan_T made a list…
70.3 bpm. Otherwise you can’t make music with OT. ![]()
@Bryan_T made a list…
I found it too, very intersting. I love Octatracking!
I have a spreadsheet! It all has to do with the recording buffer and wanting to avoid gaps/clicks at the loop point. I had a long thread where I worked through the math and learned a lot about how the OT works.
That said, my general take on the OT is that it sequences really well. The recording buffers are somewhat compromised due to that. I truly hope that the LFOs aren’t compromised.
octatrack_clickless.numbers (1023.7 KB)
The number of projects that I start at 65.6 bpm is kind of embarrassing.
Almost diabolical !
I am probably too lazy, sometimes I start at 120 bpm, it is our French national anthem tempo ! ![]()
No patriotic reasons though…
On Tempera, 88 bpm to match max rec length, 11s !
The devil’s slightly slower brother.
I also have a bunch at 275.6, but those are for sound design purposes. What a fun box.
I do wonder how the LFO Designer will behave at 275.6.
I guess well. Lfo designer allows to multiply a triangle lfo speed by 8 btw.
My doubts are about Lfo Designer with Sync Trig, at pattern’s beginning.
Is the issue literally only on the first trig, but only on the 1st, 3rd, 5th, … times the pattern plays?
Not only on first trig, and I am not sure about working cycles.
Microtiming and speed 33 vs 32 solves it (on 16 steps, not sure with 64 steps)
Apparently solved using speed 4 mult x32 vs speed 32 mult x4.
Don’t ask me why ! Maybe speed isn’t precise in that case.
I compared square and designer on VOL using Sync Trig and same sample with phase opposition : perfectly null.
Differences using slices as dest…![]()
Flex of course.
That’s wild!
8x16? 16x8? 2x64? 64x2?
Not perfect. Better with 2x64 but perfect with 4x32.
![]()
Interesting!
I’m back home with my OT and confirm that I get the same type of behavior with combinations of Mult/Spd. Quirky.
I’m playing at BPM = 153.1. Sixteen slices on sixteen trigs. I’m showing things as (Multiplier, speed).
Work:
4x, 32
16x, 8
64x, 2
Don’t work:
2x, 64
8x, 16
32x, 4
How’s that for inconsistent?!?!?
At least there are working settings !
And the weird thing is that step lfo seems to behave normally with other destinations.
Would be interesting to compare with START mode (vs SLICE mode)
Forgot to mention that i was using the 2*Slice-1 mapping for the LFO values.
Here’s a simple example. I cut the Moog (nearly) scalar thing into 16 slices on two separate tracks. LFO at 8x and 16.
Since I can’t help myself, I mapped the crossfader to speed with two different speeds as the B value, plus some filter, and reverb mix. A quick way to take something monotonous and transform it.
With lfo designer I like to modulate speed with % trig conditions (fast odd speeds for randomness in Hold mode) and assign Speed 0 to a scene in order to freeze the value…
(ex with comb filter)
I played around with the Amen file you posted. Unfortunately, it made me realize that the mult/speed settings that I thought were working do not always work. This was at 137.0 BPM.
Bummer.