Sim'n'Tonic Nome 2 - U-SYNC 2.0 (Windows compatibility is here...)

https://simntonic.com/pages/u-sync?utm_source=mailerlite&utm_medium=email&utm_campaign=usync2_launch&utm_content=explore_usync&ml_recipient=201407065874236744&ml_link=201406945610958424&utm_term=Thu+15+Oct+2026

Changelog is here:
https://simntonic.com/pages/u-sync-changelog

Seems to change the way the software part runs somehow. No longer runs in the menu bar on MacOS, as far as I can tell?

And a new video from them:

1 Like

I installed the update and it seems to remove the little Sim’n’tonic menu bar item on MacOS. Apart from that, seems to still be working. Haven’t really tested any of the new features yet though.

U-Sync 2.0 for Win is a great progress and a new value proposition for Nome and Nome II.

Many Win users start testing and posting their results:

That’s good because following that mass test in real life there will be U-Sync 2.0.1 ff. for sure. :wink:

It’s cool that it auto detects the latency value for you.

Yes but the value it detected for me didn’t match the value I measured when I ran the test myself. YMMV of course.

1 Like

This blog post from them compares jitter values across multiple DAWs to show the improvement the Nome/U-Sync combo brings. It’s all fairly persuasive but I am concerned by this section on Logic and Reason (I’m a Logic user):

Blockquote
Logic Pro and Reason share one timing pattern (†). With U-SYNC, about 23 ticks per run land 33 µs late while the rest stay within 1 µs, and those few ticks are what put both DAWs at about 5 µs RMS. The pattern is the same in two DAWs on two operating systems. FL Studio on Mac (‡) is the only other U-SYNC result above 0.1 µs: a few ticks off by up to 10 µs put it at 0.53 µs, still 2,000× lower than that DAW’s own clock.

I wonder if this is something that is inherent to those DAWs, or whether it is something that can resolved by a software/firmware update?