-
-
Notifications
You must be signed in to change notification settings - Fork 255
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tidal sync not working? #681
Comments
It seems past improvements to fine-grained cps changes have broken network sync. The cps can change from one event to the next. To calculate this accurately, the tempo is manipulated from one event to the next, during a frame. Previously, the cps was changed via a shared clock server over OSC. This server still runs but no cps is shared. Probably some changes need to made to the old clock server code, to cope well with these cps changes which can be very frequent. Or longer term we could switch to use superdirt as a clock server, for easy integration with link etc.. |
@ndr-brt noticed that two processes are perfectly in sync if the cps has never been changed, up until it is next changed |
It could be nice to move the clock server to superdirt, and then benefit from the new link support in supercollider. That would mean superdirt would need to keep a list of current tidal clients and update them when the cps changes though. For now tidal could send out a cps update to the existing clock server once per frame, if it's changed that frame. |
This works:
|
@yaxu it works also without the
|
Running two streams, and they don't synchronise..
The text was updated successfully, but these errors were encountered: