Hi weary,
are you sure LOCAL is on?
Could you connect the MIDI in to MIDI out with a cable?
Is then the MIDI LED on when you turn a pot or hit a key?
Yes, LOCAL is ON.
Doesn’t work. No reaction. Also there is no reaction on external sequencer 
It’s important to remember that MOOG does not hand make every resistor or other minor component, and that flawed components from suppliers can fail prematurely. Mine came perfect in the box new, went wacky, was in the replacement range, I swapped out the analog board they sent as a replacement, following their detailed instructions, and it’s worked perfectly ever since. I sent back the old board at their expense.
How much better customer service and pride in their product could they have had? It was new in 2013 and is a joy to play and make sounds with.
Then it does not send notes or any informations to the MIDI out jack?
This sounds strange for me.
Hey, everybody! Good news here!
Moog Music sent me a new mother board for free!
My Voyager is singing again!
But! There’s one problem with Mod Wheel. It doesn’t work.
And the most interesting is that if I use Mod Wheel Out on my VX-351, if i turn the Mod Wheel control voltage on the ModWheelOut changes.
All local parametres are ON.
Any ideas?
Anybody else have their warranty-repaired main board go bad a SECOND time? Apparently some components used in (or left on) the replacement boards were faulty as well. Trying to sort this out with Moog, but man, am I unhappy with them now.
well that really sucks!!
good luck with the fix…if you find which components went south, would be good to post so everyone is aware
Got an RMA. Hope it gets sorted for good this time.
Well, in addition to the main board, the connections to the input jack panel were loose and that made the screen look like gibberish and the synth not play even after reinstalling a known good main board. I reseated a red connector on the input jack board, and all good.
Thanks for the follow up, happy it is fixed!
Hi,
I´ve run into some problems with my Voyager - there has been some prior issues when the whole instrument would go silent, some issues with the lcd screen and now the filter envelope is not triggering correctly. (There is a lag of varying length between the attack and decay stages, for example with both knobs at zero it now takes from 5-10 seconds for the envelope to close…) Same problems whether triggering with the keyboard or using an external gate. My serial number is 3091, so apparently Moog have stated that there is presumably some faulty parts. Synth purchased in Helsinki in 2011. Anybody with any advice? Is the person to contact still andy@moogmusic.com?
Thanks in advance,
-Tuukka
Yes, and he will authorize an RMA if your Voyager is in the serial number range. It is a Voyager Select, yes?
Good luck.
Ok, thanks for the reply - I´ll try to get in touch with Andy! It´s a performer edition…
-T
Damn … I wish I would have checked here first.
My Voyager RME is on the fritz. All presets have scrambled names and don’t seem to change much if anything from preset to preset. I contacted Moog tech support and they said an OS re-install may fix the issue. The problem now is that I can not successfully re-install the update. I follow the instructions verbatim yet it does not even make it past the first step without issue.
My hope is that it has to due with settings inside of SysEx Librarian 1.4 : Transfer Speed and/or Pause between played messages perhaps. I tried a bunch of settings but unfortunately all gave me the same result.
Here is what I did:
I load the SysEx file into SysEx Librarian. I have my Voyager RME connected via MIDI to my MPK249.
I put the RME into Receive Update mode and start the transfer. All seems to be going as expected except that once the file is done sending the RME still shows a progress bar about half completed.
According to the Instructions the Voyager should Display: “The Operating System must be re-loaded Re-load bank D? …"
I only get a frozen progress bar. If I now reboot I will, however, get the above message. This behaves the same way. It only gets about 1/2 way by the time the transfer is complete. If I now reboot it just asks me the same thing as before, ie “The Operating System must be re-loaded Re-load bank D? …"
Now I’m stuck in a loop and if I exit this mode and go back to Panel the only thing making sound is the noise generator.
OUCH!
Any ideas what is going on here and how to fix it?
FWIW I had better luck using midi OX instead of sysex librarian, it’s also free
did you do this? ( copied from another thread )
The update file order is:
- go to the MASTER page “Receive Update” and send bank “B”.
- then if the Voyager asks for bank “D” leave “NO” and press ENTER.
- in the MASTER menu go to “Receive Update” and send bank “A”.
- now when the Voyager asks for bank “C” select “YES” and ENTER and
send bank “C” to the Voyager. Do the same thing with bank “D”.
Check after the update whether the boot and the system numbers are the same
in the MASTER “Software Version” menu.
I also successfully used Mdiox to update. I had to slow the transfer rate once or twice.
I know it has been a while.
I was storing friends Voyager in my studio for 2 months, and all of the sudden the second half of the synth is not working
Oscilators are generating sound, mixer is working, but filters, envelope and output is not working.
Tried updating firmware to 3.5, and still the same issue.
Can anyone tell me how I can resolve this?
I have a repair here for what appears to be the faulty IC in this voyager OS that a customer brought over. I believe the repair facility i freelance for would likely be or has been a warranty center for moog, but regardless I filled out a support ticket last week and emailed the email left earlier in this thread, but nobody has made any contact with me. Was hoping to get this cleared up as this is for a very good customer in both of our cases…
I detailed the issues in the first post to support last week with all pertinent info.
Thanks!
Sean