Live data from Hacker News

Show HN: Beatsync – perfect audio sync across multiple devices

github.com

31–40 of 135 posts

Re: Show HN: Beatsync – perfect audio sync across multiple devices

#36

Very cool! As someone who doesn't know much about the topic, I'm surprised that "millisecond-level accuracy" is enough. I would have imagined that you need to be accurate down to some fairly small multiple of the sample rate to avoid phasing effects. Do you have any interesting insight into that question?

If you look at professional distributed audio systems (Dante, AES67 etc) you'll find that they all require PTP support on the hardware to achieve the required timing accuracy, so yes, you need However, it very much depends on what your expectations are, and how critical your listening is. If no one is looking for problems, it can be made to work well enough.

Re: Show HN: Beatsync – perfect audio sync across multiple devices

#39

Very cool! As someone who doesn't know much about the topic, I'm surprised that "millisecond-level accuracy" is enough. I would have imagined that you need to be accurate down to some fairly small multiple of the sample rate to avoid phasing effects. Do you have any interesting insight into that question?

Yeah the threshold is pretty brutal, but it is enough. Experimentally, I'd say you need under 2-3ms but even at 1ms you can start to hear some phase differences. Most of the time, I think my synchronization algorithm is actually sub-1ms, but it can be worse depending on unstable network conditions.

How are you measuring this? I'm surprised the Web Audio API scheduling system has that much insight into the hardware latency.

Re: Show HN: Beatsync – perfect audio sync across multiple devices

#40
post #34

Very very cool idea, but this is a bummer: "Optimized for Chrome on macOS. Unstable for other platforms..." Once that changes (at the very least, the macOS part), I can't wait to play with it!

It works on other platforms! Just not as smooth as Chrome.
Post reply on HN