Features that have a good chance of being implemented in the future, and Firmware updates.
Topics ar marked as: [A]=Approved, [WIP]=Work in Progress, [F]=Finished
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.
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.
MPrinsen wrote: ↑26 Apr 2024, 13:40
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
MPrinsen wrote: ↑26 Apr 2024, 13:40
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
MPrinsen wrote: ↑26 Apr 2024, 13:40
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
MPrinsen wrote: ↑26 Apr 2024, 13:40
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
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!
MPrinsen wrote: ↑26 Apr 2024, 13:40
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.
Dave wrote: ↑04 May 2024, 03:34
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
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?
muZikman wrote: ↑06 May 2024, 19:01
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
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.
HappyClocker wrote: ↑07 Jun 2024, 17:18
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
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!
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
pauljove wrote: ↑20 Jun 2024, 17:53
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
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
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.
! Then I will wait for FW 3.1.
But Ricky said he won't find it useful unless it has individual per-port latency adjustment