Weird problem when updating the Voyager

The Moog Forum Minimoog Forum
1

So I bought the Voyager editor and made backups of all the sound banks from with the editor. My MIDI interface works bi-directionally with the Voyager just fine (it both sends and receives MIDI).

However, when I tried to upgrade to OS 3.4 (or 3.5) nothing happens. :unamused:

I follow these steps:

  1. Master → Receive Update → This will delete the OS and then I press yes
  2. So I get a message “Waiting for system exclusive data transfer of Bank A, B, C, or D”
  3. On the Voyager Editor → Help → OS update from file → I choose bank_B_340.syx → reduce the packet size to 128 → Start … and nothing happens.

I don’t see any activity either on the Voyager or in the MIDI interface or in the computer. I tried with different sizes and no luck. I tried the option

Help → OS Update 3.5 and still no luck

I tried it with MIDI-Ox and no luck. I can receive Sys-ex from the Voyager but not vice versa. I checked to see if Sys-ex is enabled in the Voyager and it is.

Help. :cry:

2

This should answer all of your questions, if not, you may have bigger problems:

http://www.moogmusic.com/forum/viewtopic.php?t=8572

Btw Rudi told me specifically to use MIDI-OX to update the Voyagers OS, not the Editor Librarian.

3

I have tried MIDI-Ox too… :frowning:

4

And you used these instructions?

On Windows, using MIDI-OX and the same configuration in the screenshot, goto:

View → SysEx

Then on your Voyager goto:

Master → Receive Update → Delete Operating System

Then transfer the banks as prompted by your Voyager using MIDI-OX SysEx:

SysEx → Send Sysex File → B → (skip D) → A → C → D

5

Check your cables and/or MIDI loops?

6

These are precisely the values in MIDI-Ox (I have also used it with other values lest the Voyager chokes). I don’t have any MIDI loops whatsoever.

It’s driving me nuts because I sent and received all of the banks using sys-ex. In MIDI-Ox, I can send the System and Boot ROM with sys-ex and they show up in the monitor window.

I don’t see any activity in my MIDI interface when sending the updates. Could it be that it chokes? When sending sys-ex from the Voyager I see it’s activity LED flashing rapidly but when I send the updates it’s always on.

This is crazy.

7

When I did this I had to manually draw the connection between the “MIDI-OX generated event” port and the Voyager port in the port routings view of MIDI-OX.

8

Such a connections already exists in mine. :confused:

9

I had this problem, and somehow, the midi port selection got scrambled. I’m not sure what fixed it, but cycling the power on the Voyager and re-selecting the proper midi ports in the editor fixed the communication problems. (I’m using a MOTU MTP midi interface).

When I used the Voyager Editor to update my RME, I had to set the packet size to 320. Smaller numbers kept failing part way through.

You are using the right OS for your system? Do not sent the RME OS to the keyboard.

The latest update for the editor includes both the RME and keyboard versions of the software. Under help, just select the “Update Voyager OS” option and see if it works (the latest update to the editor is free) because your OS files might be corrupt. Also, make sure you are sending the bank the Voyager is waiting for. If you try to send bank A when it wants bank B, it will just sit there. (Yes, I did read it was the first bank, so it shouldn’t matter which one you send:) ).

What midi interface are you using? Is there a configuration panel for your device? If so, double check it isn’t filtering anything and that the settings are compatible.

I’ve found updating the OS is different than transmitting/receiving patch bank data. It is more finicky. I had no problem with my keyboard, but had to do the RME like 5 times before it went through without a problem.

10

Do you have “Pass sys ex” enabled in MIDI-OX?

Obvious question but has to be asked.

That’s the only reason I can see it appearing in the sys ex window but not appearing at your MIDI interface.

11

Hi,

I am using a Yamaha UX-256 MIDI Interface. Initially the Voyager was connected to port 6, but after I noticed that I can’t update it, I connected it to port 1.

I have downloaded the OS 3.5 for the Voyager keyboard, got the files from Moog’s site. But there were only 4 banks, is it possible that I got the wrong ones?

I have tried different buffers and delays, nothing works. Have rebooted my PC, switched off and then on the MIDI interface, and same with the Voyager. It just loads version 3.3. as if nothing happened.

I checked for possible filtering, and no. There isn’t any sys-ex filtering, otherwise I wouldn’t be able to send and receive whole banks to and from the Voyager.

:confused:

12

Guys the files I am using I downloaded them from:

http://www.moogmusic.com/voyager/?section=product&product_id=163

it’s the voyager_3_5_keyboard_web.zip

Right?

13

Well,

I think I solved the problem! :smiley:

I just had to install new driver for my MIDI interface. The old one was ver. 2.07 and the new one 2.17. It kinda crapped Bank A of the presets with weird names like I_fvcked_bank_A_^%&^% so I had to reload this bank manually. I am waiting for Rudi to confirm that I am ok - it boots with 3.5 and all the menus are there, just want to make sure because it freaked me out.

Peace
:smiley:

14

Yeah, I’d say you got it. The OS file really just leaves the banks in some random state. I had to reload all the banks too and it was simple and everything is working flawlessly.