Sim'n Tonic Forums

Hi all!

Problem
Since the update for the NOME I to prepare for macOS Sequoia, I've been having an issue with the display jumping or flickering. I've checked my cabling and everything seems fine (to be honest, nothing changed, but I checked). The power and data are separated (using an Arturia adapter), and it seems like the jumps/flickering aren't affecting my setup. Everything seems to stay in sync, but it's still a concern.
Does anyone else have this and can tell me how to fix it?

Setup
USB Power/Data splittet via Arturia adapter, Ableton and Plugin with a dedicated output on the sound card. As I said, nothing has changed in the cabling, only the update has been installed.

Nome generation (I or II) and Firmware version:
NOME I; 3.0

More info:
Video (on my OneDrive, MP4, 5MB): https://1drv.ms/v/s!AhWHEQVffIK472PP2Po ... C?e=SgEmpE
The NOME I was always connected with the DATA to a USB Hub, to make sure everything is okay with the hub, I connected it direct to the laptop. The issue is the same.

That does sound strange indeed - thanks for reporting!

Can you please make sure that:

• The U-SYNC Daemon is fully stopped
• There are no other cable plugged in your Midronome (only the USB cable)

When you do these, is the problem still there? If it is, can you try powering it from a simple USB phone charger (i.e. not connected to the Midronome)?

If it is not, then please start adding things one at a time to see which one creates the issue.

Thanks
Simon

Hi Simon,
Thanks for your quick reply! I really appreciate it!
Of course, I stopped and restarted the service before posting here, but that didn't help.
I suspected the USB hub, but I also had the flicker with a direct data connection to the laptop. I followed your advice and used a power bank and - no more flickering! What the hell...?
Unfortunately, Ableton had updated in the meantime (and I always install these updates automatically) and I went back to the old power supply - everything works now.
I swear I'm not stupid.
I will keep an eye on this.
Best regards,
Mika

Well that's great news either way
But yes this could be caused by anything trying to change the tempo on the device, either over USB (U-SYNC, or MIDI CC messages) or over the analog input (in 24P or tap mode).

Please do not hesitate to write here if you see it again or have any more info about the matter

Simon