Moog Music Forum

Any news on 'official' release of this update, Amos?

Is this tested, working and finalised now ?

Hi all!

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.

Cheers,

Amos

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'.

Let me know and I'll test this weekend.

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 wonder if it is technically possible to send this trigger signal with different voltage outputs, depending on the velocity info. There are some users already who can make use of this feature:
http://www.moogmusic.com/forum/viewtopi ... 19&start=0
http://www.moogmusic.com/forum/viewtopi ... 73&start=0

It would be really nice to see this feature added, I hope it is easy to code too!

Amos wrote:Hi all!

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.

Cheers,

Amos

I just purchased an MP-201, and I DL'd the last test version of the software that Amos posted in this thread. Is that last posted version of the firmware upgrade the final production version?

Any news on Moog 'officially' putting out the firmware update? Amos - have you tweaked anything since the one posted above, or shall I just download that one?

I just loaded the last update that Amos posted, and it looks like it's working fine. As for any docs that go with it, I can't say. So far, the updates appear to be self explanatory in context with their use (for instance, the use of the tap-tempo multiplier appears in the channel setup edit menu).

Done the update, Worked fine.

It wouldn't reload my old presets though - just kept acting as though it was an empty file. Thankfully I know them all pretty well and it only took about 40 minutes to set everything up again!

All good.

Hey, here's the final version. Somewhere or other I promised I'd have this out in time for Moogfest, and I only just made it.

There should be an official announcement / files added to the Moog website some time soon, but given the craziness associated with Moogfest happening right now, I thought I'd post a link here just to be true to my word.

Here you are:

MP-201 v2.1 firmware update (Mac)

MP-201 v2.1 firmware update (Windows)

Cheers,

Amos

Amos, is this final version the same as V2.1, build 348?

Update:
I downloaded it, and see that it is build 349. I'm going to update my pedal with this build anyway, just in case anything changed from build 348.

Thanks, Amos!

Now, is someone working on a software editor for this pedal?

Thanks Amos! I'll check it out when I get home from Moog Fest! Having a blast in Asheville!

mayidunk wrote:Amos, is this final version the same as V2.1, build 348?

Update:
I downloaded it, and see that it is build 349. I'm going to update my pedal with this build anyway, just in case anything changed from build 348.

Thanks, Amos!

Now, is someone working on a software editor for this pedal?

There's one more small bug fix; it was possible to get an invalid CV output in pitch-to-CV mode if the played note was too far below the root note.

We've got a couple software editors for other products to work on first, but in theory I think that will give us an editor framework that would allow for an MP-201 editor as well.

Amos wrote:

mayidunk wrote:Amos, is this final version the same as V2.1, build 348?

Update:
I downloaded it, and see that it is build 349. I'm going to update my pedal with this build anyway, just in case anything changed from build 348.

Thanks, Amos!

Now, is someone working on a software editor for this pedal?

There's one more small bug fix; it was possible to get an invalid CV output in pitch-to-CV mode if the played note was too far below the root note.

We've got a couple software editors for other products to work on first, but in theory I think that will give us an editor framework that would allow for an MP-201 editor as well.

Very cool, Amos! Of course, we're now without power for at least a week, due to the freak snow storm! Oh well, it may be dark, but at least it's really, really cold!

Thanks for all of your hard work, and dedication! It's very much appreciated.

I ve tried to update with 349 but there is something strange..many characters in the display can't be read. I ve tried 3 times reverting firmware but nothing.
Someone had this issue?