I did implement the feature but didn’t enable it on the beta.
One thing is for sure, once you start an upgrade, either you have the new firmware or you have nothing at all, as the firmware update wipes the previous firmware before doing its thing. So my guess given your video is you had a weirtd corruption during firmware upload! I will dig into it but know that 5 of our beta-testers have successfuly updated to this beta version, on the 3 platforms with the recommended and tested sysex software … I wouldn’t have claimed it was stable if it wasn’t the case
@Mathieu Of course the cutoff should do that, that makes perfect sense, just me being slow! I’ll have another go and drop you an email if it still refuses to work. Thanks!
This happened 4 times, 1 time starting from v1.99, 3 times starting from corrupted v2.0b3, and each time the sysex transfer was declared successful. It was only by redoing the entire procedure (->1.99->bootloader v2->2.0b3->clean that the update ended up being done correctly at the 5th attempt (and all operations were performed with the same PC, the same configuration).
I think a survey is necessary: who here managed to update his machine the 1st time and without difficulty? Even better: who on this forum has simply managed to perform this update? The only posts following its publication mention various problems. I am clearly not an isolated case, and this while I voluntarily reinstalled zero (as new) to precisely avoid the sometimes hazardous version jumps.
The reason for that is that most people that successfuly updated simply won’t come back here We need to solve your issue though, could we jump to a private conversation to pinpoint your issue ? You can contact us via contact@norand.io
Using the latest replaced firmware from Mathieu I did the following steps:
1.) Sent it mono_V1.99.syx … After this, steps 1-16 and Pattern were flashing. I let them flash for a few minutes, but nothing happened.
2.) Power Cycled
3.) Sent it mono_secondary_bootloader.syx … After this it began 3 pass auto-calibration and rebooted itself. Pass 3 takes the longest.
4.) Hold down Tempo+Function and send it mono_V2.0b2.syx …After this, it runs a new Auto-calibration routine while the step LED’s indicate status. At the end of this, all step LED’s remain lit.
5.) Then “Clean Memory” boot via F#+G#+A#+Follow+Power … this shows Step LED’s gradually 1 through 16 and reboots automatically.
Big thanks for the update, @Mathieu! The new firmware is now up and running over here. The new file did the trick for me, no more freezing during calibration.
Step 3 above where I listed “auto-calibration” the LED’s cycled through the first two times-- the sound on output was almost a SAW wave rather than a Sine wave — and the last pass (Sine wave) was about a minute, then it rebooted.
I mean. The SUSTAIN pot simply has zero effect on the sound. The led is always on and at same brigthness no matter the position.
flashed ‘not as new’ and on mono_V2.0b3
-edit-
Seems like release has no effect on envelope either. If acts like an AD/AR envelope (wich is fine btw)
