KB Amount Glitch

I just made an LP patch where I’m using the filter’s resonance only for tone, and was annoyed when I discovered that the ‘KB Amount’ won’t save between about 3400 and 3740 (precision mode amount), or any higher than 3740, as every other parameter goes to 4095. The pot also skips straight from 3400 to 3740 and tops out there. I can reach the skipped parameters using the Precision Mode, but cannot save them to memory.

The main annoyance is that this small blackout area is where the ‘KB Amount’ would tune the filter resonance true to the keyboard, so my octave is forced to be sharp by a semitone, or flat by a semitone.

I found this glitch using OS v.2.0, and immediately upgraded to OS v.2.21 hoping it would be fixed, but to no avail.

Has anyone else found this problem, or come up with a magical fix?

I’ll check this out later tonight or tomorrow and let you know what happens on my LP?

Anyone else have this problem?

Thanks - I’m eager to find out whether this is a problem with the OS or if it’s just my LP.

All anyone has to do is enter Precision Mode from the main menu and then select KB Amount and crank the Filter pot all the way clockwise. If it tops out at 3738, then its an OS bug. If it goes to 4095, then something’s wrong with my Phatty.

Update:

I contacted Moog’s Tech Support and Rosser Douglas promptly replied. Through a couple e-mail exchanges it seems that the problem is with my LP. He checked a few LP’s at the factory, and the ‘KB Amount’ parameter worked fine from their filter pots.

It seems a weird problem, as this is the only parameter my filter pot and save function have problems with. It’s hardly a crippling issue, so I won’t ship my LP all the way to the factory to get it fixed (my warranty is expired). One day I intend to get the CV output mod done, so I’ll get my ‘KB Amount’ taken care of at the same time. sigh

hi, a have THE same problem, and i was told it is a software issue. :frowning: so it’ s not?

hi, a have THE same problem, and i was told it is a software issue. > :frowning: > so it’ s not?

Woah! Really? Well, if that’s the case, then it’s not just my machine. Then it is either an OS bug, or a hardware problem with a certain amount of LP’s. My LP Stage II’s serial number is SE04256. Perhaps there was a hardware problem with a run of LP’s (maybe with a similar serial number to mine).

If anyone is reading this who could check their own LP, it would be very helpful to figure out this problem. As I mentioned above, just enter Precision Mode from the main menu and then select KB Amount and crank the Filter pot all the way clockwise. If it tops out at 3738, then its an OS bug. If it goes to 4095, then there is a hardware problem that affects at least two Phattys.

i have Stage I SE02160.

and i was told it is a OS bug which will be fixed. that was, what, 2 years ago? or 1,5.. anyway the problem is still with me

It MUST be a firmware bug, as I just checked the demo Phatty at my local music store, which had the same odd KB Amount behavior.

I hope this is taken care of in the soon expected OS 3.0

So, the latest word I’ve gotten from Rosser is:

“I have talked with one of our engineers, and apparently this problem can come from the DAC calibration being off. There is a chance that all three LP’s that you have experienced have drifted in their calibrations. To fix this requires a multimeter and opening the LP up while it is on.”

My encountering this problem happened because I’ve been getting deeper in to programing and patching my LP, and would not have even noticed this before. So I don’t know for absolute certain if it’s something that’s drifted over the year and a half I’ve had it.

With three LP’s displaying the exact same problem, at the exact same precision amounts, it would seem to be a factory calibration error of some kind rather than a random drift over time.

FWIW, mine does it too. This is a Stage I, serial SE00380, running OS 2.10S.

Interesting, a Stage I as well.

Well, Amos, if you happen to read this I would be delighted to hear any opinion of yours: Calibration drift, factory calibration error, or firmware bug?

I also think it has nothing to do with time period.
Something would change over time, but it stays that way, and i’m talking from my experience ( 1,5 - 2 and values don’t change)

Hi all- Just to input: I have a Tribute (serial #188), running V 1.04T. The filter amount goes all the way to 4095.

Good Luck ! :slight_smile:

good for you :laughing:

Is it the ‘Filter Cutoff’ amount or the ‘KB Amount’ that you mean?

The issue at hand is the ‘KB Amount’ as selected by the filter pot.

Hi- It is the “keyboard amount” . All the way to 4095.
Cannot understand why it would ~seem~ to be a software issue, but not so widespread. ( I hope.)

Thanks for your post - up until now I’d counted four LP’s with the error and none without. I’d hoped to hear from more LP owners to see if it was a universal problem or a selective problem. Though, if you’re running OS 1.04T, it could be something in OS 2.xx systems.

Any OS 2 users care to check their units?

stage 1 SE0851 OS 2.21

Kb amt via pot goes upto 3798
in precision mode with value encoder it goes upto 4095 but has a jumpy behavior (definately could be my encoder)

I have not check what values will or will not save with a patch, yet.

Also, the tribute edition also has more parameters that use the Moog RAC technology. I am not sure if KB AMT is one of them. I think it is a couple more. From stage manual “In the Stage Edition,
RAC provides responsive analog control for the Osc 1 & 2, Filter Cutoff, Filter Resonance,
EG Amount, Overload and Filter EG Sustain parameters.”

Noprobs here with my Tribute (serial # 29) running OS 2.10S
:slight_smile:

So far with the error are three Stage I’s and two Stage II’s. And the two Tributes mentioned are free and clean.

This is an interesting point. I’ve just taken a look at the Tribute manual and it doesn’t mention any specific parameters for the RAC. So, it’s quite possible that the Tribute does have RAC control for the KB amount, which could be why they don’t have the problem, regardless of their firmware version.

I’ve made a couple sweet patches now based on the tone coming from the noise source through the resonant filter. And it sucks that this KB Amount blackout is right in the sweet spot where my keyboard would play the filter in tune.

There’s still a glimmer of hope in my mind that it could be a firmware fix instead of a re-calibration, because it’s so much easier to update the firmware than ship the thing across the border to Moog.

If Rosser understood and researched my question properly, and the Stage II’s coming out of the factory are now fine, then it may involve a factory repair. I suppose it’s a good excuse to get the CV output mod done. :frowning: