I posted an earlier update in another thread last Friday, but I’ve made some improvements since then… I think what I have now will be the official next version, I just need some more folks to test it before I release it to the general public.
Would you like to help? Please download and try the update and let me know how it works for you. Thanks!
Changes in the new version include:
NEW FEATURES:
triplet clock divisions
separate bank change MSB, LSB messages, each/both of which can be OFF per channel.
tap-tempo multiplier (x1, x2, x3, x4)
can assign same MIDI CC number to multiple MP201 channels
BUG FIXES:
LFO channels now load CV Lag settings correctly on preset load
LFO Off Mode “Initial” now always returns to correct initial value when turning off the LFO.
I tried installing it, the MP201 hung with an error message saying something about FW LOAD ERROR 2 2
(I don’t remember the exact message, but do remember the 2 2 part)
I was able to restore 2.0, but when I tried to install the new software again, the installer hung so badly that I had to restart my machine. After I did that, several of my other USB devices had vanished. This is not good.
Ah, OK. That’s what I was waiting to find out. I have more work to do.
Once a unit has been updated, it’s hard to put back to its pre-updated state, which is necessary to find bugs of this kind.
This tells me I need to work more carefully on my test MP-201, to iron out these update problems.
Thanks for testing so far! I will keep at it…
So far, no problems restoring to v2.00. So, it shouldn’t be a paperweight
My problem here is in trying to restore my test unit to “exactly the state of a non-updated v2.00 unit” so that I can see the same error that folks are reporting here when attempting the 2.1 update. My problem is that the update works fine for me so it’s difficult to trouble-shoot…
OK I got it all figured out. First I was able to revert my unit to production condition, for proper testing…
then determined that the v347 code was too large in size, and that’s why the update did not work.
I removed the code that converts v1.0 presets up to v2 format - this was taking up nearly 1k… now the update works.
I’ll test carefully and post a working update this week.
It’s a shame to lose the v1.0 conversion ability, but you can always use the v2.0 MP201 firmware as a bridge… it will accept v1.0 preset sysex in and will convert it to v2.0 format… you can export the v2.0-format sysEx and import that into v2.1. I’m hoping few to no people would need to do such a thing, anyway…
It’s not official yet until you folks test it and give me your feedback… but I think it will work this time.
Things to remember:
back up your presets first; there’s a new preset format so the presets in the unit will be scrambled by the update. You’ll be able to load your presets back in to the new firmware after the update, and they’ll be automatically converted to the new format.
you must use the USB connection on the MP-201 to send the firmware update. You can use USB or DIN MIDI to send the Factory presets.
The procedure is: back up your presets, send the firmware update, send the factory presets after the unit reboots, do a Factory Restore, do a Footpedal Calibration, reload your own presets. Done.
Seems to work here this time too, with one exception: In order to get the MP201 to start updating, I had to turn the value knob. After that, all went smoothly.
Well there’s only been one error reported when doing the update and I think we figured out that it was user error / windows / not the firmware update’s fault.
I just wanted to check in to let you know that a lot of my time right now is taken up with the upcoming iPad release;
I’m also working on an update to the Little Phatty editors to support the new v3 Phatty firmware.
However, I think I can declare the MP201 update finished; I just need to update the documentation and let our Marketing folks know to make an official announcement. It’s safe to say it will be out before Moogfest; probably sooner.
I’ve been snoozing on this one. Is there a feature that you would like tested aside from triplets specifically or simply that you would like to be assured that it installs cleanly with no blowups or ‘silver screen’.
Thanks again for getting this done Amos. It can’t have been easy to fit it in given all the other projects and the now-discontinued status of the MP201, so it’s doubly impressive that you and Moog Music didn’t let it drop like so many other companies would do.
Are we still on time to ask for new features for the upcoming OS?
I am using the MP201 to trigger a Boss HC-2 and I’d love to be able to send velocity info along with the MIDI notes coming from my sequencer.
From what I read in the manual this can’t be done:
“If MIDINOTE OUT is enabled, the channel will output a NoteOn with Velocity 64 when the Gate is turned On, and
a NoteOff (velocity 0) when the Gate is turned off.”
However, it is stated as well that the velocity from incoming MIDI events is recognized:
“VELO TRIGGER allows you to set a MIDI Velocity (1-127) below which the Gate will not turn on.”
!!!
I have more work to do.
