Home › Forums › General › Panels, Components, Macros › Has anybody made a moog voyager panel???
- This topic has 24 replies, 4 voices, and was last updated 11 years, 6 months ago by Syntholabo.
-
AuthorPosts
-
February 21, 2012 at 3:39 pm #560
Hey, i have been searching and searching but can’t find anything. I had a go at making one myself but it’s over my head I’m afraid. Would be really greatful if someone has even a partially working panel for the voyager. Thx Z
February 21, 2012 at 4:04 pm #3906Well i did two Ctrlrs once for the Mood Voyager and the Little Phatty but moog asked me to take them down, the Voyager is pretty simple most are CCs and some CC pairs, below is a XML for all the parameters
that might help you.
[code:1cdwgl6w]
<?xml version="1.0" encoding="utf-8"?><controller name="Moog Voyager">
<modulators><group name="Mod Wheel">
<modulator name="vgrMWAmount" type="cc_pair" lsb="38" msb="6" />
<modulator name="vgrMWSource" type="cc" midiValueMap="0,0,16,32,48,64,80" number="68" />
<modulator name="vgrMWDestination" type="cc" midiValueMap="0,0,16,32,48,64,80" number="69" />
<modulator name="vgrMWShaping" type="cc" midiValueMap="0,0,32,64,96" number="70" />
</group><group name="Pedal/ON">
<modulator name="vgrPONAmount" type="cc_pair" lsb="40" msb="8" />
<modulator name="vgrPONSource" type="cc" midiValueMap="0,0,16,32,48,64,80" number="68" />
<modulator name="vgrPONDestination" type="cc" midiValueMap="0,0,16,32,48,64,80" number="69" />
<modulator name="vgrPONShaping" type="cc" midiValueMap="0,0,32,64,96" number="70" />
</group><group name="LFO">
<modulator name="vgrLFORate" type="cc_pair" lsb="35" msb="5" />
<modulator name="vgrLFOSync" type="cc" midiValueMap="0,0,32,64,96" number="67" />
</group><group name="Oscillators">
<modulator name="vgrOsc2Freq" type="cc_pair" lsb="42" msb="10" />
<modulator name="vgrOsc2Wave" type="cc_pair" lsb="43" msb="11" />
<modulator name="vgrOsc2Octave" type="cc" midiValueMap="0,0,16,32,48,64,80" number="75" /><modulator name="vgrOsc3Freq" type="cc_pair" lsb="45" msb="12" />
<modulator name="vgrOsc3Wave" type="cc_pair" lsb="45" msb="13" />
<modulator name="vgrOsc3Octave" type="cc" midiValueMap="0,0,16,32,48,64,80" number="76" /><modulator name="vgrOsc1Wave" type="cc_pair" lsb="41" msb="9" />
<modulator name="vgrOsc1Octave" type="cc" midiValueMap="0,0,16,32,48,64,80" number="74" /><modulator name="vgrOsc12Sync" type="cc" number="77" />
<modulator name="vgrOsc31FM" type="cc" number="78" />
<modulator name="vgrOsc3KbCont" type="cc" number="79" />
<modulator name="vgrOsc3FreqRange" type="cc" number="80" />
<modulator name="vgrGlideRate" type="cc_pair" lsb="37" msb="5" />
</group><group name="Filter">
<modulator name="vgrFilterCutoff" type="cc_pair" lsb="51" msb="19" />
<modulator name="vgrFilterSpacing" type="cc_pair" lsb="52" msb="20" />
<modulator name="vgrFilterResonance" type="cc_pair" lsb="53" msb="21" />
<modulator name="vgrFilterKB" type="cc_pair" lsb="54" msb="22" />
<modulator name="vgrFilterMode" type="cc" number="86" />
</group><group name="Mixer">
<modulator name="vgrMixExternalAmount" type="cc_pair" lsb="46" msb="14" />
<modulator name="vgrMixExternal" type="cc" number="81" />
<modulator name="vgrMixOsc1Amount" type="cc_pair" lsb="47" msb="15" />
<modulator name="vgrMixOsc1" type="cc" number="82" />
<modulator name="vgrMixOsc2Amount" type="cc_pair" lsb="48" msb="16" />
<modulator name="vgrMixOsc2" type="cc" number="83" />
<modulator name="vgrMixOsc3Amount" type="cc_pair" lsb="49" msb="17" />
<modulator name="vgrMixOsc3" type="cc" number="84" />
<modulator name="vgrMixNoiseAmount" type="cc_pair" lsb="50" msb="18" />
<modulator name="vgrMixNoise" type="cc" number="85" />
</group><group name="Envelopes">
<modulator name="vgrEnvFilterAttack" type="cc_pair" lsb="55" msb="23" />
<modulator name="vgrEnvFilterDecay" type="cc_pair" lsb="56" msb="24" />
<modulator name="vgrEnvFilterSustain" type="cc_pair" lsb="57" msb="25" />
<modulator name="vgrEnvFilterRelease" type="cc_pair" lsb="58" msb="26" />
<modulator name="vgrEnvFilterAmount" type="cc_pair" lsb="59" msb="27" />
<modulator name="vgrEnvAmpAttack" type="cc_pair" lsb="60" msb="28" />
<modulator name="vgrEnvAmpDecay" type="cc_pair" lsb="61" msb="29" />
<modulator name="vgrEnvAmpSustain" type="cc_pair" lsb="62" msb="30" />
<modulator name="vgrEnvAmpRelease" type="cc_pair" lsb="63" msb="31" />
<modulator name="vgrAmpEnvMode" type="cc" number="87" />
</group><group name="Options">
<modulator name="vgrVolume" type="cc_pair" lsb="39" msb="7" />
<modulator name="vgrMod1Amount" type="cc_pair" lsb="34" msb="2" />
<modulator name="vgrMod2Amount" type="cc_pair" lsb="36" msb="4" />
<modulator name="vgrOptGlideSwitch" type="cc" number="65" />
<modulator name="vgrOptReleaseSwitch" type="cc" number="88" />
</group>
</modulators>
</controller>
[/code:1cdwgl6w]February 21, 2012 at 4:11 pm #3907Hey thanks Atom, but I’m a bit lost here. Is it possible for you to send me the actual panel file?
February 21, 2012 at 5:08 pm #3908Well that means doing the panel from scratch. Ill try to cook something up today but it won’t be pretty.
February 21, 2012 at 5:25 pm #3909Excellent, I don’t want you to go to too much trouble though. And i dont care about how it looks – i’m after functionality first and foremost, i can always try to dress it up later myself. your help is much appreciated Atom. Thanks in advance. i’ll gladly pay you for it or make a donation to a chosen charity if you like to cover your time.
February 21, 2012 at 9:08 pm #3910Ok it’s ready for testing, you’ll find it in the DDB.
February 21, 2012 at 11:10 pm #3911Just did a quick update, i based the values on the free/demo editor on the MOOG page, hope that their editor works and the values are OK. Please let me know.
February 22, 2012 at 4:36 pm #3912Atom, you are an absolute gem!!! I’ve been looking for this solution for ages. Thanks a million. I’m at the early stages of testing yet but so far everything on there works except the external knob on the mixer panel (this also allows users to change presets in internal mode) which at the moment just appears to be dead. Would be good to have some of the missing elements on there too like the Octave selector on the oscillators as well as the main volume and a few other bits. To put icing on the cake it off would be great to be able to change banks in here too…I know, I don’t ask for much )) Anyway for what you’ve done so far, thanks a million. If you’re ever in Dublin the drinks are on me! Thank you thank you thank you!
February 22, 2012 at 4:48 pm #3913One more thing Atom, I use the 64 bit versions of Logic and Maschine which I’m plugging CTRLR into. I can’t see anything on the web site about 64 bit – is there a 64 bit version of CTRLR coming at any time?
February 22, 2012 at 4:55 pm #391464bit on the MAC or on Windows ? I tried the EXTERNAL knob it works with that weird editor from MOOG, the Octave switches are on the panel for each oscillator i don’t understand what do you mean that it’s missing. The main volume knob is in the Performance Controls. I’ll add a program/bank change but can you tell me how many banks and programs per bank the Voyager has ?
I did a small update of the panel with some minor tweaks, so re-download it.
February 22, 2012 at 5:16 pm #391564 bit om Mac.
Ok, so when the external button is set to ON it should adjust the ext audio level, when set to OFF it should change presets. Neither works for me. And yes that Moog editor is very weird! The voyager has 6 banks with 128 presets in each one.
Something funny going on here with the file in the DDB. I just went to download the latest version. In preview window I can clearly see extra elements (like the Octave switch). But when I download it and load into controller lots of stuff is missing. See this screen capture shot. ANy clues?
[attachment=0:14m05ohn]my ctrlr window.tiff[/attachment:14m05ohn]
February 22, 2012 at 5:18 pm #3916Sorry heres the screen shot
February 22, 2012 at 5:19 pm #3917Well you are using a very old version of Ctrlr, please download the latest nightly or stable builds (wichever works better for you), you’ll notice it has new icons and a different look and feel to it. Then let me know.
February 22, 2012 at 5:29 pm #3918Weird, i downloaded that from the ctrlr web site like 3 days ago. Ok have it working now. Looks great thanks. WIll test it fully and advise.
One more question: my hardware controller doesnt have the ability to let me rename the parameter controller buttons but i’ve read on forums that this can be done by midi. So question is – where in CTRLR can i name each of the parameters so that when i load the VST the parameter knobs are named correctly?
February 22, 2012 at 7:16 pm #3919Atom, I have to make a correction, there are actually 7 banks of 128 presets on the Voyager not 6.
February 22, 2012 at 7:41 pm #3920You can enter the EDIT MODE of the panel select each slider/button/list and rename it (the right hand properties panel, the modulator name[unique] is the exported name).
February 22, 2012 at 8:11 pm #3921thx, i can see though that you already have them named so that’s that. For whatever reason they don’t actually come through to my controller (which is NI Maschine). parameter adjustment works fine, i’m just missing the names. I think it just doesn’t support this feature…shame.
February 22, 2012 at 8:24 pm #3922yeah some hosts/DAWs don’t ask the plugin for parameter names or how many parameters the plugin has after it has been loaded, and Ctrlr does not know what panels it will load so it exports just an empty list and it’s up to the Host to ask if they changed, some DAWs do that and it works very well. You could ask the developers to maybe implement something like that i’m sure they would benefit from such a feature.
February 22, 2012 at 9:09 pm #3923Yup, users have been asking NI to integrate this feature for about 2 years. Doesn’t look like it’s coming any time soon. I’m having so much fun with the Ctrlr panel – why Moog would not develop something like this themselves or want to keep it from their customers is beyond me! Thx again.
February 23, 2012 at 12:44 am #3924I don’t know why MOOG isn’t making programs like Ctrlr for their devices (i’m sure they the resources to do that), i think they’re doing something like that for MuRF now. As for NI i don’t know if that’s any priority for them i guess if you push them and give them good reasons to implement that they might.
-
AuthorPosts
- The forum ‘Panels, Components, Macros’ is closed to new topics and replies.