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
drmick wrote: ↑11 Feb 2025, 09:33
Yes - forcing the bootloader worked for me.
Ok thanks. But I guess without forcing the bootloader you have the same issue as Dave?
If you don't mind, could you please tell me your precise Windows version and the list of MIDI interfaces (their names in particular) you see in your DAW?
Thanks
Simon
mayersj1 wrote: ↑10 Feb 2025, 14:23
So, all three of my Macs have already been upgraded to Sequoia. I'm stuck during the bootloader upgrade showing Err on my Midronome running firmware 3.0.
What are my options here? Given that Sequoia has been out a few months before this FW update, I'm feeling that the information on needing an older version of MacOS is a little late to the game here.
Do you have a solution or am I stuck with a Midronome 1 not being able to go higher than FW 3.0?
Thanks in advance.
Steve
I'm stuck here too, did you find a solution? I'd love to update my Midronome, but my Mac has been on Sequoia for many months.
mayersj1 wrote: ↑10 Feb 2025, 14:23
So, all three of my Macs have already been upgraded to Sequoia. I'm stuck during the bootloader upgrade showing Err on my Midronome running firmware 3.0.
What are my options here? Given that Sequoia has been out a few months before this FW update, I'm feeling that the information on needing an older version of MacOS is a little late to the game here.
Do you have a solution or am I stuck with a Midronome 1 not being able to go higher than FW 3.0?
Thanks in advance.
Steve
I'm stuck here too, did you find a solution? I'd love to update my Midronome, but my Mac has been on Sequoia for many months.
Well the info about the update went out a while ago, very shortly after the Sequoia release (actually as soon as I found out).
I'm sorry but there is really nothing I can do - the only way to upgrade the bootloader is to use it. Is there no one you know that has a Windows or an older mac machine? You just need to borrow it once to run the bootloader upgrade which will take about 30 seconds.
The very last option would be for you to ship your unit to me so I can manually upgrade it, but I think you finding another machine is way easier
I’m sure I can find a machine to update the firmware with. I just wanted to ask if there is any possible workaround before I give up with my machine. Also, I’m impatient and have taken my birthday (today) off of work to play music. Part of today is my home studio maintenance, so I’m updating all hardware and software.
This is unfortunate. As to your timeline, let's take a look at that:
1. Sequoia was released 9/16/2024
2. Your FW 4.0 release notification (according to your support page) was 2/1/2025 (4.5 months or thereabouts AFTER Sequoia released)
3. Where exactly did you announce that users with Sequoia wouldn't be able to update the firmware of their Midronome 1 devices?
Looking back through the thread, this was initially to be released in November (matches the expected date in the email I received as well). Sporadic postings from November through to 1/17/2025 (still not releasee) and then a release in Feburary.
And to answer your question without starting a flame war, no, I don't know anyone with a Windows machine. I have a Linux laptop. Will that work? I use Macs so I don't have to touch Windows anything. I really don't want to have to fork over the ~$100 it would cost me to ship this unit to you to resolve an issue that shouldn't have happened in the first place.
Seeing as Sequoia is out now (and has been out for almost 5 months) and you haven't come up with a bootloader solution other than to tell people to find an older OS speaks volumes about the support these devices will have (in my opinion). Better for me to cut my losses now and look for another solution.
mayersj1 wrote: ↑12 Feb 2025, 21:48
Where exactly did you announce that users with Sequoia wouldn't be able to update the firmware of their Midronome 1 devices?
The info was not about FW 4.0, it was about uploading the bootloader itself and then re-loading the 3.0 firmware. I posted it in October in multiple places, including Facebook page, group, and sending an email to the mailing list. Sorry if you missed it.
mayersj1 wrote: ↑12 Feb 2025, 21:48
you haven't come up with a bootloader solution other than to tell people to find an older OS
As I keep saying, the solution is the new bootloader, which was out in October. But to upgrade from the old bootloader to the new one, you still need to use the old bootloader once. I'm sorry about this, but there is no way around it.
(short tech explanation: the bootloader is the part of the firmware that takes care of updating the rest of the firmware. Actually most bootloaders cannot update themselves but I found a way around it - but you still need to talk to the current bootloader once until it is replaced with the new one)
Dave wrote: ↑10 Feb 2025, 18:18
Everything else about the Midronome is working great - the interfaces show up in the DAW, I can send MIDI CC to start/stop the sequencer, etc. I made sure nothing else was using MIDI and waited several minutes after starting the firmware updater - it still can't detect the Midronome.
The detection of the device is very different if it's in Bootloader mode or not. The bootloader uses my special secret sauce which I am happy to hear works very well all across OSes and versions. When not in bootloader mode, the detection is simply MIDI. I've tested it on Windows 11, but I have not checked the precise version, maybe 24H2 changed the way the MIDI interfaces are (in particular their names). What are the MIDI interfaces called in Ableton?
Dave wrote: ↑10 Feb 2025, 18:18
Also, bootloader mode with 3.1 never showed "rdy" on the device, just "ugr" or something. It still worked when I updated it to 4.0.
Yes that's normal, Nome II shows con (connecting) then rdy (ready), while Nome I shows UPG (upgrade mode) and uses the LED to indicate the connection status (yellow=connecting to green=ready).
Simon
I'm using Studio One Pro as my DAW (can't stand Ableton ). In MIDI OX, they show up
* Midronome
* MIDIOUT2 (Midronome)
* MIDIOUT3 (Midronome)
(again, I'm now successfully on the 4.0 firmware, so am not sure if they changed with that)
My device is normally connected via a white Arturia USB dongle, but I also tried using a direct cable just in case that was an issue, but that didn't solve the issue.
This is unfortunate. As to your timeline, let's take a look at that:
1. Sequoia was released 9/16/2024
2. Your FW 4.0 release notification (according to your support page) was 2/1/2025 (4.5 months or thereabouts AFTER Sequoia released)
3. Where exactly did you announce that users with Sequoia wouldn't be able to update the firmware of their Midronome 1 devices?
Looking back through the thread, this was initially to be released in November (matches the expected date in the email I received as well). Sporadic postings from November through to 1/17/2025 (still not releasee) and then a release in Feburary.
And to answer your question without starting a flame war, no, I don't know anyone with a Windows machine. I have a Linux laptop. Will that work? I use Macs so I don't have to touch Windows anything. I really don't want to have to fork over the ~$100 it would cost me to ship this unit to you to resolve an issue that shouldn't have happened in the first place.
Seeing as Sequoia is out now (and has been out for almost 5 months) and you haven't come up with a bootloader solution other than to tell people to find an older OS speaks volumes about the support these devices will have (in my opinion). Better for me to cut my losses now and look for another solution.
Thanks.
Without getting into the rest of it, could you run a virtual machine in Linux (or on the Mac) that you install a test version/demo version of Windows onto and then run the firmware, and then delete the VM? Hopefully you could even just use demo versions for all of that and not have to pay anything. I don't know if the USB stuff in a VM works the same as I've not used a VM in many years. Just an idea!
Dave wrote: ↑15 Feb 2025, 00:45 In MIDI OX, they show up
* Midronome
* MIDIOUT2 (Midronome)
* MIDIOUT3 (Midronome)
Ok thanks for the info That is the same it has always been and should definitely be detected by the update software... I'll try to find a fully updated Windows 11 machine to test on and see if I can reproduce the issue.
So let's disregard the fact that your announcement that you needed to upgrade the bootloader came out a month after Sequoia was already released and I'd already upgraded to it. I see that there was some sort of the same issue back in the 2022/2023 timeframe as well.
I've got UTM installed on my Mac. Tried virtualizing MacOS 14.6.1. Found out that MacOS doesn't support USB virtualization.
Installed Windows 11 for Arm64 (M1 based Macs). Midronome is seen when connected to USB port and I can enable it's usage in Windows. Putting the device into bootloader mode though, it's never detected by Windows at that point unless I unplug it and let it connect normally. Is this an issue with UTM? Issue with Windows 11? The only clue I have is that when the Nome1 is put into bootloader mode, there is an UNKNOWN PCI device that is not started due to an issue. Not sure if that's the Nome1 or not.
I'm not going to fork out more money for Parallels or beta test a VirtualBox for Arm64 installation if I cannot be guaranteed this is going to work.
Being in the software development business myself, I understand how these things happen. I do believe that there should have been something you could do/can do with the new version of MacOS and the bootloader. If you aren't paying to get early access to the upcoming releases so you can get the warning out BEFORE the shipping version of the OS is made public. (again, I'd been fully updated for a month before you said/sent anything in October of last year).
Any other thoughts/ideas? I don't have anyone else around me using Windows or an older version of MacOS. Small town and all that. I hope you can see what a problem this is. Because of an issue that your development either didn't have the forethought to design around or provide a force upload for, I'm left with a piece of hardware that is now non-upgradable. This was even a Kickstarter/Idigogo (can't remember which) purchase. I was putting my faith into you and your product. That faith is now destroyed...
While my Midronome had been detected by the FW 3.0 update file plugged into an Elektron USB Hub under Win 10 it was not detected by the FW 4.0 update file after up updating that PC to Win 11 and the same USB hub (though I could see it's FW 3.0 I/O in Ableton Live)
Simple solution: I did not use that Elektron USB Hub and plugged in the Midronome directly into my PCs USB: And voila FW 4.0 file immediately detect the Midronome und Update from FW 3.0 to 4.0 went flawlessly.
I spent the last few days fighting with this bug - it's a nasty Windows thing unfortunately, it seems that sometimes the OS prevents the software to do any MIDI communication. It's very random and I could not find any pattern as to when it happens and when not. I've also seen it in other MIDI software. But from my tests it's always solved by simply restarting the software.
So I've made a new version 1.1.0 of the update software which automatically restarts the tool if this happens. And if it does not help it will give you a more detailed error message.
The Nome manual also now has a "troubleshooting" paragraph (inside section 8), giving you info on what to do if you have issues updating
I downloaded the 1.1 firmware tool and now it DOES detect my device - but it also gives an error about not being able to use MIDI. I'm assuming this is the Windows issue you'd mentioned in the post above. I'm also assuming that if it did connect, it would tell me I already have 4.0 installed.
I did use the Device Manager to remove the Midronome and rescan to find it and that didn't change the error.
Attachments
2025-02-27_08-02-51.png (6.57 KiB) Viewed 16679 times
Interesting... And even restarting the tool does not help? Maybe there is another software taking "ownership" of the MIDI so the update tool cannot.
As far as I know you're the only for who it happens every time. In all my tests (and there were a lot of these) it was always very sporadic, happening about 1 time out of 4.
Note that you can always "force" the start in bootloader mode and then the tool will definitely be able to communicate with your device (since the bootloader does not use MIDI) - and yes it will say you have 4.0
@mayersj1: please stay polite. Yes I ignored your post because I had nothing more to say. As I said I'm sorry but there is nothing I can do about it. You can easily sell your Nome I for a good price, probably way more than you paid for it (before the Nome II's, I've seen them sold for 400€).
). In MIDI OX, they show up