[F] Software (U-Sync) doesnt connect to Midronome

[firat_shade]

Hi there need some help

i tried everything what is explained in the manual but nothing helps.

i own the first Midronome
System is Macos Ventura
Apple Sillicon M1

anyone knows whats going on ? The Plugin and the Hardware unit is not connected to the software

[Simon]

Hi

Thanks for asking here. If you can give us more information on what's happening it would help a lot.

My first thought: is your device upgraded to FW 3.0?

If so, could you please try the following:

• Unplug your Midronome
• Open the Audio MIDI Setup, in the MIDI Devices window, delete anything with "Nome", "Midronome", or "Nome II" in its name
• Stop the U-SYNC Daemon completely, close your DAW
• Start the Daemon and plug the Midronome
• Check the Daemon status to see if it says "Midronome connected" -> if not then please check there is an audio device called "Midronome-do-not-use" in the Audio MIDI Setup
• If it says "connected" simply start your DAW, load the U-SYNC plugin and it should work

Let me know how it goes!

Cheers
Simon

[firat_shade]

Hi Simon thank you for the fast reply on my post.


I tried to use the bootloader it looks as if it has worked but i cant check it because if i want to use it again to check the current FW, bootloader 1 doesnt do anything.

i Use an Mac M1 with sonoma, i would try to do it on a windows laptop.
But maybe you can tell me how i can check which FW is on the Midronome

[firat_shade]

So i tried a second try to use the bootloader. i used an old windows laptop and it worked the bootloader was sucessfull.

i follow the instruction you send befor but nothing happen.

The it feels like when the plugin is connected to the midronome Daemon they dont accept the midronome hardware, otherwise if the hardware is connected they dont accept the software Midronome Daemon.

Sometimes, Midronome Daemon accepts the hardware connection, but I can't pinpoint the exact circumstances under which the software does this
same with the Plugin in Ableton

As information

Midronome is Updated with the bootloader on you website.
I use an Mac Pro M1 with Sonoma 14.6.1
DAW is Ableton.

On Midi Audio Setup befor your instruction there was midronome and nome 2 i deleted all and now only nome 2 is there.
And in the Audio Setup there is and Midronome do not use device

[Simon]

Thank you Firat that is very useful info! I'll do some investigation on Monday and get back to you here! )
Simon

[Simon]

Hi Firat

So this was an actual bug - really sorry about that!
It is fixed in version 1.0.1 of the U-SYNC software.

You can install U-SYNC software version 1.0.1 from this link: https://download.simntonic.com/software ... -1.0.1.pkg
You can install it on top of the current version, it should upgrade it smoothly.

​​Let me know if this works - thank you!
​Simon

[firat_shade]

Hey Simon,
no worries this is why i am asking
Thank you for your reply i tested the Hardware and the Plugin with the new Midronome Daemon, just working. Solved the problem within the first try
Thank you hope you dont spent to much time to fix it.

Tomorrow i test is with an drumcomputer but i think right now everything is fine

[firat_shade]

Hey Simon,

so i tried to sync a octatrack to the midronome
Midronome Daemon is now showing the Hardware and Plugin as connected
in the Plugin the light is green seems to be everything is okay.
The Midronome is showing the orange Locked led and the input is switched to Sync
when i am starting the DAW and push the play button the midronome doesnt react,

please correct me if iam Wrong

to use the midronome with Usync the only connection is USB and to send the clock signal to a synth Midi 1 & 2
no audio input and no audio output? like the old vst versions

hope you can help me

[Simon]

Yes you only need USB. The "Locked" LED on both the physical device and the DAW plugin should light up orange when you press play.
Is it not the case?

If it is, then all is good and the reason your Octotrack does not track automatically is because you have not set the "autoplay" ("A.PL" setting must be set to "on").

If you still have issues please try disabling the Overbridge stuff on your computer as it may interfere with U-SYNC.

[fffiiissshhh]

Same issue here. I've updated everything to the absolute latest (firmware, bootloader, and USYNC.) Am on Sonoma 14.4 running Ableton Live 11 Suite. Also deleted all the old Midi configs from old versions of midronome as suggested earlier in this thread. Anything I'm missing?
Weirdly, when i try to start usync daemon, nothing happens - should i be seeing something up in my menu bar or an application open or is 100% background? It shows up in Search when i hit command/space, but nothing happens when I hit enter. Activity monitor shows USync daemon is running.

[Simon]

