Midronome Community

Hi :) No I'm sorry but it cannot, and if it could it would only create problems as syncing with a MIDI Clock sent over USB is generally a bad idea. The Midronome works best when it runs as a master, so if you can rearrange your setup to make it the master, it's definitely better. In case you really ...

Ha ha yes I forgot quite an important thing: all sync modes start right away now, so the 2.4.P. mode is not necessary. But in any case with Firmware 3.0 you'll want to use the new fancy stuff instead of 24P mode... he he very exciting things you'll see

Please note that this is not "un-done", as 2.4.P. mode has been removed in Firmware 3.0. The plan is to implement in the not-so-far future an additional setting to simply stop sending the clock when pressing Stop on the device. Please let me know if this is important to the community :) Ch...

The limit will be increased as part of Firmware 3.0, to 1000 bytes instead of 125 (the actual value is to be confirmed).

Moving this topic to feature requests where it belongs

closing this since no replies since January.

Status: solved in Firmware 3.0 by removing 2.4.P. mode entirely.
(note: the 24P mode now starts without the 1-bar delay)

ETA is this month

This will be solved in Firmware v3.0 and up by adding extra input interfaces, ending with this configuration: 3 MIDI Outputs: (same as current) Commands MIDI Out 1 MIDI Out 2 3 MIDI Inputs: Clock Module Itf 1 Module Itf 2 Clock is the usual input where the clock is sent, as well as Start/Stop messag...

Short description of the issue : USB Midi Setup (devices connected to the Midronome and how): macOS Sonoma on M1 mac, Midronome plugged in using USB Steps to Reproduce : Simply try to use the USB forwarding interfaces MIDI Out 2, it does not forward, instead the USB-MIDI "Midi Out 2" acts...

Hi :) This does look like a very large delay indeed. You said the TR8S is connected via USB, but it is sync'ed to the Midronome, correct? If not -> clearly that's the issue :D If it is -> it could be the MIDI note you are sending from Ableton over USB which gets a delay. Make sure delay compensation...

Hi Mark

No it is not. Add-on modules have been delayed by the release of Firmware 3.0 unfortunately.
They will probably out at the same time as the next batch, next summer

Simon

sorry for the late response, seems I am not getting email notifications from the forum. No worries at all, and if you want to receive notification emails you can turn them on here: https://forum.midronome.com/ucp.php?i=ucp_notifications&mode=notification_options Thanks for the long feedback abo...

Thanks for creating a separate topic :) You did not follow the template though, so I am missing some information (in particular your firmware version). Could you please edit your post and follow this template: Short description of the issue : Setup (devices connected to the Midronome and how): Steps...

Yes this fit perfectly the description of this well-known issue.
Unfortunately it's a hardware issue, caused when you have a ground loop in your setup.

There are many workarounds and solution - see the linked post

Simon

Hi Scott Very sorry to hear - we investigated this issue heavily with Jandt (who created this topic), I also spoke about it with Manu (who designed the OXI One). The conclusion is the original OXIs have a slightly different MIDI input design which is very sensitive to tolerances - if you get a newer...

Ha glad to hear
I have not tested the plugin in Ableton 12 indeed, but I do not see any reason why it would not work

Let us know if there is anything else

Simon

Hi Max :) That's fair, definitely a few months, not years. Difficult and complex features are the ones that take time, for example the one that is coming with Firmware 3.0. Once this is out I will start working on Firmware 4.0, and its difficult feature is the improved tap tempo, which is the only o...

Interesting! My guess is that when you activate sync, the beatbuddy syncs to the incoming clock (from the Midronome) but then generates its own clock for your looper, which gets out of sync from the original Midronome clock… ? Could you try re-arranging the wires to get the Midronome to send the clo...

Hi :) Thanks for the suggestion! I think this would be difficult, both because it might be specific to your setup but also because even if other people have the same setup they would need a different note so it needs to be configurable somewhere. The easiest workaround is to send the note you want o...

I have been having reliability issues with my Korg SQ-1 when syncing it via analogue to the Midronome. Every now and then, it would jump a few steps and get out of sync. I see - great info! All your ideas seem to be very on point :) Would you mind creating a post about it in the “Midronome Bugs Rep...

Bruno wrote: ↑07 Dec 2023, 16:54 Somehow the advises in the manual from denis dosen`t solve my latency problem, also not with external audio effect.

Wait a few more weeks for Firmware 3.0 - that might solve your issues

Simon

but all the jitter is still happening between the daw and midronome? so the midronome stabilizes it? Well no that's the point, the Midronome uses the audio clock as a reference, so the only jitter it gets is the audio clock's jitter (which is usually very low ) +/- 0.5 samples. When you sync stuff ...

Thanks for reporting! I assume with "plugging the Midronome into the MRCC" you mean using USB - if not please let me know. That's going to be a toughie, and I'm afraid to say it probably is a bug on the MRCC (my first guess is that it cannot handle the multiple USB-MIDI interfaces of the M...

so... a clock taking the route of daw>midronome>hardware is more stable than just daw>hardware? Ha ha that does go against natural judgement indeed :D :lol: The key point is the first line. If I call 1, 2 and 3 the communication lines: daw ---> midronome ---> hardware 1---^ 2---^ daw ---> hardware ...

I understood that as having the need for an additional power plug for the module, for example another USB port.
That will be the case for a big module that uses a lot of power which would be too much to get from the module interface.

Well actually the circuit could not be simpler, the module will simply attach to the current device, no other power supply needed (for now all modules will follow this idea actually). The only difficulty is that MIDI Clock (sent on the Midronome's module interface as well, but it would be the same w...

Hey Tim :) Yes it's definitely planned and will come in a few months hopefully. The modules have been slightly delayed by the coming release of FW 3.0, but they will get there eventually ;) Note that, at first, the modules will only be designs (which will be free), but I will guide you to fabricate ...

In the video and also in the manual it says that „Locked“ only lights up for each bar - in my case its always on. I see - the manual says that the Midronome syncs and the LED lights up after one bar, which is the case in 24P mode (it takes one bar to start the sync). In "2.4.P." mode it s...

Oh I see, it was syncing fine, but you were wondering why the Locked LED was on? Ha my bad I misunderstood :D Well if it's syncing fine then all is good - and yes when it's syncing the Locked LED turns on, to let you know precisely that your Midronome is sync'ed (i.e. "locked") to your DAW...