Sim'n Tonic Forums

Short description of the issue: tried with Nome II and same result. At the moment, Pro Tools, USync plugin, daemon, ams and mac all see the Nome II. On playback, PT and Usync operate as if Nome II is syncing however the Nome II is unresponsive to PT. Then it breaks further - USync doesn't see the Nome II, but daemon, ams, mac all see the Nome II. Downstream midi gear reacts properly to pressing play on the Nome II.

Setup (devices connected and how): Macusb port>Nome II usb

Steps to Reproduce: unreliable. once it breaks, which is fairly quickly, it's hard to get working again.

Expected Behavior: it just works!

Actual Behavior: always breaks when saving while in playback

Nome generation (I or II) and Firmware version: I have both Nome II & Nome I - same behavior. I believe there is a USync aax plugin problem.

More info: see attachments

Hi Charles

Thanks for reporting!

Is "AMS" Audio MIDI Setup?

I think this problem is related to the fact you have 2 devices. I noticed this bug a while ago, the U-SYNC daemon gets confused when there is more than one Nome (I or II) connected to your computer. For now I have added to the manual that U-SYNC simply does not support multiple devices and can easily get confused if there are more than one connected at the same time. I hope to solve this in U-SYNC 1.3 / FW 4.x coming after FW 4.0.

Try restarting everything and making sure only one device is connected at a time (Nome I or II - it should both work exactly the same), and let me know if you still have those issues.

Cheers
Simon

Hi Simon, I only have one Nome device connected at a time. Yes, AMS is Audio Midi Setup. For some reason, the aax plugin is not seeing the Nome I or II while the mac, ams, daemon are. Any ideas?

I'll do some testing today but this is not something I have seen before it might something specific in your setup that is breaking it. I'll also test the other bug with the saving while in playback.
Any other info you could tell me about your software/OS setup that is particular?

Simon

EDIT: I could not reproduce this issue at all - can you also tell me what the plugin window shows when this happens?
Re-reading your first post I am also very confused as to when this actually happens... You wrote "always breaks when saving while in playback" -> so is this related to the other bug? If not, when does this happen? sporadically, randomly? Or it just never works? If it is random, please try to find out which specific action triggers the issue, that will help the resolution a lot, thank you.

And:

cgoodan wrote: ↑31 Jan 2025, 20:25 More info: see attachments

Clearly missing some info here?

cgoodan wrote: ↑04 Feb 2025, 17:52 Hi Simon, I only have one Nome device connected at a time. Yes, AMS is Audio Midi Setup. For some reason, the aax plugin is not seeing the Nome I or II while the mac, ams, daemon are. Any ideas?

Hi Charles

As written in the other bug topic ( viewtopic.php?t=476 ) the issue with the "DAW is not supported" is solved.

Regarding this issue, I have been doing a lot of testing and devlopment on U-SYNC those last few weeks, preparing for both U-SYNC 2.0 and U-SYNC for Windows (still a huge secret for now so shhh ).

It's still very strange that you doing anything in AMS makes any difference, since U-SYNC does not use MIDI at all.

The only case where I have experienced similar behavior to what you describe was on my macbook air M2 (base model), while it was plugged in the docking station. The laptop was very hot and generally slow (both extremely rare) and I could see the U-SYNC Daemon simply failed to send the initialization command to the device.
So

• from the point of view of the device, there is no daemon connected so it won't react to anything
• from the point of view of the daemon, the initialization command was sent so the device is "connected"

That fits the behavior you experienced.
(if this is the actual issue, it is of course solvable by code (the Daemon could just keep trying until the device responds), but if the Daemon fails to send a simple initialization command to the device, it means communication is not reliable, so the chance that everything else will fail afterwards is very high - which will create weird drops, disconnects, etc.)

In my case I just had to deactivate/reactivate the plugin to make it work - and it would fail about 60% of the time. I think it's a macOS mechanism when the device gets hot to slow down everything (to prevent overheating), and that means U-SYNC messages are not sent properly.
When I disconnect the docking station, the laptop goes back to normal temperature, and it works 100% of the time.


I would suggest the following to investigate this further:

1. Please check your OS version (is it up to date?), and your machine - try closing down as many other programs as possible, check the CPU and RAM usage, and check the computer's temperature
2. Please check with another DAW (any of the supported DAWs, many of them have free trials, and AUD Luna - which will be supported soon - is free), see if you have any similar issue where the plugin shows connected but nothing happens on the device. If the issue is the same I had with my laptop, then it is between the Daemon and the device, it has nothing to do with the plugin

Looking forward to hearing what you find

Simon

PS: I understand you probably don't have much time to spend on resolving this, but since the issue is not reproducible except on your setup, it cannot be solved without you involved. We can also let it be