I don't thing this is related to Firat's issue, his was an actual bug in version 1.0.0 which was fixed in 1.0.1.

The Daemon is running in the background, but you should see the "SnT" icon at the top right of your screen. If you do not, please try the following:

* Try to uninstall the daemon and reinstall it again, then start the daemon again
* If you still do not see the SnT icon, please try to open the terminal and copy-paste the following in the prompt and press Enter:

Code: Select all

/Applications/U-SYNC\ Daemon.app/Contents/MacOS/U-SYNC\ Daemon

Then see if you get any error or anything. If it works, you will see nothing in the terminal, and you will not get the prompt back (it will just write a new line as you press Enter and nothing else).

If the daemon is started, then click the icon to see if it detects any device - maybe you need to upgrade its firmware.

Let us know how it goes

Simon

[fffiiissshhh]

I dont see the SnT icon in the menu bar.
I have two daemons in my search: Midronome Daemon and USYNC Daemon. Neither is titled SnT. Both show up in activity monitor as running. No icon in menu bar.
However in terminal, I dont get an error, as you mentioned it just new-lines.
Thanks

[fffiiissshhh]

Edit: i'm silly, the SnT is there in the menu bar, it was hidden because i'm on a mac that hides menu items if you have too many. When i click it it has an option to restart usync daemon. I will try that and report back.

[fffiiissshhh]

Ok, saw two menu bar daemons running - Midronome Daemon and SnT daemon. Quit Midronome Daemon, restarted SnT Daemon, and it updated my Midronome Firmware and is detecting it!

However, now in the plugin in Ableton Live, I'm getting "Plugin is disabled/bypassed" . So close! Wondering if my settings are somehow wrong?

[Simon]

Overall it sounds like you have quite a messy instalation, which can cause many issues. As I've said in my previous post, start by uninstalling everything and then installing U-SYNC 1.2.

There should be no "Midronome Daemon", the new daemon is called "U-SYNC Daemon".

