Sim'n Tonic Forums

As to why this is happening, well the only way another software can interfere with U-SYNC is by sending some audio to the "Midronome-do-not-use" audio interface. Maybe that software somehow had the wrong interface selected? I checked all the settings and it wasn't routing any audio to the...

Reporting back here with findings! Over the weekend I got another MacBook which isn't used at all for audio-related tasks (so as fresh as an audio stack can get :D), I installed only Ableton Live on it, the Midronome Daemon, and the U-SYNC VST. The Midronome worked flawlessly, start/stop, following ...

I haven't touched the device since setting up with the beta VST + firmware 2.9.0 but might be a good sanity check :) Well the FW should definitely be updated to 3.0 but you said you did that already? You'll need the Firmware Updater software + the FW 3.0 file - see https://simntonic.com/support/ So...

I did some tests and so far no success :/ Connected only the Midronome to the computer, no other USB devices connected, sound output set to my computer's speakers. Tested through my desk's Thunderbolt dock (Belkin Thunderbolt 3 Dock Pro), a portable adapter (Satechi Type-C w/ HDMI + Ethernet), and a...

I noticed there's an audio device called "Midronome-do-not-use" on Audio MIDI Setup.app, coincidentally I have started getting corrupted audio recorded back from my Analog Heat which I always use to record the stereo output from my whole setup (the Analog Heat is last in the chain as an in...

Hey, Simon! Thanks for the quick reply :) I had at first tried to install the latest .pkg before removal but then noticed I had duplicated daemons and VST since the names didn't match exactly and the installation didn't replace them, after noticing that I removed everything Midronome-related before ...

[SOLVED - the issue was from another software interfering with the U-SYNC Daemon, SoundSource from Rogue Amoeba] ------- Hey, all! I have had my Midronome since one of the first batches, was using the old U-SYNC VST (think it was a beta version) w/ firmware 2.9 perfectly in sync, and noticed my Mid...