writesure
Joined: Dec 31, 2004
Posts: 3
Location: Brighton, Colorado
|
 Posted: Sun Jan 30, 2005 6:34 pm Post subject:
MIDI out modules |
  |
|
| One of the main reasons I'm getting the g2(x) is to use the midi out modules to send note and controller data to other gear in my studio. Are there any issues with these modules that I should be aware of or do they pretty much work as advertised. Specifically I'm wondering about processor lag time (latency), more exactly this; a midi start command is sent to both a drum machine and a g2 note sequencer (and or control sequencer)(via an input module, sure) feeding a midi out module which is feeding an external (real) synth. Will the timing between the drum machine and synth be pretty smack on? Anybody doing this kind of thing? |
|
Rob
Joined: Mar 29, 2004
Posts: 580
Location: The Hague/Netherlands/EC
G2 patch files: 109
|
| Posted: Mon Jan 31, 2005 7:33 am Post subject:
Re: MIDI out modules |
|
|
| writesure wrote: | <snip>
more exactly this; a midi start command is sent to both a drum machine and a g2 note sequencer (and or control sequencer)(via an input module, sure) feeding a midi out module which is feeding an external (real) synth. Will the timing between the drum machine and synth be pretty smack on? Anybody doing this kind of thing? |
When the G2 receives a midi clock signal the G2 masterclock will automatically start to listen to this external clock. A ClkGen module must be set to 'Master' to use this external midiclock. The ClkGen module has an 'Active' output that goes high after a MidiStart command and goes low on a MidiStop command. The 1/96 or /16 clock outputs on the ClkGen must be ANDed with a logic module with the Active output, which makes sure there are only clockpulses when midiclock is set to run. Then you can use a S&H module to send midi cc#s only on the 1/16 or 1/96 clock pulses.
You can also let a LFO be controlled by the G2 Master clock by setting the range to Clk. The LFO can be reset with the ClkGen Actibe output to let it sync to the MidiStart command.
The Midi Out modules look at changes on their inputs, so you don't really have to clock them. They just follow the motion of the control signal on their blue input. The rate is set automatically, whenever there is time to send a midi command on the midi out connector the module will check if there is a change and then send that change. No change, nothing sent.
Midi is able to send about 1000 midi CC# commands a second. If you send only one midi CC# the rate is pretty high, but if you send e.g. twenty different midi CC#s the update rate for each CC# falls down to about 50 times a second, depending on how fast they change. This is the Midi 'cable' limitation, the G2 DSPs can in essence handle much more than this.
By using a S&H that samples changing values before they go into a Midi CC# Out module the update rate is limited and then the G2 is pretty much on time. By letting the Out modules send continuously changing signals bad timing is hardly noticed as everything is continuously evolving. Bad timing could occur when sending more than 20 different CC#s, still, this would be caused by the speed of the midi cable. I send some 20 different CC#s now and then, but never really noticed problems.
So, all in all it works pretty well. |
|
Forum index » Clavia Nord Modular » G2 FAQ
FAQ
Calendar
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
Chat Room
