![background image](http://html1.mh-extra.com/html/critter-and-guitari/organelle/organelle_user-manual_2686196039.webp)
Preparing Patches for Organelle™
objects. As with most facets of Organelle, the choice of what to use — and what to ignore
— is completely yours.
Overriding Standard MIDI Behavior
We just finished saying that you can generally change how Organelle works so here is the
proof. In case you want to disable the MIDI messages used by Organelle, we have made it
easy to do so. (If you are uncertain why you would want to do this, feel free to ignore this
section.)
There are two additional data streams for asking Organelle to do this.
•
[send midiOutGate]
– Outgoing message to Organelle; a boolean value of either
0
(zero) for disabling normal MIDI out messages, or
1
for restoring them
•
[send midiInGate]
– Outgoing message to Organelle; a boolean value of either
0
(zero) for disabling normal MIDI in messages, or
1
for restoring them
By disabling either (or both) of these functions, you are canceling the standard MIDI
messages used by Organelle (see
chapter three
). The assumption is that your patch will
then provide its own methods for dealing with MIDI. But again, it’s your prerogative.
A Few Tips on Patch-building
Here are a few thoughts and suggested guidelines for preparing and/or making Pure Data
patches for Organelle.
•
Build the simple version first.
Particularly if this kind of programming is new to you,
the best thing you can do is start by building something simple that works. And then
slowly expand it, adding or changing only one function at a time.
•
Break your idea into pieces.
If I were, for example, building a basic playback
sequencer, I would break this down into three conceptual pieces: a clock source (like a
metronome), a data structure (for storing the notes I want played back), and a labeling
function (to convert the clock source’s nameless “ticks” into the “1, 2, 3…” etc. that
would tell the data structure which address to playback at this moment). Some of
these pieces might consist of single objects. Others would require small programming
blocks.
Page
!
of
!
39
51