They should always stay in sync but it has been buggy for a little while. I'll try to work out why.. It's probably something quite small.
1 Like
Ah it's a little more complicated
edit Ok I committed a quick fix to main @ndr_brt if you want to try it out!
2 Likes
Ok, now it's working, a setcps <value> changes tempo on both the tidal instances.
Just a question, if I want to connect two tidalcycles on two different computers I just need to set the sTempoMV address like it's stated here: Network tempo sharing - TidalCycles userbase?
I need to expose a particular port or the sync works on the 6010 out of the box?
I know, I could just try it, I will do it in the next days, but I'm just trying to understand that better 
Both computers will work relative to their local clock. So for it to work, those local clocks will need to be in sync. You can use the usual ntp for this but it can take a long time to get in sync (you can use ntpdate for an immediate correction, that can help a lot) and you might hear occasional glitches, especially if on unstable wifi. PTPD is a lot better, it's designed for computers on the same LAN.
1 Like
hi alex can you recommend a good tutorial for installing & configure PTPD? and how we could enable it to work with tidalcycles?
I don't know of a tutorial, but if I remember right, you just run it.
1 Like
I would like to report a strange behavior in syncing two tidal instances on two different computers.
Me and @ortensie_27 are preparing a "duo" live show, we followed the instructions on documentation (Multi-User Tidal | Tidal Cycles) and we did:
- installed
ptpdon server - launched tidal on server
- launched tidal with the server ip valued in
cTempoAddrfield on client
at this point, any cps change by the server it's not reflecting on client, but it does other way around, so the client is able to change the cps on server. It's supposed to work like this? the server has no control on it?
For everything else this work nicely, it's a lot of fun play with someone else.