Chapter Two, Understanding
The Three Obstacles - And Two Solutions
Finding the right paradigm:
To solve the compatibility problem once and for all so that you never need to fiddle with the
front panel and never need to cripple someone else’s sound Canvas might require thinking in a
new way. It might not be easy because you will actually be fighting against the grain of thinking
that has already become a precedent in Sound Canvas circles and by others who create
products for Sound Canvas users.
For example, the typical instrument definitions used on MIDI sequencers expect all Sound
Canvas users to use map 0 for native sounds. Using those definition, your software will not
display the correct patch name when you have that patch directly selected on it own map. I feel
like I am fighting the current of the Nile river when I suggest you avoid the permanent use of
map 0. This may remain true for most sequencers even after it becomes an accepted fact that
until we move away from map 0 there can NEVER be upward compatibility.
Although the solution to compatibility in this text is simple, the terminology used to express it has
to cross several barriers. Most importantly there is a terminology barrier and the sequencer
bank switching barrier.
Terminology Barrier
Roland likes to use terminology that differs from standard MIDI terminology. Each sequencer
used by SCUG members has its own terminology. This gets really confusing when we all use the
same terms but mean different things.
This chapter runs deeper into definitions of terminology as used inside this text. If you feel you
have a grip on what you need to do, skip to chapter three. However, if you get confused there,
then return to this chapter. Depending on what sequencer you use and what other sound
modules you may have used, certain terms can have a completely different meaning.
Bank Switching Barrier
Not all sequencers work the same way. Some sequencers require the use of bank switching
methods where you can enter bank numbers but not controller values. Other sequencers require
you to enter values for controller #0 and controller #32 and have no awareness of “methods.”
Those sequencers and those who use them live in two different worlds. The terminology and
approaches to our simple solution are completely different.
If your sequencer uses methods to change banks you might not have a clue yet how to directly
address the three different maps. You may have noticed that every value for controller #0 or
controller #32 you enter into your sequence is completely ignored and has no bearing on what
11
Kommentare zu diesen Handbüchern