I know this isnt the proper place to submit wishes, but i thought i would run it by this group in case im missing something. i love my RME, but i quite often use it in “drone mode” by flipping the ENV GATE sw…
so heres my list:
1.) the MW mod buss should be able to be used without a ModWheel message. that is, if i had a stand alone RME, i should be able to modulate like i can on the P buss.
2.) the release knob function should work from the front panel. as it is, if “release” is disabled, this renders the REL knob useless.
3.) The LFO rate range should be wider than it is. at its slowest (000), it seems to be around ~5 seconds. no idea what its at at 255.
4.) Glide rate also doesnt work if the software switch has been disabled.
unless you need a truly ultra-short release (in which case, turn off “release” from the Panel Options menu), I’d just leave Glide and Release switched ON in software… then set glide time or release time knob to minimum when you don’t want portamento or long release times. Does this solve your problem? Obviously it’s not as convenient as having those switches always by your left hand, but if you have an RME and need fast access to these parameters, another option is to use a programmable MIDI controller and map a button to these parameters. Glide on/off = MIDI CC# 65; Release on/off = CC#88.
You could also map a button to send CC#1 off=0, on=127; this would turn the Mod Wheel bus on or off. If it was On, you could control the depth of modulation using the Mod Bus 1 Amount knob on the panel, and it would act exactly like Mod Bus 2.
USB is not a good choice because of possible ground loops. Midi uses opto-coupler on the receivers side. So there is no ground loop possible with a non defective Midi connection (thanks to the midi pioniers for thinking of this detail!).
And on the other hand, there is not much data to transfer to or from the RME or the Voyager when using an editor. Only a dump of all sounds takes some time.
And USB causes much more trouble in the software then midi. Remember: Moog still uses analog boards. They are not computer builders like all the VA synth companies. So adding USB would need different skills and plenty of testing for first time USB developers.
a list of known compatible controllers should be maintained on the tech support FAQ page
You should be able to program all really user programmable midi controller boxes/keyboards to work fine with the RME. Even exotic ones like the IBK work fine with the Voyager and RME.
I agree. I don’t understand why the Release “off” or portamento is even an option in the menu. If you don’t want portamento then just save the patch that way! I mean, maybe if you could turn it globally off, but it’s saved per patch.
I just purchased a RME and I have a couple of questions. First of all the Filter tracks the portamento. I thought that this wasn’t the case and you had to pay it extra to get this. Another thing is the high pitch sound from the panel lighting. I thought that they fixed this?
Howdy! The filter tracking is now standard on all new Voyagers; has been for about a year or so I think. You can pay extra if you already have a voyager and would like this mod added at the factory.
As for the sound from the panel lighting, the new lighting you have heard about is on the Voyager Select Series; the RME still uses the first generation of panel lighting. You don’t usually get a high-pitched sound from the RMEs though; that’s a little unusual. Unless the sound you’re talking about is extremely faint… like you have to be right up on it to hear it. That would be pretty normal due to the physics behind the electroluminescent light panel.
I guess what i would like to see are changes in the software.
For example, physically turning the GLIDE RATE knob should override software settings.
The same way for RELEASE— the physical movement should override the software. Theres nothing more frustrating than dialing in a bass sound (staccato) that needs a fast release and having to scroll through pages of menus to get into the OFF setting. argh.
i see your point about midi CC#! and sending 127/0— but i could also just throw my MWheel up.
sometimes i program the RME in “free” mode and wish that it would really be free— but its definitely chained to midi in this case.
Hi,
what’s about this idea?
Turning the release/glide pots to the min position the release/glide switches turn off the release/glide, turning the release/glide pots to the max position the release/glide switches turn on the release/glide…
Have fun,
Rudi
So the number of possible values is 14 bit + on + off = 16386?
Or is it on + off + (14 bit -2 values) = 16384 ?
The first would be working without the need to change any sound data.
And sending these values would not make sense except ON and OFF being send as additional CC #65 (Portamento on/off) and not as Glide time values.
Servus Till,
there’s no change for the MIDI out data of the pots.
When you turn the pot to the min position the release or glide switch is off when the pot value has been reached 0. When you turn the pot to the max position the switch will be on when the pot value has been reached 255.
Is it clear enaugh? Otherwise I will explain it in German
That’s a great idea Rudi. As you have probably figured, some of us like to make these changes while playing, not with menus.
Till, that’s interesting about the midi vs USB. Maybe the solution to having too many midi jacks is to use a midi expander box so I don’t have to chain all my keyboards together in a midi “loop.”
The reason I want a list of controllers is that all my keyboards produce digital artifacts with the Voyager RME. I’m still not aware of a single synth-action controller with a joystick that doesn’t make the Voyager produce digital artifacts with pitch bends.
No no, of course they are still independent; you can use them at the same time for different effects. I meant only that if you send CC#1(mod wheel) value 127, then the Mod Wheel Bus Amount knob will work on the Mod Bus, the same as the Amount knob works on the Pedal Bus. You would be able to turn the modulation amount from zero to maximum using the Amount knob.
I have had my RME for a couple of years and I love it! Often, about half the time, I use it as a pure table-top synthesizer – I bought the wood handles to complete that vibe! And, just as a side note of interest, I almost always use the Real Panel Parameters. I too like to use it in “drone mode” by flipping the ENV GATE switch to ON/EXT, and then I just tweak the knobs and space-noise-trance out. I get plenty of great sounds out of it just as it is. I have found the Mixer Out / Filter In to be quite useful. I have thought about getting the VX-352 to augment the RME’s capabilities, but I would really prefer to be able to use it stand-alone with its existing onboard capabilities, from an aesthetic standpoint. What it amounts to is that when I am doing drone mode, one of the Mod Busses lies “silent” and inert.
I would really love my RME even more, if as soundsubs suggested, that the MW mod buss would “be able to be used without a Mod Wheel message. That is, if I had a stand alone RME, I should be able to modulate like I can on the P buss.” It kind of defeats the purpose to send a MIDI message via mapping a button. As someone pointed out, in that case I might as well just hook up my MIDI keyboard to the RME and use the Mod Wheel (which I do the other half of the time any way . Believe me, for me, it’s not a BIG DEAL, but it would be a big enhancement that would further my enjoyment and creativity.
Isn’t there any way to just turn the MW buss on internally (via a Master Menu selection, etc.)? I guess if so, Amos would have told us. If not, could this be addressed in a future software upgrade?
Yes, it would be really great to be able to enable MOD buss 1 without needing a MIDI controller. I’m at this point trying to control the RME with an analog controller (nice pitch bend:-) and I’d really like to be able to access MOD bus 1 without a MIDI controller. Perhaps this could be addressed in the next software update. (Amos - Rudy??)
I’m using the RME with both a VX351 and 352. I can’t seem to find away around this limitation even with these boxes.
…and it would be great to able to program the range as in pot mapping, as with the CC#1 off=0, on=127 sometimes the value of 127 is too sensitive,
err… replying to my self. Doesn’t this work - pot mapping MOD 1 to Modulation wheel? Seems to but not in a global way, just per patch
This is easy - the only downside is you have to set it up by each preset - just use pot mapping to set the Mod Wheel Buss AMOUNT pot to control the Mod Wheel @ 100%. This means that when you turn the Mod Wheel Buss AMOUNT pot, the voyager maps its voltage to both the MW Bus Amount CV as well as the Mod Wheel CV. Pot Mapping is in the EDIT menu.
If you didn’t want both these controls tied together, you could use a different control, like headphone volume to control the Mod Wheel.
Thanks a lot! I knew that there was an answer. I just didn’t know how to do it. Once again Moog Music proves that they care about their customers in a big way. This information has made me very happy.
. Believe me, for me, it’s not a BIG DEAL, but it would be a big enhancement that would further my enjoyment and creativity.