I’ve been trying to fix this issue with my Voyager RME for a very long time but for some reason I always just gave up and never asked for help. I’ve searched and searched through this forum ( many times ) trying to find the answer but I just can’t seem to find it.
Here’s the problem:
All of my presets are pre-bent down by their pitch-bend amount. In order to get them back to pitch I have to touch the pitch-wheel on my controller. I’ve investigated the Pre -Value ( from section 1.4 PITCH BEND AMT. in the manual ) but that has led me to zero solutions. I’ve tried manually adjusting the pre-value in the Voyager Editor software, but the value always says PRE 0.0.
I can’t figure out for the life of me how to fix this. Does anyone out there know how to fix this? I’d REALLY appreciate any help. Running OS 3.5.
try this:
disconnect the controller from the RME and switch them on separately.
Move the pitchbend of the controller.
No connect them with a midi cable. To simplify this, do just a straight connection. No not include other midi equipment.
If the pitch is now right, then the controller is somehow sending some nasty pitchbend data. Or some other midi equipment you use at the same time. For example some midi recording software.
And then try to change to a different RME sound by using the RME buttons. Still all right?
And if you use the controller to change sounds, then try this. Still alright?
Try to work this out by changing the sequence of things you do. And simplify it. So the chances are better to find a reasons why this happens. This is the way you try to recreate certain things while beta testing. Only if you can give a full description of what happens when with what kind of hardware, the chances are, to discover the reason why.
Because, the are no other users complaining about this, it has to be something with the incoming midi data (and therefor not a Moog related problem) or a hardware problem not known yet.
So test it. And then give details. I am sure we will find the reason.
Do you have a computer with some midi monitoring software? Try to connect it to the midi thru of the RME after you test the things above. And store the received data. I might give us information about what is happing in detail.
There are so many experienced users, midi freaks, Moog technicians and the Moog Voyager software programmer reading the forum several times the week.
Sorry I didn’t give you guys enough details in my first post. Let me try and give you as much detail as I can. See my comments below.
Right now the RME is being controlled by my Little Phatty, but I have tested this on all of my controllers ( MicroKORG, Nord Lead 2, Axiom Pro, MPK49 and a few others ) and the problem exists on all of them. I’ve also used a midi-monitor app to check for any nasty pitch bend control being sent and I can tell you with absolute certainty that its not coming from the computer, or any of my controllers. Just having the RME connected to the little phatty via midi, no computers involved yields the exact same result.
I only change patches on the RME itself, never via midi ( ok, almost never ).
I’ve created a short screencast to demonstrate the issue. I hope this helps everyone visualize this really strange issue. In the video you will see the voyager librarian/editor software and a midi-monitor. I wanted to do this via the editor software so that you could see me manipulating the pitch wheel in real-time, and hear the impact it has on the oscillators. There is no other controller information being sent to the RME at all, as you can see by the Midi Monitor that I have running. The only data that is in the event list is note on/off and a sysex program change message. I’ve connected the RME to my computer via USB midi ports ( micro lite ). For this demo, I’m sending notes to the RME with my Akai LPK25.
The first thing you will hear is the note F4, but apparently pre-bent. All of the patches on my RME exhibit this behaviour. Watch and listen as I manipulate the pitch wheel, the pitch JUMPS up just as I touch it. As I let go of the pitch bend RME comes back to pitch properly. It really seems like the issue is just that somehow all of my patches are pre-bent, and I can’t figure out how to get them to not be.
Just want to say thanks for your help. I’m still hoping that there’s a chance I’m missing something completely basic and that its not a hardware issue!
So as it turns out, I was finally able to solve this with a complete wipe of the OS and patches. I’m still not 100% sure what was wrong, but I suspect I actually might have installed the Voyager Keyboard OS ( doh! ) instead of the RME. It was a while ago, I’m not exactly sure but HOORAY its fixed.
Glad you got it fixed! It sounds to me as though you had a RME that had the Keyboard version firmware loaded by mistake! The keyboard version scans the pitchbend input, and if the pitchbend signal is not there, as in the RME, it outputs the lowest value. So if anybody else sees this kind of behavior, there’s a nice clue to fix the problem…
