[RELEASED] Firmware 4.0

[Simon]

STATUS: Released - update using the Sim'n Tonic Firmware Update software.
See also this Youtube video that demonstrate the new features: https://youtu.be/Ysv2PiQ9FmU

-----

New Major Features:

• Start/Reset for ANLG output - viewtopic.php?t=210
• Tempo presets - viewtopic.php?t=211
• Support for other time signatures (6/8, 2/2, 4/2, etc.) - viewtopic.php?t=301

New Minor Features:

• Mute follows Play - viewtopic.php?t=144
• Stop the midi clock output - viewtopic.php?t=340
• Ability to slow down the MIDI Clock output - viewtopic.php?t=376
• Turning the locked mode on or off is now shown on the display ("Loc" for on and "L.o.c." for off)
• The AutoPlay A.PL setting has now more options, to select which port you want to start playing automatically (1, 2 or both)
• A pedal/footswitch configured as PLA (start/stop) can now also do resync with a long press, just like the play buttons

Fixed issues:

• Missing restart/reset of connected machines when using drum pad in P.A.d. mode - viewtopic.php?t=442
• Diverse minor bugs solved, very particular UI situations
• Lots of internal improvements for bettter firmware stability and reliability

Interface changes:

• The advanced settings will now always be visible, but will be in a "sub-menu" at the very end of the list
• The settings list has changed a lot, in particular the advanced settings list. Don't worry the settings will be upgraded smoothly so you will get a device with the same configuration before and after FW 4.0. See below the complete new settings list, and look at the specific feature topic (links above) to know more about each option.

Code: Select all

	CL.1 -> 0-59
	CL.2 -> 0-59
	Vo.1 -> 1-9
	Vo.2 -> 1-9
	SIG  -> x/y, with x [1-32] and y [2-16]

	inP -> OFF, PEd, PAd, P.A.d., 24P

	A.PL -> OFF, bot, Mi.1, Mi.2

	AnL  -> con, FOL, din
	An.1 -> OFF, '1, '2, '3, '4, '6, '8, '12, '24, run, StA, rES, 2, 3, ..., 99
	An.2 -> same as An.1 (An.1 & An.2 hidden if AnL = din)

	LEd  -> OFF, On
	bri  -> 001-008

	Adv  -> (advanced settings list)
		PEd  -> Mut, PLA, tAP, PrE
		PE.2 -> OFF, Mut, PLA, PrE
		PE.t -> SuS, LAt
		Mut  -> nor, FOL
		rES  -> OFF, On
		PL.1 -> bot, Mi.1
		PL.2 -> Mut, PLA
		Mid  -> OFF, con, FOL
		Mi.2 -> '1, '2, '3, '4, '6, '8
		PrE  -> presets from 1 to 50

list-of-settings.png

(note: for more explanations on each setting, see the topic for the individual features)

[MPrinsen]

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 catch up to stay in sync as well.

[Simon]

Correct

[Maxcote819]

Hi,

I do know there’s no ETA at the moment, but i’m wondering : what’s the eta ?

No, I get it, there’s other updates before that one, unfortunately for me, I was counting a bit too much on the presets feature and have been waiting for it to really use my midronome. If you say it might take months, I’m willing to wait, but if it’s years, it’s simply a great piece of gear that I’d have to sell until then.

Thanks Simon !

