Moog Music Forum

Hey guys,
I got a reply from Moog support today, and they said it was fine to share it here:

The first bank to be
loaded will be Bank B, and on a lot of units that I have experienced it
will then immediately ask for Bank D after that, which you should just
give it (basic rule of thumb would be to give it whatever bank it asks
for). It probably will not reboot after this load-in of Bank D. You will
then need to go into the Master Menu->Receive Update and then send it
Bank A. After Bank A has been successfully transferred it will probably
begin to prompt you for the remaining banks (Bank C and then D again).
It is not a typo, and you do need to re-send it. After all this, your
Voyager has been (finally) successfully updated to OS 3.5.

Reloading the same operating system onto the
Voyager twice is not a problem, and can be a good way to assure that you
have done it successfully.

Thx, Jwolford!

Somehow I got it to work properly last night. Don't know quite how, or why after numerous attempts, but...wipes brow...WHEW!

Thank you for everyone's efforts, I never received response from tech.

No problem, bhrama. Thanks to Subtronik, csus7 and Moog support for chiming in on this.

I honestly think the documentation should be revised to reflect what we've learned here. This was a confusing update, but the new features are very nice and the new presets are great.

I kind of like challenges like this cause it gives me a chance to dive in deeper and I come out with a better understanding of whatever it is that was giving me trouble....

OK, I just did the whole update once again, and it asked for bank D after each update. Moog support said to "give it whatever it asks for" so whenever Bank D was requested, that was the bank I sent. So it went like this:

Send Bank B (Voyager reboots), Requests Bank D (no reboot, had to select master/ receive update before sending next update)
Send Bank A (Voyager reboots), Requests Bank D (no reboot, had to select master/ receive update before sending next update)
Send Bank C (Voyager reboots), Requests Bank D (no reboot, had to select master/ receive update before sending next update)

Doing this did not scramble preset bank A as it had before.

As bhrama said, WHEW!

Here is the right update order again:

1) Start with bank B (this is the boot system and it makes really sense to start with that bank first)
2) Then when the system asks for bank D leave "NO" and press ENTER.
3) Then press MASTER (page 2.4) and load the banks A,C and D.

Have fun,
Rudi

Hi all,
managed to save my presets with SysEx today It's one big file... is that ok, particularly if I have to reinstall after a failed update ?
Next step is to update my Voyager from 3.3. Could someone talk me through the process please. Thank you. Best wishes Barrie

I'm having all sorts of problems with this. I tried updating to 3.5 from 3.1, and everything is all messed up now. I tried the various ways of updating via this topic, and none of them have prevailed successfully. I now have banks A,B, and C, duplicated in banks D,E, and G. The unit says it's running 3.5, and from what I can gather, the 3.5 additions seem to be working, but my presets are all messed up. When I bought the unit, I had 7 banks of presets, all different, while the Voyager was running 3.1. Since I wanted to get the Librarian software, I wanted to update to 3.5. It has been a disaster so far. Any tips/tricks? Things to try?

Hi leorapture,
your problem has nothing to do with the software - you re-loaded the factory presets in all banks.
If you want to reload the presets from A-G send me an email (rudi at moogmusic dot de)