Page 1 of 1

Extremely high bpm sometimes after starting Windows computer but before starting DAW

Posted: 26 Jan 2026, 17:40
by Dave
(please follow this template when submitting a new bug report, feel free to remove sections if they are not relevant)


Short description of the issue: Extremely high bpm sometimes after starting Windows computer but before starting DAW

Setup (devices connected and how): Midronome via USB to computer

Steps to Reproduce: Have the DAW not started. Maybe turn off and on the computer? My Midronome is normally out of sight so I can't always see the readout.

Expected Behavior: Stays set to last bpm (it's set to read the input from the DAW)

Actual Behavior: It shows 3xx bpm until I hit play in the DAW.

Nome generation (I or II) and Firmware version: Midronome with latest firmware

More info:

Re: Extremely high bpm sometimes after starting Windows computer but before starting DAW

Posted: 27 Jan 2026, 16:13
by simntonic
Hi Dave,

Thanks for your report!
From what you’re describing, it appears that Windows or another application may be sending unintended MIDI data to the Midronome during startup, which can result in an unexpected tempo change.
I’ll look into it.

/Frey

Re: Extremely high bpm sometimes after starting Windows computer but before starting DAW

Posted: 01 Feb 2026, 20:42
by Dave
simntonic wrote: 27 Jan 2026, 16:13 Hi Dave,

Thanks for your report!
From what you’re describing, it appears that Windows or another application may be sending unintended MIDI data to the Midronome during startup, which can result in an unexpected tempo change.
I’ll look into it.

/Frey
Thanks!
I'm hoping the new MIDI stack coming to Windows over the next month or so will help/solve it/not make it worse :D

Re: Extremely high bpm sometimes after starting Windows computer but before starting DAW

Posted: 03 Feb 2026, 11:20
by simntonic
Hi again, Dave

I have been unable to recreate your bug, but my guess is that Windows sends some audio signal to the stereo input on the Midronome which then gets interpreted as a tempo change. The stereo input is sensitive to input signals so it would make sense if that were the case.
Can you confirm whether or not the bug disappears when you boot Windows without connection to the stereo input?

Best regards,
/Frey