Just installed the 3.5 beta and wow, very nice work Rudi, thanks a lot!
3.5 now remembers my global octave transposition settings on reboot.
There’s many more features for this beta that I’m sure everyone will love, but I’ve been asked by Rudi to keep quite about them until there’s an official release.
My suggestion is for anyone wanting to speed up their work flow with their Voyager should try this out.
Just contact Rudi to see if he needs anymore beta testers.
A heads up for anyone wanting to try out this beta:
Before you update to 3.5 be sure to backup your ‘Bank A’ presets because after the update it creates broken presets for the first twenty or so.
Voyager digi-board hardware update ONLY affects how many banks of presets you may have. Any Voyager OS will run on any Voyager digi-board. If you have an old-version digital board, it will run the new OS but you will still have only 1 bank of 128 presets.
The other reason to update the digi-board is if you need to replace the Select Series/EBlue/Anniversary Edition backlight inverter… the new style inverter requires the new (smaller) digital board in order to fit inside the chassis. This does not affect RME Voyagers, only the keyboard versions.
This is on my wishlist too. Something like a fine tune mode.
Or a smaller dead range before the knob movement is accepted as a movement and not some “noise” that needs to be ignored.
What about a menu-enabled mode where you get a “rough” value on the frequency knob of the oscillator you want to tune, then use the headphone volume to fine tune that osc by +/- 100 cents?
Or press a button while turning the frequency knob to go into fine tuning mode, where the range is selected by a button?
I have suggested this to Moog (Rudi, Amos) something like 5 times so far. It would be great to have something like a Shift function where the user presses a button while rotating the Frequency knobs and you can fine tune the Voyager precisely.
OK, I would like to see a version where the fine tuning of all knobs is possible while pressing a button. For example the PANEL button. Then this knob is limited to something like 1/4 or better 1/8 in range based around the value it had before. Then you can fine fine tune the detune or adjust other parameters with the full maximum resolution available internal in the Moog Voyager. All this is only available for one knob at a time.
To leave this special mode, just let the button go.
Because now the adjusted knob value is not corresponding the physical position, this knob need to be moved to the closest possible value that is near to the just fine tuned one, before the change is actually used to edit a sound again. Something like a snap-mode for the knob.
I could easily live with this, if this would not allow to move other knobs or react to the ingoing pedal changes while doing so.
And the Midi CC might not send out the full 14 bit values during fine tuning.
How about this Rudi?
But this is more then a day of coding to do this. And then it has to be tested. And I am not sure about the real bit depth available from the knob scanning hardware.
I think this is something for a 4.0 version. If we will see this. I wonder, how to pay for all the needed work for doing this. Maybe we have to pay for such a new feature in order to get it done. But It would be worth some money for sure. But this is something Moog Music has to think about.
The Voyager is for sure a good investment. I still remember the firmware version before 1.5 I had when I bought my Voyager. And the Voyager got more and more features. All software updates for free. I paid for the new digital board with the 7 banks.
I am asking for this new mode to get the Voyager even better. But it is the best modern monophonic analogue synth with patch memory for me anyway since years.
Is this an issue specific to the RME? I ask because on my Voyager Performer, the ocs. tuning knobs pretty much act like they’re directly controlling the circuit. When turned, they react immediately, and there is no discernible stepping. I just do not notice any issues with fine tuning the oscillators.
I can’t understand the point of even mentioning 3.5 if there are no plans to release it soon. What is the delay on releasing this OS?
Personally I suspect it is something to do with updating the Sound Tower software. Does that require a paid upgrade? I’d not be pleased to pay for that…
I mentioned it to help Rudi get more beta testers and to compliment him on his work. I think anyone can get the 3.5 update though, but with the caveat of losing the first 20 presets, but if you back them up it’s easy to put them back after the update.
I used MIDI-OX to update to 3.5 for free, so the Sound Tower software isn’t needed for this.
Also, I just bought the Voyager Editor Librarian and was told by Sound Tower the next versions are free for v3.4 owners (for anyone wondering about that).
I’m looking for a few RME testers 
