Updating my phatty from 1.03sb to 2.0 and up

The Moog Forum Little Phatty & Slim Phatty Forum
1

Problems!

Same as everyone else, I’ve managed to crash my little phatty! But after reading this forum lots I can tell that with some fiddling I can fix it. I’ve been using a Behringer BCR2000 running latest drivers as the midi interface, and after swapping everything else in the signal chain, I think it’s the problem.

I emailed Moog. Just thought I’d post correspondence up here in case it might help someone in the future and save Amos some trouble. This forum has been so helpful in troubleshooting the problem, it’s the least I can do.

Here’s the email, I’ll post up the responce when it comes through. Today I’ll try a different midi interface.

Hi Amos,

I’ll keep this short because you no doubt get a million of these.
Updating my LP SE I to the current OS and I’ve managed to disable my
LP. The LP hangs in the first phase of it, and give me the ‘Power
Cycle’ command every time after a few seconds of sending the Sysex
file to it. Now when I boot it up it just reads SEND FIRMWARE SX and
it doesn’t make any sound.

I’m using a Behringer BCR2000 as the midi interface. It’s running it’s
latest drivers. I’ve tried using multiple different midi and usb
cables, so it’s not that. I’m using OSX on a mac, so I’ve tried using
the Moog LP Librarian software (demo version), and running SysEx
Librarian. I’ve tried different speeds. I’ve tried both 2.0 and 2.1. I
can get it to communicate with the LP, because the LP enters it’s
first phase of updating, but then the error message.

So I’m guessing the Behringer BCR 2000 just isn’t compatible? I’ll
borrow a friend’s interface and try again.

I just wanted to ask, is it possible that my LP is so out of date that
it needs an older OS loaded into it first? It’s currently got 1.03sb
running on it, I haven’t updated it since I bought it two and a half
years ago or something.

Thanks so much!
-mark

2

I use an M-Audio UNO…I don’t trust Behringer stuff as far as I can throw it. Almost guaranteed that’s the problem.

3

Oh ok, that’s good to know. I’ve toured a lot with both the BCR and a small behringer mixer and I’ve had no trouble with them from a physical reliability point of view, something which I can’t say for some of my other expensive gear, cough cough Roland. Haha. But yeah, it’s a comforting thought that that could be the problem. I’m not too worried about getting this sorted, and it’ll be great to finally update this thing after 2 and a half years!

4

Behringer sux

5

For a musician trying to make a living, Behringer is a god send sometimes! Not so much right now.

6

These problems are exactly why I haven’t upgraded my Stage 1 with OS 1 since I got it like three years ago.

7

Same here! I never got around to it because I use it so much, and the thought of having it not working a day or two just seemed like a hassle.

But I’ve just borrowed a friend’s M-Audio usb interface thing, an UNO, and it seems to be working fine. Touch wood!

8

Yup, with the M-Audio interface it worked with no problem. Very straight forward. And WOW, loving some of these presets, way more to my tastes than the original ones. Nice! Who did the programming, Amos?

So don’t be afraid to update it, but don’t use a BCR2000 with a macbook because it doesn’t work!

9

Awesome, so glad you got it sorted! I recommend the M-Audio MIDISport interfaces for LP firmware update; they seem to have a much higher rate of success than some other devices.

Glad you are liking the Stage II presets… I programmed most of them (about 80 or so) myself. :slight_smile: I was definitely going for a more modern electro vibe with the new sounds.

Cheers!

-Amos

10

Updating the OS with all the new presets and the arpeggiator makes it feel like a new synth. Very impressive that it’s free too!

Thanks Amos, your programming really impressed me. Really loving a couple of the basses, some really impressive low end, and some of the modulation setups you have going on sound excellent!