Global Synchro and Local Syncro drift with same BPM

[antwan]

Hiya,

Question:

I have a patch on Track 1 with a Global Synchro module, I'm also using a sampler and some math to get a short click on the "1" of each bar. The On outlet is sent into a Data bus.
Then I have an identical patch on Track 2 except that the Global Synchro module is a Local Syncro module, and I'm using a GetBus connected to the On inlet to receive the trigger sent from Track 1.
Both Synchro's are set to 120 bpm sharp.

I verify that both Synchros were resetted, then I press start. First both of the clicks are in sync, slowly they start to drift apart.

How come?
Shouldn't they stay synced, with the same start trigger and with the same BPM, hosted by the same machine?

Thanks

antwan

[senso]

Your patch can be very simplified.

You can put global and local sync on the same patch.
The local will become master anyway.

So you probably don't need a data bus?
The [start cycle] outlet sends at the beginning of cycle.
Just connect it to the restart inlet of the local sync.

works fine, I proceed like that.

[antwan]

i understand that the way you described it will keep the two in sync (cycle start -> restart). this was more like just a test. i dont understand why they would loose sync if they have the same tempo and were started at the same time...?

antwan

[senso]

You are right, normally they should not loose the synchro.
I'll take a look.

[antwan]

thanks man,

antwan

[senso]

tested another time:
If they are at the same tempo and they start at the same time they keep the synchro!

[antwan]

is that with both within the same patch or via data bus to another patch?
also is that Global Synchro.On to Local Synchro.On or Global Synchro.Cycle start to Local Synchro.On or what is your wiring?

antwan

[senso]

You don't need a data bus to transmit global sync from a patch to another.
Use the "Global Sync low CPU" module.
Just connect the "cycle start" of the global to the "restart" of the local.

[antwan]

Hi,

basically what I'm testing is issues with sync drift between two computers running Usine via OSC. This was just a simplified setup of that (a simulation of that on one computer...) and I noticed this sync drift even without the other computer involved...

Thats why I have the data bus, as a simulation of the OSC. This is what I'm trying to solve

antwan

[senso]

I do this kind of remote syncho very often:

on the master:
from a global sync module I take the [Tempo] and [cycle cycle] and send their value to OSC.

on the slave:
then I take a glob sync module and I connect the [tempo] inlet to [tempo] from OSC and the [restart] inlet to the [cycle cycle] from OSC.

Works perfectly; with a small latency but not a real problem, as we suppose that the two computers don't play the same thing!!!!!

You can add On/off, bar length, etc connections in the same way.