How do I get the 2.0 beta. I’ve signed up for that but haven’t received the download for it
Hi, looking for access to the V2 beta so I can get started on the editor - don’t have the link so far. thx
I was just wondering if there’s any update/timeframe on the first beta bugfix patch?
I’m stuck between two worlds right now - I don’t really want to learn the previous workflow/shortcuts, but the new firmware has no way of saving patches…
Just wondering if I should put it away in a box for a few weeks and come back later, or if I can keep it in the current setup if a patch is incoming soon?
Hey everyone,
I’m working on a patch right now, and implementing the remaining unimplemented old features as well. Should be ready by next week.
@SquidgyB you should definitely roll back to 1.99 and start having fun with the synth in the meantime!
If you subscribed to beta and didn’t get the link send us an email 
Cheers
5 Likes
Appreciate the update for us impatients
Hi,
I would like to come back to 1.99 but can’t find the sysex. Would someone be kind enough to upload it here ?
Thanks !
I got it ! Thanks to JB from Norand 
Hello everyone,
A second version of the beta is available 
It is still not final. let’s get a bit technical:
I am rewriting the sequencer event parser to be fully asynchronous because of the new dynamic projects thingy. Since it is now possible to have a pattern with thousands of dynamic events, they need to be deserialized on load, which take some time and thus needs to be asynchronous (nobody wants the first step of a pattern being delayed by a few dozen milliseconds !).
This proves to be quite challenging for the Undo/Redo feature because I can’t just read and historize the previous events, it also needs to be asynchronous. Basically the sequencer needs to call back the event historizer once it parses the events.
So I need to rework some part of the architecture and beta test it before we go live. And also implement the few unimplemented features of course, sorry about that …
Anyway, thanks a lot for your bug feedback, please keep it coming!
Here the download link :
https://storage.googleapis.com/norand_public_files/mono_2.0b2.zip
Happy beta testing!
3 Likes
Thank you for all of the incredible work that you’ve put into this Mono project Mathieu. Your time, effort, and creativity is amazing and I as well as many others I’m sure, truly truly appreciate and value this work. Ty!
Joey
Hi there,
I just experienced a fatal crash of Mono after switching to beta 2. First of all, a small recap:
-
The unit was updated to beta 1 the day this version was actually available. No problems encountered during the successive steps (1.99 ->dump->bootloader v2->beta 1). The device was since perfectly functional (if we exclude the youthful defects of v2.0)
-
Upgraded to beta 2 tonight. Again, no problem encountered when transferring the file using the SysEx transfer utility (under Windows 10).
-
After about 45mn of play, big bug of the unit which does not answer any more to the commands. Clean shutdown by the power button, wait for about ten seconds, then restart… or almost:
-
From now on, the unit doesn’t turn on anymore. There is a random light flash of some keys at power up (and only if the unit has been unplugged before), but it turns off immediately. However, the unit behaves normally when booting on the bootloader v2 (keeping the Tempo & Func keys). The leds light up normally (in bootloader configuration), the mono is visible in the midi devices, and it can be reprogrammed. However, even if the upload of the firmware beta 2 is 100% successful, the mono does not restart a configuration of use as it did during the first upgrade. Instead, it starts the calibration and memory reset procedure (already experienced when upgrading from v1.99->2.0), then blocks once the progress indicated by the SEQ steps reaches 16. I left it at least 30 to 45mn blocked on step 16 (after a regular progression which seems to be going normally), without any result.
-
So, I went back to the beta 1 version, and there everything works normally again (not even a calibration procedure at the end of the SysEx upload). Stranger still: my presets are still there (which is rather good news).
-
Being stubborn (and curious), I try again to upgrade from the newly reinstalled beta 1 to beta 2: again the calibration / memory initialization procedure starts after a smooth upload. Again, it takes a while, then fails at SEQ step 16 (after 2 full turns of the progress bar).
So now, I can’t go back to beta 2, otherwise I’ll turn the mono into a brick. Could it be a hardware problem related to the internal memory? The weight of beta 2 is a bit heavier than beta 1, which might explain why beta 1 still runs on my unit, while beta 2 invariably crashes it. In any case, it’s very strange.
Thanks a lot for your report !
It is totally my fault 
, there is a small difference in the projects metadata on the new beta version, which causes it to not “understand” some previous projects. It will freeze at boot because it thinks the project is corrupted. This week I will :
- implement some UI alert that tells the user a project is corrupted
- Implement project dumping on 2.0 to be able to save and restore projects from previous beta build
- The ability to dump “corrupted” projects for further inspection, and to be able to restore it even if the metadata are corrupted
In the meantime you can either stay on beta1 or re-init the unit at boot on beta2 (you’ll loose your presets and pattern unfortunately). To do so, boot the unit with [FOLLOW] + [F#] + [G#] + [A#].
Cheers
2 Likes
Hi Mathieu,
Thank you very much for this detailed answer, and what’s more posted on a Sunday! The only thing that really worried me was the hypothesis of a hardware failure of the unit. For the rest, it is the very principle of the beta, and the inerrant risks to the exercise. I am aware of the difficulty and the work that can represent the complete rewriting of a firmware in a fixed hardware framework, and I am grateful to you to increase in this way the already impressive potentialities of this instrument. Good luck in this delicate task, which is added to the daily tasks of a small structure like yours. You have my full support
1 Like
any news about the new os?
2 Likes
Hello Yoko!
Well I had a few setbacks these two past weeks, but I believe I’ll be able to push a “final” beta version, with all the features and a more stable experience by the end of the week!
Cheers
3 Likes
was it released / did i miss that?
I have not seen so on any other forum.
1 Like
on the lookout myself.
Nothing public yet that i have come across.
Hello there,
We are currently finishing Undo/Redo test. A beta version updated will be ready next week !
Thanks for your patience !
Cheers
2 Likes