Sim'n Tonic Forums

This would be great and will definitely make me place my Midronome in a more prominent (easier to reach) place in my setup!

I guess I have to do some more testing. I suspect that my gear is set to Auto and when it receives a Stop message, it reverts to its internal clock, so it stops calculating the incoming midi pulses.

Awesome! Hi Maarten, have you had a look at what I wrote above? Cheers Simon Hi Simon, sorry for the late response. Anyway, I get why it works like this now. However, it would be nice if an option would exist that allows Midronome to take over the "lead" and keeps sending midi clock, afte...

Will try!

Ah well, I’m only using the 24P (2.4.P. Previously) mode and it seems that it stops sending clock when it stops receiving a pulse from my DAW. So to be more accurate: my feature request is only about the 24P mode then. (I’m correct that it doesn’t do that already in that mode, right?) Or is there a ...

In some cases, it would be nice to make Midronome keep sending midi clock after a Stop signal. This can prevent other gear to switch to their internal BPM, which can cause artefacts in synced delay effects etc. Also some gear sync better to an external clock if the BPM matches already at the Start m...

Simon wrote: ↑05 Jun 2024, 21:27 Awesome Maarten, thank you, much appreciated. Yes this sounds like a bug introduced in the 3.0 firmware, I'll investigate and get back to you here.

PS: topic moved to bugs category where it belongs

Awesome!

Hi Simon, I did some more testing. First of all, I connected my Midronome directly to my Hapax midi input with a DIN cable. Then I started playback in my DAW at 130 BPM, using the "old" Midronome plugin to send pulses. Midronome starts, Hapax starts as well and everything works fine, runni...

Hi Simon, do you have any updates on the ETA?

If something can be done to make Midronome do that automatically It's not gone completely but has been improved, replacing the value with a simple checkbox (which works with latencies up to 250ms). Oh that looks like it solves the issue 99% of the times in my use case! In that case, I am very inter...

Hi Maarten, Thanks for reporting. A few questions: Is this new with FW 2.90, i.e. this is not the case with FW 2.0? How is your other gear connected to the Midronome, via MIDI? Thanks Simon I think so, but not 100% sure. I compared the 24P mode in 2.90 vs the 2.4.P. mode in 2.0. Maybe the original ...

Personally, I'm fine using the 24P mode. Mainly because I don't like changing the latency compensation within the plugin manually every time I add a plugin in my DAW that increase the maximum latency of the project. If something can be done to make Midronome do that automatically, that would be real...

STATUS : bug was introduced in Firmware 3.0, on the 24P mode. Will be investigated and solved in a future version. ---- Hi Simon, I use the new 24P mode in 2.90 beta using Ableton Live 12 with the Midronome plugin. Whenever I now stop Ableton Live 12, the Midronome does also stop as expected. Howev...

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). Correc...

This is also fixed if you use my prefered method: send the audio signal to Midronome by using the External Audio Effect device instead of the regular track output.

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). Previou...

I have no problems using Midronome in Ableton 12.

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

Any update on the ETA?

Looking forward to this one! :) Especially the improved tap tempo will possibly be a game changer for when you want to play along a live drummer with an arpeggiator or sequencer running. Currently, it is only possible to match the tempo, but if I understand it right, the improved tap tempo would cat...

Being able to add positive clock offset to any of the outputs would be perfect for me.

Simon wrote: ↑25 Oct 2023, 09:15 Thanks guys for the input

I'll see what I can do

Thanks! I think this would please many people.

A separate module sounds great, but I do hope for a software update with this feature built in the current Midronome, accessible from the menu as well. It would be great to line up different devices with different latencies, where you just "set and forget" and don't need the hands-on contr...

So, is this feature (clock offset per output) being planned, or only considered?

You need to use the External Audio Effect device to send the audio to the Midronome without delay.

I`m also struggling with the delay/ latency problem. I also work in Ableton and i`m using a rme fireface UX Interface. I have a fix latency of 28-29 ms but without jitter, the clock is really stable. When i delay the Track where the Plugin is on, nothing happens. The delay on the Track also didn't ...

Hey, I’ve been trying ever since I got my Midronome to make it work properly but no chance. Whatever what I do I ALWAYS get jitter/delay. So I waited for the 2.0 update and the plugin. Tried again, still NOT working. I am using Ableton Live 11, latest version. Macbook Pro i9. Audio interface is a K...

What if you use the E-RM plugin instead of a audio sync track?

I did find a way now (added the Ableton Delay device, but the smallest shift is only 1ms, can't shift by 0.1 ms for example), but it would be nice if the MIdronome was capable of doing this without the need of any extra plugins.

Not sure if this is already planned, but I love to be able to shift the offset (positive clock latency) of both tracks, not just one to compensate for the other.

Is this what is in your mind Simon?

Just FYI - that will definitely require a fair amount of beta-testing, ideally with as many different devices as possible. I had to do some pretty nasty things to be able to start the sync right away, in particular DIN sync / sync24 could be an issue (technically, from the first tick of the DAW it ...