synthguy wrote: ↑Thu Mar 23, 2023 1:51 pm
I thought that Moog released a huge external Midi control document for the ONE several years ago (probably still available in “downloads” somewhere).
IIRC, it allowed for CC assignment/control of most of the front panel knobs.
If that’s not working, that’s a bummer; I’ll admit I’ve haven’t had the time or the need to check that out yet. Sounds like it could be fun, though.
They did, and that works
sometimes, but sometimes not. But that's not the midi issue I'm referring to...
The issue is that when controlling the M1 from an external midi source (e.g. a DAW, my Cirklon, or another keyboard controller) sending 3 (or more) note chords intermittently (but very often) causes the M1 to hang voices. Once that happens, if you play the same note again, instead of shutting off the hanging note, it freezes
another voice on that same note. Once it hangs, it can't process an external all off command over midi. The only way to silence the frozen voices is to hit the octave up/down buttons on the keyboard (the M1's midi reset command), or shut it off altogether. There are additional problems sending chords and midi clock to control the arpeggiator, which all trace back to the voice allocation system. Bottom line, the thing is all but useless under external midi control if you want to have it play chords...
kind of an important feature for a modern polysynth...
I have been communicating with Moog's service dept about voice assignment problems since November of 2019 and about this specific issue since early 2021. They initially told me it would all get fixed in the next firmware update, but several have been released since then and it's still a problem. To their credit, they had me send the unit in last year, well out of warranty, on their dime. They replaced the keybed (which I had no issues with) and said they couldn't replicate the issue thereafter. But it still hangs notes as soon as I try to play it from another midi source, be it my DAW (running Cubase or Ableton), my Cirklon, or any of my master keyboard controllers. (Before you ask, there were no midi loops, or other wiring mistakes that cause the problem.)
I was pretty annoyed by all of this (it's been 4 years!) so I then spent a full afternoon
extensively documenting the continuing problems and shooting video clips of the setup, testing methodology, and continuous note hangs which I sent back to my service tech. Many weeks later, I was contacted by a more senior Moog company employee. In that exchange (in January 23), they
finally confirmed they were aware of the issue, but couldn't say if or when it would be fixed because
they hadn't even started deciding what the next firmware update would address. The "guess" I was given was
8 months to 2 years... My most recent email asking if they had any updates has not - as yet - been responded to.
I've been a huge Moog fan since the 70s. I own a vintage modular and a Model D reissue. I've owned plenty of other Moog instruments over the years. But my faith in the company has been seriously shaken by this experience. It's astounding to me that Moog's "flagship" poly can't reliably receive midi chords from an external controller without locking up. I'm currently of the opinion that they can't actually fix the problem, but won't admit it as it could be financially disastrous to them. I'm not a "hater" and I'd love to be proven wrong, because I really love so many things about the One. But for me, right now, its just a very large and expensive paperweight.
Moog IIP, One 16V and MiniMoog, DotCom/FSFX/Moon/STG 110, Cubase 12Pro, Ableton Live 10/64, RME UFX+, 2xMR816, MioXL, Expressionist, Cirklon, Analog Rytm Mk II, Axon AX50, Customized Variax JTV69s (the Hexstainocaster), Strat, Godin ACS Slim, Helix.