Help! Voyager now plays tone with no keys pressed

[brewatl]

This just happened. My Voyager, which is about 8 months old, just started producing a sound with no keys pressed. I've unplugged everything except the headphones. I've reset to factory. I've unplugged and let it sit. Turn it back on and there is the tone. Now it just plays a tone based on the last key pressed. No matter what sound I dial up, I'm getting this. Including when I init parameters to the base Moog sound. Did this thing just go south on me? No amount of knob twisting is helping here.

Thanks,
Mike

[GregAE]

Check the setting on your ENV.GATE switch (next to the HEADPHONES jack). From your description, it sounds like it's set to 'ON/EXTERNAL' instead of 'KEYBOARD'.

'ON/EXTERNAL' allows the Voyager to sound continuously. Nice for drones where you don't necessarily want to keep your hands on the keys, or if you are processing external sounds.

'KEYBOARD' sets the Voyager to sound only when a key is pressed, i.e. normal operation.

- Greg

[brewatl]

It is set to keyboard. The tone that is generated is actually not as strong. When I press a key or set to On/Ext, I get a full tone. When it's set to keyboard and I'm not pressing a key, the volume is a bit lower. One other note, I did add a VX351/CP251 about two weeks ago, but it has been playing fine over that period if time until just yesterday.

Mike

[MC]

Check the local control page. Sometimes all the local controllers are set to OFF. I have OS v3.5 and it happens very infrequently.

[Brian G]

Is doing this on all stored patches ? After checking the position of the keyboard/ env, gate switch, click it to env and back to keyboard even if on. If you still gave a problem after trying that and checking the menus , hope not but there maybe a chance there is a problem with the keyboard control board.

Hope it is simple fix

[GregAE]

One other note, I did add a VX351/CP251 about two weeks ago, but it has been playing fine over that period if time until just yesterday.

Does the problem still exist when you disconnect the VX-351 from the Voyager?

[brewatl]

I did disconnect the vx351. The tone is still there. I also shut off local control for all inputs and the sound continued.

Going to be on the phone with Moog to see if there are any other suggestion.

Mike

[GregAE]

I did disconnect the vx351. The tone is still there. I also shut off local control for all inputs and the sound continued.

Going to be on the phone with Moog to see if there are any other suggestion.

Mike

Okay - maybe this is a long shot...

Did you install the terminator that should have come with the VX-351? Maybe Moog engineering has changed it, but originally the VX-351 needed to have a terminator strip installed in the Voyager to work properly with the VX. I really doubt that this has anything to do with your issue, but I'll put it out there anyway, just in case.

Trying to help...

- Greg

[RL]

Check the local control page. Sometimes all the local controllers are set to OFF. I have OS v3.5 and it happens very infrequently.

Hi MC,
that's an easy thing... many sequencers are sending a Local Off message after the start. When you switch on your Voyager after the sequencer the Local Control settings of the Voyager stay active.
Have fun,
Rudi

[brewatl]

Yup - I installed the adapter in the Voyager.

VX351 was working like a charm until this issue started. I do appreciate the help, everyone. I spoke with Moog tech support and after talking about the issue, the possible culprit is the main analog board going bad. So it's RMA time. Thankfully, it's under warranty as the board is about a $600 part.

Mike