midi control of the filter cut off
midi control of the filter cut off
Trying to automate the filter cutoff using midi and not having much luck just a lot of little noises. any ideas or suggestions ? we're using logic and ive tried it in dp as well with no luck , thanks Roger
thanks for the welcome i was sure id joined a while ago but i guess not ! ive emailed moog and ill do some searching, if i come up with an easy fix ill post it. it seems like it wants to work but we already wasted 2 hours in the studio today. i wonder if it would be easier to use a midi to cv converter and control using cv ? bit of a round about way though
It's no problem recording them. Don't filter out any CC's and record a filter sweep. You'll see what I mean. It's just almost impossible to draw them in by hand. If you find a solution let me know, cause I just gave up. Another option is to just record the sweeps manually (perhaps different sets of 'sweeps'). Save them and apply them to different songs/projects.
Probably make a hash of this again, but.....Leaving the filter CC or any CC number off or on is not going to allow playback, if the sequencer design does not account for the process of record and playback of a hardware synth via MIDI. Have sequencers changed from 'doing it all'?
I believe the configuration of sequencers for particular gear and trademark requirements have made it neccessary to define sequencers with a new language. That language is often vague and only relevent to the user of that one, particular seq. So, the seq are difficult to define in a universal language. Could be that it is incougrous to record MIDI because everything is set up to be more relevant if it is at sync?
This reminds me of reading a manual with significant intrigue, only to find a theoretical inference about the instruments capabilities. The Voyager does write or rather record to MIDI.
I believe the configuration of sequencers for particular gear and trademark requirements have made it neccessary to define sequencers with a new language. That language is often vague and only relevent to the user of that one, particular seq. So, the seq are difficult to define in a universal language. Could be that it is incougrous to record MIDI because everything is set up to be more relevant if it is at sync?
This reminds me of reading a manual with significant intrigue, only to find a theoretical inference about the instruments capabilities. The Voyager does write or rather record to MIDI.
well we finally had some succes, martin gretschmann is in the other studio here and he recorded a fliter sweep into ableton live then played it back into the voayger and it worked fine, he tried it in logic and he had the same problem we had , he reopened logic and it worked ! some kind of logic problem it seems. i havent had a chance to try it myself but ill post when i get it to work properly . it may be a logic 7 issue, they add so much stuff with each new release that may be its sending some spurrious info. yes the lines of midi note event info included two instructions one #4 and one #19 as we were recording in what the voyager was putting out .
And if one uses the new "T.S. Reduction" function of the just officially released OS 3.1 you can set the MIDI of the touch surface to send its data as a single midi CC per axis. This will reduce the 14 bit data to 7 bit ("only" 128 values per axis avialable). This might cause some steppy sound jump on certain sounds. But editing these parameters in a softsequencer will be easier and will work also with older software versions of Cubase, Logic or Performer.
To use this new function press PANEL and go to item 2.1 "T.S. Reduction". Press ENTER and selct if you would like the T.S. to send 7 or 14 bit data. Its that easy.
To use this new function press PANEL and go to item 2.1 "T.S. Reduction". Press ENTER and selct if you would like the T.S. to send 7 or 14 bit data. Its that easy.
keep on turning these Moog knobs
Sequence:
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16
Sequence:
Prodigy * minimoog '79 * Voyager * MF102 * MF103 * MF104z * MP201 * Taurus 3 * Minitaur * Sub Phatty * MF105 * Minimoog 2017+ MUSE * One 16
Filter programming - Please update the System software!!!
Wow - what were they thinking when they programmed the Moog rack??? The midi standard for cutoff frequency is Midi parameter #74, resonance is #71.
Works on Yamaha, Korg, Roland, Nord, soft synths.....etc....etc.
So what does Moog Music do? They concoct some crazy combination of MSB and LSB values that are impossible to program into my Oxygen 8 controller. Jeez guys, what the heck went into that decision?
Hopefully, someone at moog Music will simplify the assignment of these all important controllers and make the Voyager Rack a useable live instrument. Until then, it's for studio use only.
If anyone can help I'll be forever grateful.
Works on Yamaha, Korg, Roland, Nord, soft synths.....etc....etc.
So what does Moog Music do? They concoct some crazy combination of MSB and LSB values that are impossible to program into my Oxygen 8 controller. Jeez guys, what the heck went into that decision?
Hopefully, someone at moog Music will simplify the assignment of these all important controllers and make the Voyager Rack a useable live instrument. Until then, it's for studio use only.
If anyone can help I'll be forever grateful.
www.marafiote.com
Re: Filter programming - Please update the System software!!
This was a quite deliberate decision. Standard midi CCs have way too little resolution for analogue parameters. They are only 7 bit controllers: i.e. there are only 128 steps available to control the parameter in question. Using a CC without parameter smoothing (which Moog can't do because this is an analogue synth, not a digital one) would lead to pretty pronounced zipper noise (as on the rolands, yamahas, etc that you mention). Moog chose instead to use two midi controllers, one to represent the high bits and the other to represent the low bits. I haven't looked at the midi specs for a while but I presume this allows for 14 bits of resolution, i.e. 16384 steps. And it's actually still not enough: at high resonance the voyager definitely exhibits some zipper noise when turning the cutoff knob. So this was hardly a "crazy" decision.pmarafio wrote:Wow - what were they thinking when they programmed the Moog rack??? The midi standard for cutoff frequency is Midi parameter #74, resonance is #71 ... So what does Moog Music do? They concoct some crazy combination of MSB and LSB values that are impossible to program into my Oxygen 8 controller. Jeez guys, what the heck went into that decision?
er, why not just use the voyager rack's controls in a live situation? Why would you want to limit yourself to the oxygen 8's (frankly) low quality knobs when you could use all the RME's lovely pots?pmarafio wrote:Hopefully, someone at moog Music will simplify the assignment of these all important controllers and make the Voyager Rack a useable live instrument. Until then, it's for studio use only.
Thanks
Thank you for a thoughtful response and the additional clarification. I never considered the analog vs. digital aspect of controllers. Now I understand.
www.marafiote.com