The first note is pushed to the one... what messes up push forward timings..
Its probably not a bug ..just an easy solution for a otherwise complex programming task...
Even when other companys quantize algorythms are able to handle this
by using an event close to the end of the loop to cover for the missing event at the one position..
So maybe it can be called a conceptional bug..or not finished implementation?
A better and easier solution in my opinion would be to introduce an +/- offset delay parameter for the grooves in the pool..
And do global time shifting with that... i made a feature request for that
[amo] forward shifted groove are not translated correct
[amo] forward shifted groove are not translated correct
mac book 2,16 ghz 4(3)gb ram, Os 10.62, fireface 400,