Moog Music Forum

A Couple of things that would be extremely helpful in doing these updates....

1. In PhattyLoader display the Phatty's current version and display the version it is being updated to.
2. include the current .hex file as a seperate file with the PhattyLoader software
3. Devise a "test" for the timing and packet size so we don't have to wait for it to fail just to realize i need to lower the speed and size each time.

These would make doing the updates a lot easier i believe. Otherwise Great Job !!!

Thanks
Don

checksum failure means there are errors in the data coming into the Phatty.
Either there is a problem with the device you are using to send the data,
or there are other MIDI messages coming into the unit. Make sure nothing MIDI or USB is connected other than for the purposes of the update; make sure no other MIDI programs are running on the computer you're using to do the update.
In Phattyloader, be sure you try slower/smaller settings on the Timing menu.

If all else fails and you have a Phatty with built-in USB, try taking it to a different computer and running the PhattyLoader over there. PhattyLoader is smallish and will run off a flash drive or what have you. If you can't get it to work on a mac, try a PC. There will be a way. If you can't get it then you can always contact Moog tech support for further assistance.

loaded V3.1 on my stage 1 using Windows 7 (64-bit) with a MIDISPORT 2x2 and everything went quick and painless. I'm also running the PhattyTuner software on the same system with no problems.

Love the update! A big Cheers to Amos and the rest of the Moog crew who brought this together!!

i have done the update in my LP Stage. I followed the instructions and everything works fine. i used an emu midi-usb interface and a laptop pc. my own presets were not deleted, all they were still there after doing the update.
i have to restart my LP manually, turning it off and then on.
i find the new features very useful! thank you very much for the moog's workers!
cheers!


PD could be possible someday that we were able to route the master volume through the LFO to have a tremolo effect? i think it would be great! and one more thing: why we don't have a "random" pattern to arpeggiate the notes? i love it! it could be also possible?
somebody is agree with me?

thanks again!

wow, amos is a really, really patient guy. i have never seen such a great customer support on any other gear. i think there should be great thanks for this update, wise guys should wait for the next update(if there is any necessary). moog is worth its money.

PhattyLoader with WIndowsXP didn't work (some error while .hex opening), but MacOSX version worked without problem. Update done, thanks once again, Amos!

Just updated my LP Stage v1, and have noticed what I think is a bug in the new update (671).

I'm getting pitch glitching on Osc2 while using the Mod Wheel. It doesn't happen on all notes, or on the same note all the time. For example, I was just using a patch which opens the filter with the mod wheel, and while moving the wheel slowly, taking maybe two seconds to move the full amount, there's no glitch. When I move through the range in maybe half a second, the pitch of Osc2 drops lightly and then rises sharply before droppng back to pitch.

It's noticable on more than just the one patch too, so I'm guessing it's global.

Also, this never occurred before updating. This evening is the first I've heard this very noticeable glitch.

I should add I 've done a full calibration and the bug is still there.

criminy. I've never seen that, but I'll go check it now.
Can you email me a patch of yours that does this?

Also you might try exporting all your presets as sysex, doing a factory restore then test for this issue again.
If you don't experience the problem (which I sincerely hope), dump your patches back in and check again.

Out of interest what OS version were you running prior to the 3.1 update?

-Amos



[edit: #$&%. I totally hear it. It's subtle but it's there. I will look into this ASAP.]

Amos wrote:Can you email me a patch of yours that does this?

Wilco.

Also you might try exporting all your presets as sysex, doing a factory restore then test for this issue again.
If you don't experience the problem (which I sincerely hope), dump your patches back in and check again.

No change. The error is evident both on the factory patches and my own, before and after factory restore, reboot and patch dump. The only difference between my happy LP and my sad LP is the new OS...

Out of interest what OS version were you running prior to the 3.1 update?

2.1 I think.

[edit: #$&%. I totally hear it. It's subtle but it's there. I will look into this ASAP.]

Cheers.

EDIT: It seems to be about a 1/4 tone in depth. It only seems to happen while the Mod wheel is actually in motion - as soon as it comes to rest, the pitch snaps back to normal.

ALSO: It's not just Osc2. I set up a simple patch with only Osc1 audible, and moving the Mod wheel stumbles the pitch of that too. I haven't been able to predict its occurrence on particular notes, particular kinds of patch, or tie it to any particular kind of mod wheel function - seems random, but pretty persistent. Even with mod wheel destination amount set to zero, the error still occurs.

Updated with no problems. Great updates..so grateful to Amos and Moog for continuing their commitment to the evolution of this instrument. Keep it up.

Hi, I would like to downgrade my stage I from 3.1 to 2.0 or 2.1 firmware, in order to bring back arp functionality, where can I donwload hex file for this 2.x fw? I have a sysex for 2.0 that worked but after 3.1 update seems to not receibe firmware updates in syxformat. Thanks in advance.

what arp functionality are you looking for? To the best of my knowledge, it's all still there, except for LFO as a clock source for the arp (which never worked very well to begin with, really). Let me know what you're trying to do with the arp and I will do my best to help.

The only way to downgrade is via a USB Debug Adapter from silicon labs... there's no way to downgrade via MIDI.

Thanks Amos for you quick answer. I have the same problem like other people in this forum: after 3.1 671 fw, when I press value to switch on arp it goes to max or really high bpm for any preset I try. Any way to solve it then? I try preset 86 bouncy seq it shows 188.6 bpm.... ussually was pleasant to play and know seems trying to play vangelis's spiral

Rfx wrote:Thanks Amos for you quick answer. I have the same problem like other people in this forum: after 3.1 671 fw, when I press value to switch on arp it goes to max or really high bpm for any preset I try. Any way to solve it then? I try preset 86 bouncy seq it shows 188.6 bpm.... ussually was pleasant to play and know seems trying to play vangelis's spiral

I get the same thing -- I didn't realize others were experiencing this, too...

Rfx wrote:Thanks Amos for you quick answer. I have the same problem like other people in this forum: after 3.1 671 fw, when I press value to switch on arp it goes to max or really high bpm for any preset I try. Any way to solve it then?

Yes, a very easy way. Turn on the arpeggiator, select LFO RATE and use Modulation knob to set the arp rate to a speed you like. Then save the preset; it will save the new internal arp rate.

Easiest way to save preset when arp is running is to press CURSOR twice, then press Enter (if cursor is in Name field, Enter will save preset instead of toggling Latch on/off). Or, turn off arp, then press Enter to save preset.

The reason for this is that the arpeggiator rate had a format change in the new OS, so the "old" parameter value is not interpreted the same way by the new firmware. Adjusting the rate and saving the preset will fix this.

Sorry for the inconvenience!

-Amos