I updated to the keyboard OS 3.3 about 2 weeks ago, and I noticed that a subtle “bug” was fixed, or changed. back in version 3.2 if you physically put your mod-wheel to it’s highest position, and then changed to a new patch, it’s electronic position would stay in that position. Now in version 3.3 whenever I change patches it always resets back to the “no-modulation” position. The 3.2 version was useful (and at times nesessary) for me, because when I would have patch that I would end up having full modulation before going to the next patch, I would set up my next patch to use that first modulation bus, and it would smoothly transition, now instead, I have to quickly Jiggle the modwheel after I’ve changed patches…this can seem really jagged when I want to make a smooth sonic transition. Anyways, is anybody aware of any possible way that I can change this? Thank you.
The reason to reset the mod wheel after a program change has to do with the pot mappings. Maybe it’s better to get the actual mod wheel pot value after a program change. I will fix that in the next OS.
Have fun,
Rudi
Hello Rudi,
to me the modwheel is a performance controll. And changing the patch should not change the electronic position. The modwheel sould always act WYSIWYG.
I know only a few synths where it was different. One was the PPG wave 2.2 and 2.3 where the modwheel position was a part of the sound patch, because there was no other way to change modulation ammounts.
I also agree with till here, in that it’s definitely a preformance control. Thanks for getting back to me so quickly Rudi
I agree with till as well.
ok guys,
if you want a beta version please send an email to me. I’m working on the keyboard version at the moment (RME version later) and I also need beta testers for the new pot routine (no zipper noises when you’re turning more pots in the “no display parameters” mode.
Have fun,
Rudi
There’s another problem that I’m having that kinda partains to this. I own the voyager editing software, and it pretty much works just fine, but when the 3.3 update came out I went to update using the voyager software and nothing would happen, I had many back and forth emails with the soundtower help-guy and Amos, and eventually amos just made some firm-ware loaders for me. That was generous and I appreciate it, but every time that I’d want to update, I’d have to nag at Amos about it. I’ve tried Midi OX and that doesn’t work either, so I’m really confused as to what’s going on. I’m not sure if it’s my computer, my midi interface or perhaps even my voyager somehow. Virtually any other midi function works on the voyager editor and with anything else (soft-synths, etc), so does anybody know what could be wrong?
eMop:
we need a little more input:
When you start to load bank C to your Voyager can you see the bar graph?
If so is there an interrupt during the transfer?
Stops the bar graph?
If not, did you get a message on the display of your Voyager?
Or did you get an error message on your computer?
Please let us know.
My voyager screen sits waiting for the transfer, so nothing changes there
My sound editor says that it’s transferring, but shows no progress being made.
When I used midi OX the sysex window says that it’s completed the transfer, but my voyager still just sits there waiting for a transfer. I’ve doublechecked my sysex setup and midi setup a bunch of times, and swear that nothing is off.
Thanks for your assistance.
My voyager screen sits waiting for the transfer, so nothing changes there
Maybe this is a stupid question and don’t beat me…
But before you start the transfer you know you have to go to the MASTER menu page 5.4 (Receive Update/ENTER/CURSOR–YES/ENTER)?
Cheers,
Rudi
Yes, I know you have to go to the receieve update page, That’s what I meant to say by saying “waiting for the transfer”, sorry about that. Just for clarification the screen reads
"Waiting for
System Exclusive
Data Transfer of
Banks A, B, C or D"
and stays that way after sending any sysex from my computer
This sounds curious…
Is it possible to load presets with MIDIOX into your Voyager?
BTW, Stefan Schulz the email address you sent didn’t work… 
No, anything related with sysex doesn’t work. Including MIDIOX. If it helps, I have a Yamaha UX16 usb interface.
When you send a SysEx file (bank B or so) from your Voyager to MIDIOX - can you see an incoming data stream?
If I can offer some advice - and by no means am I a MIDI expert - but I had a few problems sending sysex via MIDIOX and a USB-MIDI interface.
My particular trouble was caused by a kind of “MIDI feedback loop”. I was sending sysex out the USB to the interface to MIDI in, and the MIDI out came back in the MIDI in of the interface. The problem was the MIDI in (from the interface) was also configured via MIDIOX to send the incoming MIDI back out!
- Try and disconnect the MIDI out from the Voyager.
- If sysex transfer then works, go into MIDIOX > port routings and set up the routings so the input is not patched to the output.
I hope this helps, or you find the answer to your problem.
P.S. if the sysex cannot transfer, how did you get 3.3 loaded? Are you saying that the sysex only stopped working after you updated?
latigid: Thanks for the help (I won’t know if it worked until monday, I’m getting my computer repaired), but I can answer your last question about how I got 3.3 transferred: Amos Gaynes made some executable firmware loaders for me that worked.
Sorry, of course, you said that before.
Well, I’ve tried disconnecting my midi-out cable from my voyager, and tried updating using MIDIOX and the editor software, but still nothing works. Oh, and to answer your earlier question, Rudi, there is no sign of progress going on in the voyager screen. Thanks everyone for your help.
I’m sorry…but is there no more advice left from anyone? I’d really like to fix this.
there is no sign of progress going on in the voyager screen.
If there’s no bar graph on the Voyager’s screen when you send the System ROM to a computer then your Voyager is broken. I can’t believe that MIDI notes and controllers are working and the SysEx transfer not, this sounds very strange for me.