Then make sure you load the U-SYNC plugin (and not "Midronome U-SYNC", that's the old one - normally it should be uninstalled automatically), and if it says "disabled/bypassed", check the plugin is enabled and not bypassed

Simon

[muZikman]

Having trouble getting the U-Sync Plugin to "communicate" with the Nome 2 (or the Midronome, I have both). This is a fresh install of a MacBook Pro w/ M1 and Tahoe 26, if that matters.

The Daemon seems to connect to the Nome ok, as indicated by the "Nome II Connected" in system tray. It will also let me update firmware, etc, and the new beta config tool seems to work ok.

What doesn't work is getting the DAW to connect to the Daemon, via the plugin, having tried new installs of Reaper and Ableton. When I put the VST plugin onto an instrument/midi track, it just gives me "Daemon Not Running".

I have successfully done this on other Macs in the past, so I know what it looks like when it works. Is there a setting in the midi ins/outs that needs to be enabled/disabled for it to function? Is there something in the Mac settings that might be blocking whatever the Daemon needs to communicate?

Not enough of a Mac expert to dive in deep, but super hoping I'm just doing something simple, wrong.

Help? (plz & thankx of course!)

[Simon]

This is a pure OS thing, either you have another Daemon or a rest of one still running, or maybe a rest of a previous plugin running.
Usually restarting the whole machine clears all these "ghost processes" and everything works
Simon

[muZikman]

Hi hi,

I just got done with a fresh re-format of my Mac, just so I knew 100% that it was fresh, and am still unable to get the U-Sync plugin to connect w/ the Daemon (which otherwise seems to be working). I have the plugin installed (VST3) into Ableton and Reaper, and both give me the same "Daemon is not Running" message.

Shows connected to USB in the Daemon's menu, and have made sure everything is a new install, and that firmware is up to date.

I don't remember having any issues w/ installs onto other machines and am super scratching my head - does anyone else in the internets have any ideas??? I'm so close to being sync'd up I can practically taste it, just need this U-sync thing to play nicely.

Please/thanks!

[Simon]

Here is another thought: maybe you have a different plugin and daemon version.

Try uninstalling the Daemon and deleting all files with the name "U-SYNC" in /Library/Audio/Plug-Ins/VST3/ and /Library/Audio/Plug-Ins/Component/

Then restart the machine, download U-SYNC 1.3, and reinstall everything.

Simon

[muZikman]

Simon - super thanks for the replies.

This was a FULL re-format (aka cleaned the hard drive, started fresh). On first bootup I installed/activated Reaper, and then installed the U-Sync Daemon/Plugin from the web. Literally I wiped everything with the sole intent of trying to get U-Sync to work.

Would it make sense to go back and try older versions? If so, this set of steps might help me to drop back down and try one of the first versions - I saw those available for download on the website.

I will plan to try my orginal midronome again tonight, just in the event that it's a hardware issue (thought doubtful).

Willing to try anything at this point!!! ...except another reformat

Thanks team!

[Simon]

Ok well you definitely do not need to wipe your whole OS to get U-SYNC to work.

Usually this is caused by:
1. a (second) daemon still running in the background and the plugin is connecting to that instead of the actual daemon you can see
2. a plugin connected to a non-existing daemon
3. a mismatched version between plugin and daemon

In cases 1 and 2 restarting the daemon/plugin or the machine solves it. In case 3 uninstalling and reinstalling works.

My next guesses are:
A. there is another software running on your machine blocking the connection between the daemon and the plugin
B. there are new macOS permissions which the daemon and/or plugin are lacking to communicate with each other

Any thoughts on those two?


PS: this has nothing to do with the hardware, you do not even need a device to try it. If this was working and no device was connected, then the plugin would show "no device is connected" instead of "Daemon is not running"


EDIT: Ooooh wait, I just realized you wrote "Tahoe 26", I had to google this to check it. This is a macOS beta preview!!! Well then this might very well be an issue with the new macOS - I'll try it and let you know!

[muZikman]

Thanks for your reply, Simon. I appreciate it.

Ok well you definitely do not need to wipe your whole OS to get U-SYNC to work.

I understand. This is a new-to-me (used) Mac, and it's my first. I've used them in my industry here and there, but have never had one in my possesion until now. Wiping it was a good double-check for me, just to know I was starting with a fresh copy of the OS. When THAT didn't correct the U-Sync issue, I got even more confused. I'm not at all new to IT troubleshooting, but like I said - this is the first Mac I've owned and feel responsible for.

My next guesses are:
A. there is another software running on your machine blocking the connection between the daemon and the plugin
B. there are new macOS permissions which the daemon and/or plugin are lacking to communicate with each other

Any thoughts on those two?

Given my full rinse of the Macbook, I don't think that "A" holds much water. I'm not sure what software would be blocking it, the only software on the Mac at this last test was Reaper and U-Sync (and then Ableton, just to doublecheck).

I do suspect "B" might be part of the issue, and checked into the permissions allocated the Daemon. Even after giving it full read-write though, it wasn't working. This is where I claim naivity though, not knowing having a high enough Nerd score to really understand how to affect things.

EDIT: Ooooh wait, I just realized you wrote "Tahoe 26", I had to google this to check it. This is a macOS beta preview!!! Well then this might very well be an issue with the new macOS - I'll try it and let you know!

If I were a betting man, I'd put my money on this. I didn't know what about my system was relavent, but glad you did catch that on a re-read. I'm happy to sit in a holding pattern where I'm at with this, and let you have a chance to do some testing on your end. Let me know if I can help. As I mentioned previously, I've seen U-sync in action and all I can think is...

[Simon]

Alright so I actually updated my main machine to macOS Tahoe as I was worried there was a bug to solve there (probably a good thing to test new macOS early anyways), but no it still works perfectly fine!

Just to be 100% sure: if you go to "/Library/Audio/Plug-Ins/VST3/", delete the U-SYNC.vst3 there, restart Ableton, then there is no U-SYNC plugin to find in Ableton, correct?

If so, then you exit the Daemon, and then move the Daemon app to the bin.

Then go to System Settings -> General -> Login Items & Extensions, delete the U-SYNC Daemon from the "Open at login" list (this should not make a difference, it's just the auto-start, but you never know).

Then download the U-SYNC installer from https://download.simntonic.com/software ... -1.3.0.pkg
Run the installer, leave everything default, and when the OS asks for some permissions say yes.

At this point the Daemon should already be started, you can start Ableton and load the plugin to see if this works.

I just tested this again on a mac mini M2 with Tahoe and everything works. If it still does not work I would be happy to jump on a remote call to sort it out.

Simon

[muZikman]

Cool,

Thanks - will try these steps and anything else relavent. Appreciate the offer to help beyond that - I'll let you know if/when it's necessary.

On one hand, I'm glad it's not the new Mac update that's throwing things off, but that means I have to go back to scratching my head!