The way morphing works still makes no sense to me, and to prove it, I performed the following experiment: I take an edited pattern, copy/paste it into an empty location, and then modify only one parameter (the env amount in this case) on this duplicate pattern compared to the original version. In theory, therefore, the only parameter that should be modified in real time during morphing is the env amount. Except that’s not what’s happening at all.
First of all, there seems to be like a hollow between 6h and 9h on the cut off / morphing knob, with an almost complete disappearance of the initial sequence, and no trace of the destination, with a very drastic, and incomprehensible, modification of the source’s sound. Then, from 9h. to noon, the initial sequence and sound seem to gradually returning. Finally, from noon to 6h, this is where morphing seems to operate normally :
I thought I had a problemfree update to 2.0b4 , but after a couple of days the Mono was didn’t turn on as normal. All lights were black, but I could hear that it was connected when I turned it on (hearded the USB sound on the computer). Tried a couple of times to update again, but it failed. So I stick to 1.99 for now because that firmware I can update to and Mono will turn on as normal. I believe it could be the new bootloader that makes this problem.
i am going to try this version. last version did not like my mono. i really love this thing so im hoping it works. the last 2.0 version glitched out my mono something fierce. been fine since i put 1.99 back on.
Still present on beta 5, but it’s an old one: the custom volume of the patch, defined by holding the function key and then operating the volume knob, is not saved unlike all the parameters of the patch. In fact, when recalling a recorded patch, its sound level is always set to the maximum, which is problematic considering the very high output level of the Mono (even with the general volume set to half, the output becomes saturated if the individual volume of the oscillators has been voluntarily pushed to generate a distortion effect).
More problematic: since beta 5, the Mono turns on a little when it feels like it (and it doesn’t seem very motivated on weekends). Otherwise, it works normally when it agrees to turn on.
In Duophonic mode, the allocation of notes to the 2 oscillators is done at random, which makes it virtually impossible to sequence. You never know if the note entered will be reproduced by OSC 1 or OSC 2. Perhaps it would be wise to assign the lowest note always to the same OSC (typically n°1), and the highest note to the second OSC. Thus, the melodic construction would be possible.
Do you know if it’s on (just no lights) or is it completely off when it doesn’t start normally?
Do you hear any sound when it doesn’t start normal (as in ticking sound)?
Do you hear USB connection on your computer when you turn on Mono if it turns on “black”?
I’ve had a lot of startups with Mono turning on with no lights (but ticking sound) after I updated to 2.0. I decided to go back to 1.99 for now. Works fine after a week.
Hi all! I hope this doesn’t come across as a charged question, but what is the current recommendation for v2.0? Reading through this thread, it appears to have a fair number of bugs, is it advisable to wait(?), or is it stable enough to safely install? Thanks in advance for the help!
@jvanaria : The beta version is perfectly usable as is. Globally, and if we exclude the problems that some people encountered during the update process in the first time (I didn’t encounter any problem from beta 3 on), we can consider that the number of bugs is relatively limited considering the number of new functions implemented. The morphing function alone is quite a gift from NORAND, and it is now fully functional with the introduction of beta 5 (still some stalls during fast and repeated movements, but I think it’s more a hardware limitation - not originally designed for this function - than a bug). That being said, and considering that the 2.0 release is just around the corner, I’m not sure it’s a good idea to commit to the beta evaluation at this stage if it’s a fully stable machine you want.
@Mathieu : the bug that makes editing totally inoperative after a pattern copy/paste persists on beta 5 (see my post dated 10 days ago). Thank you for taking into account my remarks on morphing.
ok, here are some of the quirks i’ve found using the latest beta (2.0b5)
• i feel the SEQ buttons in general are a bit more unresponsive, i find myself having to double press a trigger to delete it or insert a note. not sure if anyone else has felt that?
• can confirm @DG3IL5’s report on the copy/paste bug. cant make any edits after performing this functon
• not saving patch volume
• i find that in pattern mode, i was able to see which patterns had a patch with a sequence, only a patch, or empty. (patch with a sequence, fully lit) (patch with no sequence, dimly lit) (INIT, fully off) it seems this is no longer the case.
• not sure if this is a bug or what, but pattern morphing behaves a bit unexpectedly, i have to hold func, then turn the cutoff knob from left to right like indicated. in the video, you can apparently go from right to left while still holding FUNC to return to the original pattern; it doesn’t work like this for me. i have to let go off FUNC, then return the cutoff knob all the way to the left, and repeat the process for it to morph back. was there a change to how it works?
• have to record a vid, but in a specific pattern when slide is engaged the output just kinda fades out basically ? not sure why
• sometimes transport doesn’t start on midi sync, putting it back to internal clock and back to the midi clock source seems to fix it
other than that, 2.0 is amazing! duophonic mode brings so much more into the the table, also the new scale quantize feature is fantastic, so much fun sending midi out to other gear. @Mathieu
As usual, thank you very much for the bug reports, with b6 I think we’re getting in a place where I feel comfortable for the official release. Looking back, we’re in a much better state than when Mono was first released with V1!
Let’s have a week or two of beta testing first, here’s the link : Download
Check the Norand with MIDI clock from any other machine. My 2.0b6 slaves fine for hours and survives rapid stop/start.
With regards to TR-8S sync, I found that I couldn’t use it as a Master clock. It would indeed send poor timing info OUT via MIDI. However when set to SLAVE mode, it works and passes MIDI clock just fine.
I ended up buying a E-RM Midiclock+ to use as a master and it is flawless.
