I did some testing where I loaded the same track in both decks and
synced them together. Then on the first track I did some rolled loops
while the second track played back uninterrupted. If there was any loss
of precision, the tracks would get out of sync.
As long as latency is fairly low
It's not bad as far as accuracy but it's probably not ready for general
consumption due to underlying problems in the engine. There's a lot of
popping on the loop boundaries because we don't do any crossfading, and
sometimes I feel like there's problems during the seek after slip is
disabled.
I feel like there's problems during the seek after slip is
disabled. It's like there's a moment of silence between the release of
the slip mode and the reseek to the new position.
I think you can hint the position to the CacheReader or RAMAN to fix
that. I was mostly worried that the loss of
I just noticed Owen added a slip mode to his hacks branch. I'm just sending
this out to comment on it and ask Owen: how accurate is it? This would be
excellent to use with my new MIDI Fighter Pro mapping.
In the future we should attempt to make it possible to implement it in MIDI
Script, not
