I tried updating the OS on my Voyager yesterday and had no luck. I’m hoping someone can help. I am using Sysex Librarian on a Mac G4 running USB to a MOTU MIDI Express XT interface and out to the Voyager.
I have an AE with OS 2.1 installed. I read the OS 2.1 document and the manual, but I’m still having a problem somewhere.
I set the device ID on the G4 as 1 and the Voyager’s device ID is set to 1. (MIDI In is on in the Voyager and MIDI channel is set to 1) The OS 2.5 document says load bank B, then A, then C. I load bank B into Sysex Librarian and transmit. The Voyager receives the transmission about 85% of the way and then fails. I’ve tried selecting the MOTU and the Voyager in Sysex Librarian and I get the same problem.
Does anyone know what I’m doing wrong that is causing the bank not to load properly?
What does the Voyager do when it fails? A message on the display of the Voyager?
Maybe the files is corrupt. Try downloading it again. Except for the Midi interface you used I used the same set up with no problems on the Voyager 2.1 to 2.5 update.
Thanks for the fast response. I downloaded the files directly from the Moog website, but I guess I can try it again. Yes, the Voyager does display a message. There is a bar that “fills up” about 85% of the way while transmitting on the Voyager’s display and then, an error message says something like “OS Update Failed!!!” If you have any ideas, please let me know.
I hope I don’t confuse matters here. I do not use a MAC but within the PC software I use (MIDI Ox) there is a parameter that I always have to change or exactly what you are experiencing happens… a sysex transfer reaches > 75% and then it fails.
The parameter has something to do with the delay (in milliseconds) of buffers used for transmitting syx files. In MIDI-OX the default is 60 milliseconds. I just bumped it up to 1000 and transfers worked pefectly ever since. I originally found out about this change when I first had my Voyager and wanted to listen to other preset banks available off the Moog site; I encountered the same problem you describe. Then again when I tried my first update… same thing.
im so frustaded because i’ve got the same problem. i’m too a mac-user and can’t load the new system per sysexlibarian to my voyager. what other tricks are there avaible?
I’ve used SysEx librarian to successfully update the Voyager on several occasions and have not experienced the problems reported here.
Try adjusting the transmission rate for SysEx. Here’s how:
Open SysEx Librarian
Go to SysEx Librarian Preferences
Using the slider, increase the “Pause between played messages” parameter (150 msec is the default setting - try increasing it.)
Close the Preferences window
Also, I’d suggest that you make sure that no other MIDI programs are running while you do this (i.e. sequencers). Keep the setup as simple as possible for this update - have MIDI cables connected directly between the Mac and the Vger, avoiding any MIDI controller boxes or ‘thru’ connections. Sounds a bit extreme, I know, but you don’t update the Vger that often, and it’s important to get this right.
I’m having the same problem trying to update from 2.3 to 2.5.
Setup is: Mac G5 (OS 1.3.9)-Digi 002R- Voyager.
Using Sysex, it seems to get about 90% done and then gives me the "System Exclusive transfer has failed message. I have tried with different “Pause between message” settings but to no avail.
Have also tried to use the demo of the Voyager software but it only seems to go about 75%.
Also tried playing via Pro Tools to Voyager with no success
MIDI in and out is fine for recording and playback with the Voyager. I hust cannot seem to get the Sys Ex to install.
Does anyone have any further info to help me out? Have read most of the posts on the forum regarding this issue but still cannot figure out how to complete this task.
Disconnect the cable of the Voyager’s midi out. Many midi problems are just simple midi data loops.
Then try to download the needed OS files again. Sometimes the files are just somehow scrambled. And remember the old Netscape versions did sometimes wrong on Midi-downloads.
Setup is: Mac G5 (OS 1.3.9)-Digi 002R- Voyager.
OS 1.3.9 should read 10.3.9 or you got one of the very earliest Mac OS versions.
Another problem might be the midi interface buffer. Some midi drivers are not build for long streams of a single Sys-Ex message. So try to borrow a different midi interface from a friend and try it. Or check for a newer driver version for this interface.
It is very easy here:
I connect my Emagic MT4 via USB and connecting an midi output from the interface to the voyager’s midi in. Starting Sysex-Librarian by double clicking the first of the needed Safari downloaded sysex files. Then set the voyager to receivve the update and start the send of the midi data in the Sysex-Librarian. That’s all here. I am running always the newest OS version here (10.4.1 right now) and had no problem ever updatinng my Voyager using several OS versions since I traded in my Voyager for a Alesis A6 last summer.
I think it has more to do with the MIDI interface then the software. Once I worked out my emagic MT4 interface worked better then the others I have, I have not had any problems updating my Voyager from rev. 1 through rev. 2.5.
I tried my M-Audio Delta 1010 and MOTU 828mkII and niether would work . . failing the OS install about 85% in . . QWave seems also to have had no problems with the MT4.
There are settings to increase the buffer and lower the speed of the sysEX transfer but for me, none of these settings worked . .
Fundamentally . . if you are Mac OSX based then you should go out and look for a cheap MT4 interface . . it works EVERY time.
Do you know anything about Unitor 8? I have been very reluctant to upgrade my Voyager’s OS since reading some of the ‘horror stories’ on the forum, but it would be good to have the latest version.
Ah Ha-
Got it to work by dusting off my old roland midi controller (pc 300)with dead keys. I hooked it up via usb and ran the only midi out port to the voyager. Had no idea I could use that midi out for to transmit sys ex through the controller.
Thanks everybody for the advice
Once again, Must avoid digidesign interfaces for anything other than Protools
There was a switch on my PC-300 (controller) that let me choose between ‘keyboard’ and ‘pc’. It did not work in ‘keyboard’ mode but it did in ‘pc’ mode. You may need to look into tht as well.
or you got one of the very earliest Mac OS versions.