20.08.2013 Views

INTRODUCTION TO SYNTHESIZERS - hol.gr

INTRODUCTION TO SYNTHESIZERS - hol.gr

INTRODUCTION TO SYNTHESIZERS - hol.gr

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

The slave synthesizer will now also "pass", or "echo" the signal further into the next connected synthesizer via<br />

its MIDI Thru jack. The signal will thus travel all the way to the end of the MIDI chain and all connected<br />

synthesizers will play the same tone.<br />

When you release the key, another MIDI message is created:<br />

Release the middle C key.<br />

Until this message arrives, the slave synthesizer will keep on playing the note.<br />

Here's a little experiment for you to try: depress a key on the master keyboard, and then unplug the MIDI cable<br />

before you release the key! What happens?<br />

You guessed it - the release command will never arrive to the slave synthesizer, resulting in an endlessly<br />

playing tone. This dreaded syndrome is called the "MIDI drone" - pretty scary in a live gig situation! Sometimes<br />

the only way to shut off the orphaned tone is to turn the slave synthesizer off and on again.<br />

Not just note events, but almost every event that you create on a keyboard will be transmitted like this - pitch<br />

bend, after-touch or pro<strong>gr</strong>am change events.<br />

Most MIDI commands, such as the Note On commands we looked at so far, can be understood by any<br />

synthesizer, regardless of model. You can for instance control a Korg X3 synthesizer from a Kawai K4<br />

synthesizer. But there are also some MIDI commands which are specific for a certain type of synthesizer. These<br />

describe the setting of each individual parameter that creates a patch for that synthesizer model. These<br />

commands are called "System Exclusive" and are used by synthesizer pro<strong>gr</strong>am editor software.<br />

It is impossible to give all the details about every MIDI command in this limited space, so we will not go further<br />

into the technical aspects of MIDI.<br />

General MIDI<br />

The original MIDI standard has some major limitations. We have already bumped into one of them: a MIDI<br />

signal doesn't tell us anything about which instrument sound that is supposed to play a specific note.<br />

For example, if the composer had selected patch number 5 for channel 1, intending this to be a piano sound, but<br />

the synthesizer playing the MIDI data had a tuba sound mapped to patch number 5, then the notes intended for<br />

the piano would be played by the tuba - even though this synthesizer may have an excellent piano sound<br />

available at some other patch number.<br />

To get around this problem, the General MIDI (GM) standard was created. This standard assigns certain<br />

memory locations to different families of sounds. Piano sounds are for instance assigned to memory banks 1 - 8,<br />

chromatic percussion to 9 - 16, organ-type sounds to 17 - 24 and so on. By using this standard, you can be<br />

assured that your string ensemble parts will be played back by a string ensemble sound and not by the<br />

14

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!