[sc-users] Re: [sc-users] Re: Syncing clocks over the network

[nathan@xxxxxxxxxxxx]

On Friday, January 11, 2019 04:01 CET, jamshark70@xxxxxxxxx wrote:

> Finally able to close the loop on this topic.
>
> Nathan:
> > the incomplete ableton link branch is your best bet. link developers have put a lot of work into this problem (peep the source: all kinds of fancy stuff like kalman filters and linear regression) and their solution is bound to be more reliable than some sclang jury rig.
>
> I finally had a chance to try it. It looks like, in its present state,
> it will already work very well for syncing a number of SC clients.
>
> At the moment, I'm not able to test SC <--> Ableton or SC <--> any
> other Link-enabled software. I don't believe that will work in its
> present state. Ableton says it's the client software's responsibility
> to report to Link the time when the sound will hit the speakers. As
> far as I can see, we are reporting the sclang clock time and *not*
> accounting for OSC timestamp latency.

hi james,

i also got a chance to try out SC ableton link, connecting to a friend on ableton. i found a different issue: he wiggled the tempo around too wildly, and scsynth was immediately flooded with OSC messages and crashed. for SC ableton link to be ready for production, we need to find some way to protect against such cases.


nathan


_______________________________________________
sc-users mailing list

info (subscription, etc.): http://www.birmingham.ac.uk/facilities/ea-studios/research/supercollider/mailinglist.aspx
archive: https://listarc.bham.ac.uk/marchives/sc-users/
search: https://listarc.bham.ac.uk/lists/sc-users/search/