I think there is an off-by-one-buffer error in the sync code. When you
push the sync button, it makes a difference if the deck being synced is
processed before or after the deck being synced to.
On Thu, 2014-08-07 at 11:07 -0500, Ryan Kramer wrote:
> I made this code change
> (https://github.co
Do you know if it's syncing forward or backwards, for instance?
On Tue, 2014-08-12 at 18:43 -0400, Owen Williams wrote:
> I think there is an off-by-one-buffer error in the sync code. When you
> push the sync button, it makes a difference if the deck being synced is
> processed before or after th
Good call, this does look like a 2nd-deck sync issue. Once I nudge the
decks into sync, I can push "beats_translate_to_sync" on either deck, as
well as the deck 1 sync button, and everything stays in sync. But as soon
as I hit the deck 2 sync button, deck 2 jumps forward by about 2000 samples.
And
