Home -> Magazines -> Issues -> Articles in this issue -> View
Midi By Example (Part 8) | |
Article from Music Technology, April 1993 |
Still trapped in the MIDI maze? Never fear - Vic Lennard has found another way Out
Sixteen MIDI channels not enough for you? It could be time to find another way Out...
When MIDI was first developed some ten years ago, instruments were generally monotimbral: that is, they could play only one sound at a time from MIDI notes received on a single MIDI channel. So the 16 available MIDI channels could control up to 16 different synths or sound modules. But of course, the technology has developed to such an extent that a single multitimbral sound module may now require all 16 MIDI channels, particularly where such units boast a polyphony of up to 64 notes.
Take a typical live set-up of a synth and a couple of sound modules cabled together as in Figure 1.
Playing keys on the synth sends out note information to both of the modules. But let's say that each of them is 16-part multi-timbral - General MIDI modules, perhaps. The only way this system can operate is with both modules in tandem, responding to the same note information on the same MIDI channels. Also, a Program Change message sent from the synth will switch both modules to the same patch number, so you'll have to carefully organise your sounds if this is not desirable.
Now, what happens if your synth has a pair of independent MIDI Outs? The set-up would be as in Figure 2.
Here, each sound module can be individually addressed from the keyboard and the problem with patch changing no longer exists. Such a synth is likely to support multiple splits so that different zones of the keyboard transmit MIDI information on discrete MIDI channels - a very powerful live system.
Working live with a sequencer/workstation or back in the studio with a sequencer, there's a much more important reason for having independent MIDI Outs. Taking the above example of two 16-part multitimbral sound modules: having one MIDI Out means only being able to access 16 instruments. While this might seem a lot, it doesn't allow you to individually use each sound on both modules.
The reason for having a pair of expanders might be to make use of their different synthesis methods. For instance, one might be of the sample playback type offering 'real' instruments like strings, brass and the like. The other unit may be a standard synth for pads, allowing you to double up sounds to create useful textures. Additionally, being able to automatically access all instruments on a pair of sound modules means you are far less dependent on patch changing.
Figure 3 shows a typical set-up for this; here, one MIDI Out plays the sounds on the synth while the other is used purely for the two sound modules, using the MIDI Thru of the first to connect to the MIDI In of the second.
A second MIDI Out can also be used for the sending of accurate sync information. Obviously, the timing of this kind of data is very important, bearing in mind that it is responsible for keeping two devices locked together - a sequencer and a drum machine, for example. This is shown in Figure 4.
MIDI Out1 transmits the note and performance information to the synth while MIDI Out2 is responsible for sending the MIDI Start, Clock, Continue and Stop commands to the drum machine whose patterns will then play in time with the sequencer. While the speed of MIDI is not usually an issue, a sequencer will often prioritise the transmitted MIDI messages, and MIDI sync commands generally come way down the list. By using the second MIDI Out in this way, you ensure that the playback timing of the drum machine is not compromised.
While generic multiple MIDI Out units are available for the PC and Mac, sequencer software manufacturers for the ST tend to provide dedicated units. These often provide you with more than simply an extra MIDI Out - key (dongle) expanders, SMPTE generators etc. are also included. For most ST sequencers, there are cheap third party options such as 16 Plus from Hands On MIDI Software and ModemMIDI from the UKMA.
How do you know if a sound module is GM compatible? Look for the logo (Figure 5). But be careful: some modules are using the logo without properly conforming to the specification. Check the polyphony - if it can't provide 24 voices, it isn't GM. The result of this will be the audible cutting off of notes.
This is the last part in this series. The first article in this series is:
MIDI By Example
(MT Sep 92)
All parts in this series:
Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6 | Part 7 | Part 8 (Viewing)
Radio Days - Technology On The Air |
MIDI and the Micro |
Good Enough For The Pro? - Thoughts on MIDI's Next Decade |
Talking MIDI (Part 1) |
Dumping Grounds (Part 1) |
Adventures In MIDILand (Part 1) |
MIDI Muting - Sound Workshop |
BeeBMIDI Monitor (Part 1) |
![]() |
The Integration Game - Improving your MIDI Environment (Part 1) |
Wot, No Keyboards? - The Alternative MIDI Controllers Session (Part 1) |
Browse by Topic:
Topic:
Series:
Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6 | Part 7 | Part 8 (Viewing)
Feature by Vic Lennard
mu:zines is the result of thousands of hours of effort, and will require many thousands more going forward to reach our goals of getting all this content online.
If you value this resource, you can support this project - it really helps!
Please note: Our yearly hosting fees are due every March, so monetary donations are especially appreciated to help meet this cost. Thank you for your support!
New issues that have been donated or scanned for us this month.
All donations and support are gratefully appreciated - thank you.
Do you have any of these magazine issues?
If so, and you can donate, lend or scan them to help complete our archive, please get in touch via the Contribute page - thanks!