Hi @Tajnost ,
Are you sure. It should work, check this video at about 8min 39s…
Basically in live edit and pattern select mode hit Func/copy and source pattern followed by Func/paste and destination pattern.
1 Like
Live mode:
I can confirm that this method does NOT work in firmware 2.1.1r. In other words, copying the running pattern will paste the original (unedited) pattern.
Unfortunately.
I have a mail-exchange going with Simon B regarding several other issues with this firmware, and he is saying an update is coming soon. I have tested a beta he sent me, but no real change for the better, except something with pot mode 2 (see under). In version 2.1.1r this mode jumps like pot mode 1
Some of the Issues from my latest test (new beta):
Pot mode 2 does catch up, but does so with a jump when approaching/crossing the set value: hence, it is not possible to have a smooth transition.
Pot mode 3 (when f.ex.cutoff- knob is touched) always jump directly to a position far anti-clockwise from the physical knob position, hard to pinpoint exactly where, but likely to something like 10-11 o´clock; and not at all reacting relative to knob position.
Swing function is not working at all. The only reaction to the different buttons is that the running sequence looses the timing for a few milliseconds when entering a new seq key nr.
Offsets for velocity/accent etc can not be set negative (anti-clockwise from 12 o´clock. Leds will become increasingly brighter as you approach full ACW, but no reaction to the sound produced)
And a couple of requests I sent him:
When you delete a pattern from a seq step, there is still a faint light on the step, so it is easy to think something is in there. The only way to clear the light is by pasting
an empty (not yet recorded or worked with, unlit by default) slot on to the newly erased one. Could you please make it so the delete function removes the lights?
Projects/load mode: would it be possible to NOT have lights on empty projects, or maybe just very dimmed lights on unused slots, and much brighter on slots actually containing something?
Hope these things will be fixed asap!
4 Likes
One more thing, in this latest beta it is again possible to play mod notes chromatically with midi channel +2. That is; say you set main midi channel to 9, you can play all the different mod notes with ch.10, and the selected (physical selection on Mono´s mini keyboard) mod note chromatic with ch.11
1 Like
Did you make it work? When you prepare to update from firmware v2 upwards (Mono Mk1), you need to power on Mono while holding tempo+func (and not pattern+run as with v1)
1 Like
Update to my previous posts:
Simon B has been working hard on all the issues I mentioned above, and the following has been fixed in the new firmware now posted on the downloads page:
Swing function now works as expected!
All Pot-modes now works as expected!
Negative offsets to vel/aftertouch etc now works as expected!
More information in the download!
Thanks, Simon!!
1 Like
kool! thanks a lot to @bitt1997 for all the info!
here is the list of fixes for the MK1. sounds great!
V2.1.2r
Bug fixes :
-
- We’ve reviewed the real time system, which led us to find many ways to improve it. Mono should be able to handle high load (high USB throughput + lots of automation for exemple) without ever crashing.
-
- We have reworked our threading mechanisms, which will prevent very rare race conditions leading to freezes from happening.
-
- Fixed an issue where slide and accent ratio would lead to high load and potential freeze
-
- Pot modes have been entirely reviewed and fixed, (mod note included)
-
- Swing : now working properly with every clock source
-
- Added back selected Mod Note pitch midi channel (with midi channel + 2), can bedisabled with the mod note channel setting
-
- Negative expressivity assignment now working properly
-
- Fixed an issue where Program Changes (to change the current pattern) would leadto crash if the pattern was over 64
1 Like
In the update procedure manual it says:
- Click “Play” on the top right, Sysex Librarian starts sending the firmware. The LED on Mono will indicate progress.
I turned Mono on while pressing PATTERN + RUN and the leds were blinking. As I started to send the update from Sysex Librarian the blinking stopped. My mono was not showing any progress as it’s supposed to. How will I know if the update was successful or not?
I updated my mk1 to 2.1.2 this morning. Seems to be working so far.
Here’s my steps, and I’m not sure why, but I can only upgrade this way:
1.) I have to first send bootloader (Power while PATTERN+RUN) and let that complete. It reboots automatically.
2.) Then press (Power while TEMPO+FUNC) and send 2.1.2 sysex. The STEPS light up one by one (1-16) then it reboots and does the 3-pass tuning, then reboots on its own.
Seems to be working so far.
I’ve been on v2.xx for over a year now and its been stable, and I’ve used it live countless times without any issues.
Hope this helps someone else.
1 Like
Thanks. After sending the Bootloader Mono was not visible in Sysex Librarian. After reconnecting the USB it appeared and I was able to install the latest firmware. All seems to be working now! Also got an answer from customer service very quickly and that was very helpful 
Unfortunately DON’T WORK, just tested with 2.1.2
which is a bit strange and annoying, always in a fear that I can’t save what I’m editing so have to record all the time into DAW like with 70s synths
1 Like
Just played a bit more with 2.1.2 on mkI - it is total mess, after some time machine freeze on different conditions, during play with mode notes it started to be completely uncontrollable and now even after reset and restart some knobs not working, just light all of the time and make no effect… I can’t select patterns anymore - it stuck on pattern one for some reason… I guess I need to reinstall previous firmware again or…
Guys please do something about it or at least explain what’s going on with your machine and what’s your plan to make the software reliable, otherwise it’s a way too buggy to use it
1 Like
mine won’t even load up the new firmware
@Bornin92.wav Did you try my above procedure?
(First sending bootloader, disconnecting/reconnecting, then sending firmware as noted above?)
Try it and see if you can get it to take.
I’ve been on it for about 3 weeks now without issue.
Upgraded to v2.1.2 with no problems but I’m encountering bugs that make it unusable - the volume knob seems to be controlling the attack knob. Power cycling got rid of that issue once but then the OSC 2 controls stopped working, power cycling again made the volume knob control the attack again. Multiple power cycles haven’t fixed that.
Can I downgrade to 1.99 and is that less buggy?
1 Like
Im new to Mono. Are the firmware 2.X updates also compatible to Mono MK1?
1 Like
There are unique firmwares for each device, found on the “Manual” pages, so 2.x is indeed only for the Mk1.
Norand
Norand
2 Likes
I also had the firmware update freeze at 246 bytes. Followed your steps and managed to install mono_V2.0b3.syx no problems it seems! Will test it out now. Thanks for your help.
I believe so. I just successfully installed mono_V2.0b3.syx after a couple of steps. If the firmware freezes at 246 bytes, follow the steps that were mentioned earlier in this thread.
hello guys, thinking on buy a brand new mk1, just would like to know the status of the current firmware, any serious bug to deal with? I want it for live performance, thanks!
Midi sync stable? os behaviour during live act?