Updating Voyager OS
Growing frustration
Connected up the new midisport and disappointed to experience the same problem 
It's a mystery as I can receive presets if I do it one by one. When I request the entire bank the midi light flashes once then nothing further happens (except the dialogue box). Other functions such as the touch surface editor works well and voyager midi light flashes as I interact with the librarian program.
I'm using the Mac OX10 version of librarian and a Voyager running OS 3.3 (presently).
Any further help would be very welcome.
Thank to everyone who have helped so far.
Very best wishes
Barrie
It's a mystery as I can receive presets if I do it one by one. When I request the entire bank the midi light flashes once then nothing further happens (except the dialogue box). Other functions such as the touch surface editor works well and voyager midi light flashes as I interact with the librarian program.
I'm using the Mac OX10 version of librarian and a Voyager running OS 3.3 (presently).
Any further help would be very welcome.
Thank to everyone who have helped so far.
Very best wishes
Barrie
What Mac OS X version do you use? There is an awful midi sysex bug in the OS version 10.5.6 or later. It was fixed in 10.6
And you use Sysex Librarian, right? The latest version is 1.2.2.
I had no problem ever before the OS X bug was introduced with an Mac OS update. And no problem since the OS X 106 (Snow Leopard). I am using the good old Emagic MT4 midi interface (actually build by the german company EES as stated in the CE document).
And you use Sysex Librarian, right? The latest version is 1.2.2.
I had no problem ever before the OS X bug was introduced with an Mac OS update. And no problem since the OS X 106 (Snow Leopard). I am using the good old Emagic MT4 midi interface (actually build by the german company EES as stated in the CE document).
keep on turning these Moog knobs
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16 (sold)
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16 (sold)
The version for my mac OS is 10.5.8 (which I guess has the mentioned bug). I'm using the latest Moog librarian software. What puzzles me is that I also downloaded the same program onto my Windows PC and encountered the same problem which suggests another underlying issue??? I'm willing to use either mac or windows to resolve this (so perhaps Subtronic might still be able to help - hope so).
Is there another way to do this I wonder?
Thanks again for help received
Barrie
Is there another way to do this I wonder?
Thanks again for help received
Barrie
The Moog Librarian by SoundTower software had at least once a problem with my midi interface by not clearing the input buffer the right way. Try it with other software.
Try the often here recommended Mac OS X freeware Sysex Librarian for updating. I remember seeing several people having problems with the Moog Librarian.
You might ask for experienced Moog Voyager users nearby (where ever you are).
Try the often here recommended Mac OS X freeware Sysex Librarian for updating. I remember seeing several people having problems with the Moog Librarian.
You might ask for experienced Moog Voyager users nearby (where ever you are).
keep on turning these Moog knobs
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16 (sold)
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16 (sold)
Sure !
If you would like to store a whole bank, then set the Sysex Librarian to record multiple sysex files by using the RECORD MANY function in the upper right. If you record one sound, use the RECORD ONE. The dumping has to be started then n the Voyager's MASTER menu item #3.2 (Voyager OS 3.5).
To update the Voyager, use the Voyager update manual and simply start sending the needed update files (drag them first into the Sysex Librarian window) using the PLAY function (upper left) of the Sysex Librarian. And to not mix four update files: first B, then A, C, D. See the update manual for setails on how to set the Voyager to receive them the right way. It is not just sending and done.
And do a backup of the sounds before you upgrade (a good habit anyway on all synths).
If you would like to store a whole bank, then set the Sysex Librarian to record multiple sysex files by using the RECORD MANY function in the upper right. If you record one sound, use the RECORD ONE. The dumping has to be started then n the Voyager's MASTER menu item #3.2 (Voyager OS 3.5).
To update the Voyager, use the Voyager update manual and simply start sending the needed update files (drag them first into the Sysex Librarian window) using the PLAY function (upper left) of the Sysex Librarian. And to not mix four update files: first B, then A, C, D. See the update manual for setails on how to set the Voyager to receive them the right way. It is not just sending and done.
And do a backup of the sounds before you upgrade (a good habit anyway on all synths).
keep on turning these Moog knobs
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16 (sold)
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16 (sold)
Hey there,
I am on a Mac also, and this update drove me crazy last night. Admittedly, it was late and I was tired, but it really should be simpler than this (sorry Rudi)
I backed up everything first using the Editor Librarian. So I am good with that. But I could not, for the life of me, update the Voyager using the steps detailed here or in the documentation.
My setup:
Voyager Select Series OS 3.4
Voyager Librarian 3.50
Mac OS 10.5.8
MOTU MIDI Timepiece.
Sysex Librarian (used 1.1 last night, updated to 1.2.2 this morning)
Other updates in the past did not give me this much trouble.
The things that confused the most, was I was unable to do the update in the recommended sequence (B, A, C, D). And the fact that bank A gets totally scrambled confused the hell out of me.
I think I got it all sorted when I gave up on the Editor and did the update via Sysex Librarian.
I am going to try doing it again this morning, just to check my steps.. and see where the problem is.
I am on a Mac also, and this update drove me crazy last night. Admittedly, it was late and I was tired, but it really should be simpler than this (sorry Rudi)
I backed up everything first using the Editor Librarian. So I am good with that. But I could not, for the life of me, update the Voyager using the steps detailed here or in the documentation.
My setup:
Voyager Select Series OS 3.4
Voyager Librarian 3.50
Mac OS 10.5.8
MOTU MIDI Timepiece.
Sysex Librarian (used 1.1 last night, updated to 1.2.2 this morning)
Other updates in the past did not give me this much trouble.
The things that confused the most, was I was unable to do the update in the recommended sequence (B, A, C, D). And the fact that bank A gets totally scrambled confused the hell out of me.
I think I got it all sorted when I gave up on the Editor and did the update via Sysex Librarian.
I am going to try doing it again this morning, just to check my steps.. and see where the problem is.
OK, this is what is happening for me here. I am following the update release notes instructions document which says to do B, D, A, C, D (again? typo?).
Using both the Editor or Sysex Librarian, my Voyager does not reboot after loading Bank D.. After loading bank D, it returns to bank A patch page, my only option at that point is to reload bank D.
Can someone please tell me what is the correct procedure? Is the documentation incomplete or incorrect. What is posted here seems to contradict the documentation. And neither is working for me...
FWIW My Voyager does show it has OS 3.5 on it, and I was able to load the new bank to bank A last night.
Sorry to be a pest here, but I think I either misunderstand the process, or something about the documentation is wrong.
Thanks,
Using both the Editor or Sysex Librarian, my Voyager does not reboot after loading Bank D.. After loading bank D, it returns to bank A patch page, my only option at that point is to reload bank D.
Can someone please tell me what is the correct procedure? Is the documentation incomplete or incorrect. What is posted here seems to contradict the documentation. And neither is working for me...
FWIW My Voyager does show it has OS 3.5 on it, and I was able to load the new bank to bank A last night.
Sorry to be a pest here, but I think I either misunderstand the process, or something about the documentation is wrong.
Thanks,
I have had the exact same issue as jwolford....drove me bonkers!
I have OS 10.5.8, and the newest SysEx Librarian. Following the recommend procedure (B->D->A->C->D)), it fails after updating Bank D. My Voyager OS does indeed say 3.5, but Bank A is scrambled as well as other random banks.
FYI, I've contacted Tech and have yet to hear back. I too have updated in the past without problems. There is an issue with Mac OS bug, or the Moog documentation. Hopefully they can help us resolve.
I have OS 10.5.8, and the newest SysEx Librarian. Following the recommend procedure (B->D->A->C->D)), it fails after updating Bank D. My Voyager OS does indeed say 3.5, but Bank A is scrambled as well as other random banks.
FYI, I've contacted Tech and have yet to hear back. I too have updated in the past without problems. There is an issue with Mac OS bug, or the Moog documentation. Hopefully they can help us resolve.
P6, Tempest, Sub37
Sorry to hear that you are having troubles too bhrama, but I am glad to hear that it is not just me.
You should be able to reload just bank A via Sysex Librarian after you've attempted and failed an update. That way you won't be stuck with a bank of interesting but not all that useful random patches.
OK, it sounds like we may have a legit issue here, I'll send an email to Moog support as well. It's against my nature to email tech support, but well, what are you gonna do?
You should be able to reload just bank A via Sysex Librarian after you've attempted and failed an update. That way you won't be stuck with a bank of interesting but not all that useful random patches.
OK, it sounds like we may have a legit issue here, I'll send an email to Moog support as well. It's against my nature to email tech support, but well, what are you gonna do?
Just a side note, if your Voyager doesn't request a specific bank during an update it could be that that bank is already updated, probably after a failed update attempt. I got that information from Rudi.
This happened to me after trying to update from the 3.5 beta to the 3.5 official release. Bank C wasn't ever asked for and it made the update go all stupid.
This happened to me after trying to update from the 3.5 beta to the 3.5 official release. Bank C wasn't ever asked for and it made the update go all stupid.