hi, i just got my LP2 came installed with OS 2.2 this is my first analog synth… sounds great. imi getting freezes and fatal keyboard overrun warnings a LOT.. is anyone else expereinceing this?? i have only had this synth for 2 days, ive played with it maybe for 2 full hours . just flipping through presets and playing with paramaters.. you know basic stuff… one error im noticing DEF.. is when i go to scroll from prest 34 to 33, if freezes.. if im hitting keys while its switching i get a fatal error, keyboard overrun error, and if i switch without hitting keys it just freees temporarily and than works inbout 15 seconds… is this normal?? i have a feeling its not… 
Try different grounded sockets.
Mine was a little buggy when I first played it. I called up Moog (don’t hesitate to do this, they are awesome and quick) and upon their suggestion moved it from the multi-outlet to its own dedicated wall socket and it worked beautifully.
Both were grounded, so it just goes to show ‘ya never know.’
thanks, that llink you posted to your old thread is EXACTLY what mine is doing… i triend in a wall outlet instead of a stip and its not as bad.. but its still doing it.. how do we find out about updates in the OS??
thanks
b
For a while the parameters on my synth were drifting, after talking to Amos it was decided that a bad ground was causing the malfunction, and i just learned to live with it, then one day I rearranged my sound lab, them BAM it works again.
Why does the LP seem so overly sensitive to grounding issues like this. 
I don’t have a complete answer, but part of the answer is that the synth is always looking at the voltage of the analog pots on the panel, and if it sees a change to this voltage, it responds as though you’ve changed a parameter. Normally this is a very good thing, it gives the LP a fast and fluid response to knob-tweaking. But if there’s some fluctuation of the ground potential level due to a grounding issue, to the LP this can look the same as an intentional tweak to the panel. So, this is why you can get the LP seeming to change parameters “on its own” until you switch to a grounded outlet, disconnect the mixer that has AC leaking onto the audio cable ground, etc.
What kind of power supply does it use?
also, so wht can i do to remedy this??
Is this issue different from the Tribute problem that causes it to react extremely slow when changing patches.
I have 2.20T in mine and never had this problem in the past. I’m plugged into the same power strip as I was prior but since upgrading to 2.20, I now run into situations where changes to a patch causes the OS to stall for a few seconds where you can see the letters of the display drawn out very sloooooowly, afterwhich the parameters are loaded into each of the pots, etc.
Is this unique to the Tribute or have others seen this?
-Mike W. from NJ
Is this issue different from the Tribute problem that causes it to react extremely slow when changing patches.
I have 2.20T in mine and never had this problem in the past. I’m plugged into the same power strip as I was prior but since upgrading to 2.20, I now run into situations where changes to a patch causes the OS to stall for a few seconds where you can see the letters of the display drawn out very sloooooowly, afterwhich the parameters are loaded into each of the pots, etc.
Is this unique to the Tribute or have others seen this?
-Mike W. from NJ[/quote]
NO, i have the SE2 and it has that same problem… very curios i hope there is an OS fix for it because it basically got shipped from factory with errors..?? let me know what youve already heard if anything
NO, i have the SE2 and it has that same problem… very curios i hope there is an OS fix for it because it basically got shipped from factory with errors..?? let me know what youve already heard if anything.
update.. whenever i use preset 33 MINIBASS, it freeezes when the lfo rate gets about 80 % i have to let go and wait 10-12 seconds or so.. than turn it back down.. than its fine but as soon as i go back up on the lfo it happens again… also as started before, going from preset 34 down to 33, even without changing any parameters causes the same or similar error… im going to try and replace patch33 and see what hapens.. ill post when i do it..
thanks
I’m a programmer by trade but it’s boring stuff, not firmware for synths, etc. but I would guess that some new feature in the code is being run by CPU (arp via internal clock or something of the sort) and the right combination of events really taxes the system.
The other thing could be that the code is written in some sort of pseudo code and it’s an interpretive language that periodically triggers some sort of garbage collection. I don’t think it’s a memory leak as I’ve had my LP powered up and in use for a few days at a clip and it never locked up for good, but it’s definitely a problem.
Before, I could (we all could) twist the preset knob endlessly and the lights would flash as quickly as you could turn the knob. Now it’s dreadful. I was playing with a 3 piece this past weekend and it caused me to miss a cue, NOT good!
That’s the difference between a hard wired synth like the true analog Old School and ones with a front end and constantly evolving code. I haven’t tried downgrading and not sure what’s involved in doing so (I suppose a factory reset and a new code load is required followed by calibration?) Need some help here.
Don’t get me wrong, I really like the new features but if it comes at the expense of stability, I’ll need to run at the minus-1 version.
Anybody else seen this or have insight? Mine is a LP Tribute running 2.20T with CV-out mode done. Sys util says 2.2 588.
-Mike W. from NJ
Guys! This is my fault and I’m very sorry. It’s a firmware bug I introduced in OS2.2. I need to get some new factory presets to the production line, and fix the underlying bug as soon as I can. Right now I am working 12-14 hrs a day, every day, to finish the Taurus firmware… when this is done, I can get back to the LP.
Meanwhile, this is the bug: This slowdown happens on presets where the Arpeggiator clock source = LFO. Go to Advanced Preset, Arpeggiator menu, and set Arp Clock Source = INT. Then save the preset. Problem will go away.
Here are the Stage II factory presets that need to be edited:
4, 6, 11, 14, 18, 33, 40, 66, 82.
Again, I’m, very sorry for this. It slipped through testing when OS 2.2 was released, and then I have been unable to fix it due to my other pressing obligations. I’ll certainly correct this bug as soon as I am able.
Kind regards,
Amos
wow, thanks amos for the response.. damn.. your working like a dog… i will fix my LP2 manually no problem
thanks
brian
san francisco, CA
Ditto, thanks for coming clean. Mystery unraveled. I always have great faith in Moog products and appreciate the feedback. Any chance you have a similar patch list for the Tribute patches? (2.2T)
Yes, by all means concentrate on the Taurus code because I’m waiting for mine!!! This is workable.
-Mike W. from NJ
YO AMOS!!
just went through and made those adjustments… working like an, i dont know, a champ? thanks so much.. im feeling a lot more secure. this is my 1st moog.. SO digging it…
thanks everyone
b