“I guess by sending out the clock pulses ahead of time so that the device “feels” in sync even though it is playing earlier than it should?”
That’s why it’s starting 1 Bar later…but then you can do 1 to 4 Bars…so when you have a 2 Bar Loop in your Machine it will be not 1 Bar Off when you choose 2 Bars.
Timetravelling is not yet there ;).
Well clock stability is whole crazy story… even if you have a stable clock at all, but your machine has a laziness to interpret, then there is nothing you can do about. Also I think that complete TightClocks would be too robotic and somehow I don’t like how that feels. But that is just my own opinion. On the other Hand its nearly impossible when you do the Math. there will always rounding errors since Midi Ticks Scheduled in a Grid against Samplerate …how would you do that?
Calculate as an example 1/4th Note with 126 bpm at 48000khz…so you end up with a rounding of 476ms and 22857 samples…in fact its 22857.142857142857143 samples. Multiply by 4 to a Bar
is 91428 against 91428.571428571428571…multiplied by 4 is 365712 against 365714.285714285714286…and that’s just 16 Bars …so how do you handle the sampledrops?
Anyway I feel it sounds quite nice an has that little 808ish …it’s quite thin in what’s under the hood…I like to keep it that way, or optimize it a bit more…since to many background activities need more and more attention in scheduling then. And I don’t want to go too much into sience.
For me it should be musical in any way.
I’m not quite sure when it will be released. I have so many ideas and do it all in my spare time.
But it should’t be far. You can always improve things later.
It’s was just an idea in the first place.