Is there a way to force it to a particular patch #? I backed up a defualt patch and I thought if I sent it back to the voyager it would send it to the buffer but it restores it back in it’s original location from which I backed it up from. Am I missing something or is this how it’s supposed to work?
Yep, that’s how it seems to work.
This threw me for a loop at first, too. I kept expecting the preset to be loaded to the edit buffer (so that I could store it wherever) but transferring a sound to the Voyager blows it directly into the preset slot from which it was transferred originally, so beware of accidentally overwriting something! I started naming the MIDI files with the patch location in the filename so I know.
-Hoax
Thanks hoax. That’s a good tip of naming the patch with location #. I did lose a patch in this trial, but no big deal. Now I know better.
*** for files that won’t go into the edit buffer ***
A patch that is going to a defined preset number starts like this in SysEx:
(all in hexadecimal)
F0 04 01 id 03 nn …
where “id” = is the SysEx id of your Voyager
And “nn” = the preset number its going to stored to.
By changing this in a SysEx editor to:
F0 04 01 id 02 …
Changing the SysEx mode from “03” to “02”.
And delet the preset number “nn”, because there is of cause only one edit buffer.
I found the needed information in the SysEx PDF of the Voyager OS 2.4
*** or do this in this next time ***
store the needed patches that you need later to go into the edit buffer (or you are willing to exchange with other users) by sending them in MASTER menu item 3.1 “Send PANEL Dump” in favour of the item 3.2 “Send Preset Dump”.
I am refering to the Voyager OS 2.5 of cause.
Thanks Qwave. More good info.