[RELEASED] Firmware 3.0 & U-SYNC 1.0

[Simon]

STATUS: Released - update on Mac using the U-SYNC Daemon, or update on Windows using the Firmware Update software.
(download them both on the Sim'n Tonic Support page)

IMPORTANT: this upgrade modifies the settings An.1 and An.2, their value will be reduced by 1 after upgrading to 3.0. So make sure to adjust their value after upgrading to keep the same configuration.

----

New Major Feature:

• U-SYNC: simple, precise, and reliable synchronisation with DAWs

Fixed issues:

• MIDI Forwarding to MIDI Out 2 is not working on Mac - https://forum.midronome.com/viewtopic.php?t=369
• Midronome PLAY flashes in 2.4.P. - https://forum.midronome.com/viewtopic.php?t=297
• Preventing conflict between U-SYNC and MIDI Commands by deactivating Start/Stop commands when using U-SYNC and Autoplay

Other changes/improvements:

• All external sync modes now start right away
• Sync modes: 2.4.P. has been removed, and MidroSync ("Syn") is now hidden
• MIDI SysEx message limit for forwarding is now 500 bytes - https://forum.midronome.com/viewtopic.php?t=338
• New MIDI Commands to start as MIDI CC - https://forum.midronome.com/viewtopic.php?t=379
• The USB-MIDI interface "Clock Only" has now been removed (as part of https://forum.midronome.com/viewtopic.php?t=369 mentioned above)
• The analog speed settings (An.1 and An.2) now have a value of "0" to turn off the clock
• General improvements regarding synchronisation
• General improvements regarding USB communication

[MPrinsen]

Any update on the ETA?

[Simon]

ETA is this month

[MPrinsen]

Awesome! looking forward to it I'm checking this forum daily :p

[Dave]

ETA is this month

Fantastic!

Thanks for continuing with this labor of love, Simon.

[MPrinsen]

I'm actually pretty excited for the "combined" 24P/2.4.P. mode, as this (if I understand correctly) allows for immediate start upon receiving pulses (like 2.4.P. always did) and also us Midronome as master clock when you're not sending it pulses form your DAW (like 24P always did).
Previously, we had to choose between either of the two.

I love being able to switch between using Midronome synced to my DAW and using Midronome as the master, without fiddling with setting.

[Simon]

I'm actually pretty excited for the "combined" 24P/2.4.P. mode, as this (if I understand correctly) allows for immediate start upon receiving pulses (like 2.4.P. always did) and also us Midronome as master clock when you're not sending it pulses form your DAW (like 24P always did).

Correct And you can try this already now, it's a Firmware improvement so it does not matter if you are using Mac or Windows

I love being able to switch between using Midronome synced to my DAW and using Midronome as the master, without fiddling with setting.

Well U-SYNC is particularly good at that, in fact the transition from DAW to master and from master to DAW is extremely smooth

Simon

[MPrinsen]

I'm actually pretty excited for the "combined" 24P/2.4.P. mode, as this (if I understand correctly) allows for immediate start upon receiving pulses (like 2.4.P. always did) and also us Midronome as master clock when you're not sending it pulses form your DAW (like 24P always did).

Correct And you can try this already now, it's a Firmware improvement so it does not matter if you are using Mac or Windows

I love being able to switch between using Midronome synced to my DAW and using Midronome as the master, without fiddling with setting.

Well U-SYNC is particularly good at that, in fact the transition from DAW to master and from master to DAW is extremely smooth

Simon

Ah that’s great! I thought maybe the update tool was only available for Mac, but the only thing that is restricted to Mac yet is the U-Sync software? Cool, hope to be able to test the new firmware this weekend

[Simon]

the only thing that is restricted to Mac yet is the U-Sync software?

Correct - sorry for not making that clear enough, I'll update the beta testing page

[telder55]

Very excited to test the U-Sync feature out this weekend! I think this will be finally the perfect sync solution for my studio set up been a long time coming!

[Dave]

I'm actually pretty excited for the "combined" 24P/2.4.P. mode, as this (if I understand correctly) allows for immediate start upon receiving pulses (like 2.4.P. always did) and also us Midronome as master clock when you're not sending it pulses form your DAW (like 24P always did).
Previously, we had to choose between either of the two.

I love being able to switch between using Midronome synced to my DAW and using Midronome as the master, without fiddling with setting.

As long as I still get to choose if it starts auto-playing or not. Sometimes I want that, sometimes I don't. It works great as is < 3.0.

[Simon]

As long as I still get to choose if it starts auto-playing or not. Sometimes I want that, sometimes I don't. It works great as is < 3.0.

Yes that's the A.PL (AutoPLay) setting, this has not changed

[muZikman]

Pretty sure I already know the answer to this question, but just to check...

I am currently using my Midronome to send clock to my hardware directly by using an iConnectivity MioXL. Does/will the U-Sync software require the midronome be plugged directly into the computer, or do we think it may still function through a midi matrix like the mio?

Thanks!

[Simon]

Does/will the U-Sync software require the midronome be plugged directly into the computer, or do we think it may still function through a midi matrix like the mio?

Hi Zach This is not something we have tested but feel free to try! In my experience though, the simplest USB setup the better. So ideally no USB hubs or similar, just straight to the computer, that will definitely give the best results. But I know some beta-testers used it with a hub and said it was working fine, so it might work fine as well with the mio.

Note that this only affect the USB connexion though, you can always use your mio to manage the MIDI ports, getting the Midronome to send the clock to your mio and then forward stuff to your machines will not affect U-SYNC

Simon

[Antonb]

Great job tanks a lot! I Hope you will do it for Windows to

[1vl]

Thanks for all the work and the great update, Simon!

I know that there are complex advances involved (U Sync, etc.),
but the "Start via MIDI CC" makes me happy right now.

[HappyClocker]

Hi,

I've read the FW 3.0 release notes. Nevertheless I don't understand whether it makes sense to update to FW 3.0 considering my relatively simple usecase (I won't need MIDI CC control in near future).
... and FW 2.0 VST plugin works for me when I want to sync my Midronome to Ableton's tempo or measure changes.

So what would be FW 3.0's key benefits for me?

EDIT: THX for the continuous development!

[Simon]

So what would be FW 3.0's key benefits for me?

Well you don't have to upgrade, but there is no reason not to
(except this bug! but hopefully this is soon solved in a 3.1 version)

The big thing about 3.0 is definitely U-SYNC which you will not be able to use (for now), but each new version solves minor bugs and issues, some of them written in detail in the changelog, and some as part of the "general improvements" statement.

Note that you can freely upgrade and downgrade at anytime

[HappyClocker]

Thank you ! Then I will wait for FW 3.1.

[Simon]

(except this bug! but hopefully this is soon solved in a 3.1 version)

Quick update: this has now been investigated, this is not a bug

[pauljove]

howdy everyone

i love my midronome and so excited for usync (finally back in the studio) i've done all the instructions but the plug-in does not show up. im running logic.
any help would be greatly appreciarted, thank you!

[spacialrob]

Hi Simon,

Is there a way to disable constant clock in 24P mode unless it's being received by the DAW (using Windows w/old plugin)? I know that's what 2.4.P. did before, but I wasn't sure if there was a hidden option that would allow me to stop it from running on its own while there's no transport from the host. The reason being: I'm using a looper and sometimes don't want it to sync unless I'm playing the DAW tempo

[Simon]

howdy everyone

i love my midronome and so excited for usync (finally back in the studio) i've done all the instructions but the plug-in does not show up. im running logic.
any help would be greatly appreciarted, thank you!

Hi Paul, sorry to hear, check that the plugin AU file is in fact where it is supposed to be ( in /Library/Audio/Plug-Ins/Components ), and if it is, open the Plugin Manager of Logic to refresh the list - see if the U-SYNC plugin appears there anywhere.
If that does not help, please do not reply here and create a separate topic instead - thank you

[Simon]

Hi Simon,

Is there a way to disable constant clock in 24P mode unless it's being received by the DAW (using Windows w/old plugin)? I know that's what 2.4.P. did before, but I wasn't sure if there was a hidden option that would allow me to stop it from running on its own while there's no transport from the host. The reason being: I'm using a looper and sometimes don't want it to sync unless I'm playing the DAW tempo

Hi Rob, yes that's a great point but unfortunately not possible at the moment. But it's an easy feature to implement which will probably make it to the device soon - I've just been very focused on U-SYNC and the coming new batch lately
See here: viewtopic.php?t=340

[Foksadure]

G'day Simon.

I think you should send a Midronome to Ricky Tinez, for him to review firmware 3.0 on Mac.

https://youtu.be/zxjun514dUE
https://youtu.be/NbSlkRi6OVE

That would be an honest comparison over the E-RM Multiclock, and he'd be confused even more.

[Simon]

I think you should send a Midronome to Ricky Tinez, for him to review firmware 3.0 on Mac.

Ha you're not the first one to suggest this But Ricky said he won't find it useful unless it has individual per-port latency adjustment

[spacialrob]

Hi Rob, yes that's a great point but unfortunately not possible at the moment. But it's an easy feature to implement which will probably make it to the device soon - I've just been very focused on U-SYNC and the coming new batch lately
See here: viewtopic.php?t=340

It would help a lot, thanks! Hope U-SYNC and the new batch are coming without much stress.

[Dave]

Better late than never (with 4.0 around the corner)?

I upgraded - took a couple tries before the Midronome would accept the file for 3.0. But it did.

I've rebooted the Midronome a few times, uninstalled from Windows Device Manager, restarted the computer... I still don't have any Midronome/NomeII Command interface appearing to try and send SysEx to.

I don't have any Midronome interfaces anymore, just Nome II.

I have MIDI IN / OUT 2, MIDI IN / OUT 3, and Nome II for input and also output. No "command" option.

[Simon]

Hi Dave

You can use the "Nome II" interfaces, they should work, that's a minor bug which is solved in FW 3.2 and 4.0.

As written in the manual, on Windows MIDI inputs and outputs are not named properly, they should simply be numbered 1, 2, 3. See the picture below.
Commands is the first output, followed by MIDI Out 1 and MIDI Out 2.

If there are more issues and this is not urgent, then I'll suggest to wait for FW 4.0 which is just around the corner now

PS: but you mentioned you could see the "MIDI Out 1" name on Windows? I'd love to see that

[Dave]

I'll give sending a CC to the "Nome II" a try.

I admit to adding spaces for readability to the names