[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 one that could take time. But because of your comment, I'll make sure to release the tempo presets (which is a much simpler feature to implement), either with version 4.0 if the improved tap tempo is done in a few weeks, or as a separate version 3.1

Cheers
Simon

[Lunaman06]

… I'll make sure to release the tempo presets (which is a much simpler feature to implement), either with version 4.0 if the improved tap tempo is done in a few weeks, or as a separate version 3.1

+1 I would appreciate that as well.
viewtopic.php?t=211

[MPrinsen]

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

[Lunaman06]

[*] Full configuration via SysEx messages - viewtopic.php?t=233

• + Admin software to change settings from a computer

[/list]

Not sure how high of a demand this is. Definitely valuable but maybe it is helpful think to break this out into a release 4.5.

[Maxcote819]

Few months later, how is it going Simon ? Challenges along the way ?

Was wondering if there is now either an update with the presets or a 3.1 update as you mentioned would maybe be possible.

Thanks again ! Awesome job you do !

[Simon]

I know, there has been many delays. Major causes are U-SYNC for Windows and the new batch which is not only a batch but a new revision of everything including new branding ("Nome II"...), so lots to do there.

Plan is to get started on Firmware 4.0 as soon as the new batch is ready

[Maxcote819]

That’s great ! You’ve got an ideal eta ? Knowing it might get pushed obviously !

[Simon]

Well an ETA for start of FW 4.0 dev should be middle of November, maybe a bit before.

Then for release I am sorry, I cannot give an ETA until I've started working on the smart tap tempo as it might be a bit of a challenge.
The other features should go quite fast and I'll do them first. If the tap tempo feature start taking too much time, I might release the others first as FW 3.5 or something like that

Simon

[Maxcote819]

Hello Simon !

Hope you’re doing well !

Me again. Did you get to start tackling 4.0 ? I don’t want to rush you or anything, I knew from the start what I was getting myself in by buying something knowing it wasn’t yet implemented, but you think it’d be doable to split the release and get that preset thing out ?

Also, I never asked before, but do you have a broad idea of how it would work ? Also, external controls ? I’d love to be able to pause (or mute) and to hit either next preset or maybe double tapping could go back one preset.

And for the display, you had already something in mind ?

Thanks ! Keep up the good work man !

[Simon]

No worries, ask anytime

Yes the production of the Nome II has been delayed, and since I will start FW 4.0 dev after, then this has been delayed too.

But I hope to start very soon - still no ETA at the moment.

Regarding your other questions, please do not hesitate to share how you would want this to work (but please do it in the feature topic, not here), both in regards to how the display could show the info, how it would react to MIDI commands, and which combination of buttons you would want to use to change presets. Same for the other features - it's always good to get suggestions or ideas on how to set up the user interaction

Simon

[Maxcote819]

Oh I get it ! Take the time you need. I'd really appreciate if you'd be able to release a first version of the firmware with only the presets, but again, I get it and take the time you actually need to do it !

I'll indeed go share how I think it could work as well as to the display itself.

Thanks !

[Simon]

Awesome Max, thank you. I'm pretty confident I'll have FW 4.0 with the presets ready before the end of January

[Maxcote819]

Great ! Can't wait ! Thanks for everything !

[Simon]

Quick update here: everything is now implemented except the Presets. The ANLG options gave a lot of work in particular to make sure the clock was super tight no matter what mode you are in (Standalone, U-SYNC, 24ppq sync, reset mode, Drum pad mode, etc.).

The minor features are also all implemented, simple stuff but very powerful!

There has also been quite a lot of improvements in terms of timing (yes it will be EVEN tighter ), optimizations, and reorganizing/renaming a lot of the settings which I think make the settings list a lot clearer and easier to navigate.
But the settings change might be confusing if you are used to the old naming - so please check the list in the first post above and let me know what you think

Simon

[spacialrob]

Hey, Simon!

Successfully upgraded to firmware 4.0 today—excited to try out the new features!

One minor issue I encountered in the process is that the firmware update file for Windows was being flagged in Chrome's virus scanner for whatever reason, but it seems to work fine using Firefox ¯\_(ツ)_/¯

Thanks for all your hard work—I look forward to the official announcement and new documentation.

~Cheers~

[Simon]

Glad to hear!

The manual is already out and updated - check out the support page.
And this is the video showing the new features which will be released publicly very soon - https://www.youtube.com/watch?v=Ysv2PiQ9FmU

Regarding the virus thing, it does that every time I release a new firmware, despite the executable being signed properly (which is very costly by the way!). I even send the files for review to Microsoft so they can check it but it does not seem to make much of a difference either. I think it's "reputation-based", meaning unless you are a huge company that has released thousands of software which are now marked safe, whenever you release a new software it will always be marked as dangerous/virus by default, until many people say that it's safe.

Just FYI, the signing process for Mac is almost free, and it works - every time.

[Dave]

Past firmware updates to the Midronome worked just fine. But the new one (Windows) won't detect it even though the connections haven't changed since I received it after the Kickstarter.

Guess I'll have to temporarily re-cable things later and hope for the best. The experience so far is a step backward, in that regard.

EDIT: Nope. A new cable directly from the PC didn't make a difference. I can't update the Midronome from firmware 3.0 using the new 4.0 firmware updater.

[Simon]

EDIT: Nope. A new cable directly from the PC didn't make a difference. I can't update the Midronome from firmware 3.0 using the new 4.0 firmware updater.

What message do you get? And what Windows version are you using?
From 3.0 you should get a message that says you need to upgrade the bootloader first (if you have not done it already).
And trust me the new bootloader is a HUGE step forward - the old bootloader had many issues, the biggest one is that it does not work with the newest Mac OS.

[Dave]

EDIT: Nope. A new cable directly from the PC didn't make a difference. I can't update the Midronome from firmware 3.0 using the new 4.0 firmware updater.

What message do you get? And what Windows version are you using?
From 3.0 you should get a message that says you need to upgrade the bootloader first (if you have not done it already).
And trust me the new bootloader is a HUGE step forward - the old bootloader had many issues, the biggest one is that it does not work with the newest Mac OS.

Hi, Simon. I'm using the latest version of Windows 11 - fully updated.

The installer tells me that no device was detected: "No Sim'n Tonic device detected (over USB), please make sure your device is connected."
(side note, I think that should read, "No Sim'n tonic device detected over USB. Please make sure your device is connected.")

There's no message about updating the bootloader.

EDIT

Could be user error, but I didn't see instructions to first put the device into bootloader mode BEFORE running the firmware updater. I'd already updated the bootloader for 3.1, so am assuming I don't need to again.

At any rate, once I first put it into the right mode with the 3button power dance, then the software on the PC was able to detect it.

In the end: SUCCESS!

[Simon]

Could be user error, but I didn't see instructions to first put the device into bootloader mode BEFORE running the firmware updater. I'd already updated the bootloader for 3.1, so am assuming I don't need to again.

Yes that's correct, you should not need to start the bootloader - the new one is smarter and starts automatically (the 3 button thing is now a safety feature in case something goes wrong - I was going to mention it for you actually, great you tried it yourself!).

The question is why the update tool could not detect your device? This detection happens using MIDI, the tool just checks which MIDI interfaces are available. In my tests I found that Windows can be a bit slow to list the MIDI interfaces so sometimes, if you press the button right after starting the software, it will say there is no device connected (I guess because the OS is not "ready" and gives an empty list?), then you press again and it works.

Would you mind trying a few more things:

1. run the tool again (without starting the device in bootloader mode) and see if it detects the device
2. if not, check your list of MIDI devices in the Device Manager, and check the list of MIDI interfaces (and their names) in your DAW

Thank you
Simon


PS:

(side note, I think that should read, "No Sim'n tonic device detected over USB. Please make sure your device is connected.")

Thanks for the feedback - noted

[drmick]

Hi,
I just wanted to flag that I have had the same issue with Win 11 and firmware update.

[Simon]

Hi,
I just wanted to flag that I have had the same issue with Win 11 and firmware update.

Thanks for the info. Could you please check the same steps I wrote for Dave (MIDI devices and MIDI interfaces)?
And did you manage to do it by force-starting the bootloader? See the Troubleshooting section in the Nome manual.

[mayersj1]

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

[Dave]

Could be user error, but I didn't see instructions to first put the device into bootloader mode BEFORE running the firmware updater. I'd already updated the bootloader for 3.1, so am assuming I don't need to again.

Yes that's correct, you should not need to start the bootloader - the new one is smarter and starts automatically (the 3 button thing is now a safety feature in case something goes wrong - I was going to mention it for you actually, great you tried it yourself!).

The question is why the update tool could not detect your device? This detection happens using MIDI, the tool just checks which MIDI interfaces are available. In my tests I found that Windows can be a bit slow to list the MIDI interfaces so sometimes, if you press the button right after starting the software, it will say there is no device connected (I guess because the OS is not "ready" and gives an empty list?), then you press again and it works.

Would you mind trying a few more things:

1. run the tool again (without starting the device in bootloader mode) and see if it detects the device
2. if not, check your list of MIDI devices in the Device Manager, and check the list of MIDI interfaces (and their names) in your DAW

Thank you
Simon


PS:

(side note, I think that should read, "No Sim'n tonic device detected over USB. Please make sure your device is connected.")

Thanks for the feedback - noted

Hey, Simon. Without starting in bootloader mode, the firmware updater won't detect the device - not with 3.1 and not with 4.0. 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.

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.

Win11 24H2 (which has been a tough OS update to get working well in general for audio, so not sure if it has anything to do with it)

[Simon]

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?

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

[drmick]

Hi,
I just wanted to flag that I have had the same issue with Win 11 and firmware update.

Thanks for the info. Could you please check the same steps I wrote for Dave (MIDI devices and MIDI interfaces)?
And did you manage to do it by force-starting the bootloader? See the Troubleshooting section in the Nome manual.

Yes - forcing the bootloader worked for me.