like the Nord Lead 3! I feel like that’s one of the problems with them though, those die over time.
no idea if the knobs have a catch up mode in the new firmware. but probably. most synths with presets and non-endless encoders do. I prefer jump mode though, so I haven’t looked.
I have seen some vids where it’s clearly jump mode.
Not sure catch up mode is a thing on this synth. Hopefully.
Got to check the manual again.
I like Jump mode in the studio, I don’t mind sudden jump and prefer the quicker path.
But when playing in a live setup, jump kills it.
oh for sure jump mode is awful live. I’m not concerned with that though.
I’m not around mine for the next week or I’d check the settings for a catch up mode.
Looks like there is a new firmware (1.2) for all you Muse owners:
NEW FEATURES
CHORD
• Key maps added, allowing you to save up to 8 different chord mappings for KEY mode.
• KEY MAP item in MORE menu – selects between key maps 1 through 8.
• CLEAR CURRENT KEY MAP item in MORE menu – clears out the current key map (selected by the KEY MAP item above) when selected.
• MIDI PANIC soft button in the MIDI menu sends Note Off messages to all voices and SEQ and ARP,
sends All Notes Off message to KEYBOARD MIDI OUT CHANNEL via USB/DIN and All Controllers Off message to KEYBOARD MIDI OUT CHANNEL and LHC MIDI OUT CHANNEL via USB/DIN.
IMPROVEMENTS
• CLOCK More Menu - Change ARP and SEQ START/STOP language to avoid double-negatives.
BUG FIXES
• Pressing ENTER or SELECT on empty menu item will no longer cause crash.
Jesus, you read stuff like this and it sounds like the OS is held together with duct tape and fishing line. I enjoyed my time at the shop demoing the Muse, but I would hold off on making any decisions until it’s a bit more stable
I don’t mind so much when it’s firmware. My on-release Take5 had a hardware problem where it would fry the mainboard if the USB connection was the slightest bit not what it expected - the replacement board had a resistor that wasn’t on the original, so it truly was a hardware design error.
possibly. but talented developers miss obvious stuff all the time. I’m sure I could nitpick the Digitakt II firmware updates and draw the same conclusion.
maybe their test process just needs improvement. or their beta testers were all like “why would I select an empty field?” and it fell through the cracks.
personally I think it’s a great sign that they’ve released two updates since launch (one month ago). and features have been added, not just bug fixes.
At least Sequential repaired these for free and revised the PCB design. The Matriarch is full of hardware flaws, some of which have allegedly been repeated in the Muse. See here:
Free in warranty, usual $25 fee and board swap if not. I’d rather have a firmware update than a main board revision.
My guess is they pushed it out a little early, which is why several more menus are empty, and there are some bugs. It already feels in a better state than my Matriarch.
One of the things people complain loudest about there is something I don’t think Moog considers a flaw, the band limiting of the filter when fully open. It sounds right to me, and only something I’d notice if staring at a meter.
1.3 took something like four years for the Matriarch, the Muse pace seems much faster - so far.
Very true.
Actually happens to me once in a while with all analog. I test a build super carefully before sending it out, then someone does something that I totally didn’t think about.
I always make a revision and then do the board swap for them in these cases, but then I feel totally silly for not thinking of it in the first place.
People use things and develop things completely differently from others.
I would say that I have never experienced 95% of bugs that people mention with a given synth. Take Elektron and the bug report threads on here. I’ve almost never run into ANY of the tens to hundreds of bugs, and I know it’s entirely because I use things differently.
I think with complex digitally controlled poly synths it’s impressive that they come out working as well as they do on release. As long as things are fixed I don’t see a problem really.
Well, given how bad Moog are with Matriarch firmware, I would not expect miracles…
They changed a lot in-between though. Who knows, maybe scaling for better support.
Seems like different people.
And, really, the Muse I received with 1.1 firmware was in better shape than the Matriarch with 1.2.3 firmware (which was released ~3 years in to the Matriarch’s product life), which still is effectively unusable for paraphonic playing with 1.3.
We’ll see in 2-3 years but in its current state the Muse already sounds great and works fine for my purposes.
Apologies, I can never resist rambling against Moog due to my personal experience. Not very constructive.
I get it, they can be a pretty frustrating company.
At the same time, we’ve entered the era of the not-quite-finished product. That sucks, but it is largely inevitable. So long as it gets the final coats of polish in a timely manner I think that’s ok. A fully finished firmware at release would be better, but I don’t think that’s really going to happen much anymore for something at this level of complexity. If you look at other recently released things in that price bracket the only synths that feel “done” are the ones with a much reduced feature set.
I’d love to be wrong, but this is the era of the post-sale firmware update.
even the TR-909 had firmware issues on release. Roland fixed some. but it took another 40 years and a third party to finally get it right (mostly MIDI timing issues). so even though we’re in “the era of the post-sale firmware update” I think we should be happy that it no longer requires an IC swap to update. hell, we don’t even have to wait for updates via MIDI anymore; everything has a USB option. and of course, we should appreciate the companies that strive to make the firmware the best it can be before moving on. here’s to hoping Moog does so with the Muse!
BUT, I also agree with you: even the 1.1 firmware is perfectly usable for me.
I would say there are a couple of exceptions. I’ve owned/own both. The 3rd Wave was pretty spot-on at release, and now it can do about 2-3 times more than it could on release while working pretty much flawlessly. Absolutely incredible what those two guys did and are still doing!
The other one is my Gemini. I know that there ARE a few bugs. People have mentioned them in the UDO forums. However, from my playing/programming, I haven’t run into a single issue yet. Not that I doubt that there are a handful of things for George to fix, but from my own expeience its a very complex synth that came out nearly perfect. Now if he would just add non-hacky linear FM between the audio oscillators, I would be over the moon. 
Should be entirely possible given the architecture.
Anyway, hopefully Moog continues to sort things out, then go back and hit the Matriarch with a nice update. Sometimes they have to put that stuff on hold while developing new things, even though that seems a bit backwards to users. Otherwise they wouldn’t get the new item out in time to be competitive with their peers, and then bad things happen to the company. Just the way things move these days.
The Waldorf XT is still my first or second favorite synth of all time and it DOES have some pretty glaring bugs that never got fixed. They still never impacted me really with how I used them, but I know they hit other people quite a bit harder. Still a very worthwhile synth even now, so things have a habit of becoming classics even with a few flaws. That said, hopefully everything gets wrapped up in a tidy bow as opposed to becoming a flawed classic. 
I dont think Moog and Inmusic are going to hang around. They will get as much new gear out while they are in the news. I can even see a new Moog One.
This doesn’t square with how Inmusic has supported the recent MPCs. Like them or not, they have supported that platform very well.