Voyager won't update

The Moog Forum Minimoog Forum
1

Hi,

I’m trying to get my Voyager Performer to update to 3.4, and having no luck (previously I took it up to 3.3 with no issues).

Following the instructions in the PDF, I put the synth into Receive Update mode and send bank B with Sysex Librarian. Instead of showing a progress bar the menu pops immediately back to Receive Update, or even to Panel Mode, even as the MIDI light continues to flash. If I try to repeat the process, I get a Sysex Failed!! message before it goes into its waiting-to-receive mode, but otherwise the same thing happens.

I checked all the obvious setup things - midi channels, sysex ID numbers, switched cables, etc - and they all look right. If I put Sysex Librarian into receive mode it will receive bank and OS dumps from the synth just fine. I’m using the latest OS file (vgros3-4-62308), but as an experiment I tried sending a 3.3 bank and got the same results.

Any clues what might be happening? Anything I can reset to give this thing a boot in the ass?

Thanks!
JN

2

There is a problem with the latest Mac OS X 10.5 update . It prevents ALL midi software from transmitting midi sysex the right way. At least this is confirmed on Mac PPCs.

I bet this is the problem here.

This was discussed at the Waldorf Music mailing list. I had the very same problem here. I solved it by using OS X 10.6 now.

3

Thanks, but this is a PPC Mac on 10.4.11, so that can’t be the issue.

4

SysEx Librarian is a very good tool. I use it for years. So there is some other problem.

It is very unlikely, that the Voyager is the problem here. I can’t remember such a problem.

Did you ever did a successful update with the very same configuration of the Voyager using the very same midi interface?

And is the Voyager the only connected midi unit to the midi interface?
Are all other midi related programs closed?
And maybe try to deconnect the midi output of the Voyager in case of a midi loop.
Tese thing should help to check if there are some problems other then the midi file, the Sysex Librarian, the midi interface and the Voyager itself.

5

I checked for a firmware update for my RME card, found one, and updated both that and the drivers. It’s all good now, and I’m on 3.4…

Thanks for the suggestions.

6

Glad to hear it wasn’t the Voyager that caused the trouble.
I never ever had a problem with updating caused by the Voyager itself.
And I think nobody else had problems with it.

Rudi does a great job delivering us good software for the good hardware.