Midronome VST Plugin: BPM jumps when DAW is stopped on Ableton

[ozark2001]

Maybe here is an idea to improve (as in stablelize) the bpm clock time that Nome ends up with whenever the DAW stops?

This is of importance to continue to run any hardware synced by Nome without having to start the DAW again, like programming a drum machine in the same (+/-1 bpm) tempo of the DAW. Currently one needs to set the bpm of Nome back to match the DAWs bpm manually after each DAW stop, since Nome bpm ends up either higher or lower seemingly randomly within small or huge variation.

It is clear there is reason why Nome has to do this (to decide if stopped or slowed down), but maybe there could be something like a "backup cached value" of the bpm that was actually active within a few constant triggers before the stop instead of just ending with current random deviation. Then for all cases other than when the bpm really is continously changed/ slowed down right before the last pulse + stop, it would presumably be much more accurate to be the same bpm as the DAW

Just posting this suggestion since on PC using the 24ppq is the only way to currently sync with Ableton, this variance in tempo makes it very frustrating to use with Ableton.

So hopefully (while waiting for Windows U-Sync) the current method could be improved

[Simon]

That's a very fair request

But actually this is not by design - it's a minor bug in the old "Midronome" plugin, which I believe is quite difficult to solve. For some strange reason, on some setups/configurations, and with some DAWs, the plugin sends an extra pulse when it stops, which gets the Nome to change its internal tempo.

I've moved this topic to the bugs forum - and might get to it eventually Definitely no ETA though.

For now you can try changing your configuration, like sample rate, buffer size, etc. (or try another DAW if you have one) to see if it disappears

Simon

[MPrinsen]

+1.

Every time I stop Ableton running, the BPM goes down to about 29. This is very inconvenient, as I have some gear that needs clock running in the background, even when playback is stopped.

[HappyClocker]

+1.

Every time I stop Ableton running, the BPM goes down to about 29. This is very inconvenient, as I have some gear that needs clock running in the background, even when playback is stopped.

+1 also from my side.

[Simon]

Thanks guys for the feedback. We can look into this depending on when U-SYNC for Windows is coming out.

Please note that this is a bug in the "Midronome" plugin, which is open-source (based on JUCE). So if someone feels like having a go at it, do not hold back The issue is that the plugin sends an extra random pulse when the DAW stops. As I said this is not on all DAWs, and not on all configurations.