-
Notifications
You must be signed in to change notification settings - Fork 76
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
Support Ableton Link via SuperDirt instead of Carabiner? #185
Comments
Yes I think so. |
I am not sure how SuperDirt currently does scheduling, but it appears to not use |
All the timing is done by tidal, superdirt just uses the timestamps that tidal produces. It is a bit difficult to tell how these timestamps could be processed to fit on the link clock. |
The devil is in the details of course. How will Tidal sync to SC's LinkClock? You can't assume LinkClock will be strictly monotonic because it's constantly making micro-adjustments to match other peers on the network -- so you couldn't use the network to identify a starting time and then let Tidal run under its own power. You'd have to slave Tidal to SC's clock, using some kind of constantly-running network messaging that also absorbs and compensates for network jitter... ... which is all the stuff that Link is already doing for you, better than you could rearchitect it for yourself. (I say that having tried and partially failed to write my own network sync for SC. It is harder than you think.) My opinion is that you won't actually save any effort this way. It would be easier to import the Link library directly into Tidal, and get rid of carabiner that way. |
Good points @jamshark70. I'll close this for now. |
SuperCollider 3.11.0 supports Ableton Link: https://github.com/supercollider/supercollider/releases/tag/Version-3.11.0
Currently Tidal supports Ableton Link via a separate tool called Carabiner: https://forum.toplap.org/t/link-support-preview/418/16
Would it now be more streamlined/maintainable for Tidal users to access Ableton Link via SuperDirt?
The text was updated successfully, but these errors were encountered: