Preparing Patches for Organelle™
•
Try to keep CPU usage under 75%.
Even the most carefully constructed patches
might require additional resources in a performance situation. While only a guideline,
this is a practice that we ourselves endeavor to follow.
NOTE:
Current CPU usage can be viewed from the system information screen (see
chapter three
).
•
Building patches directly on Organelle is possible.
This requires setting up
Organelle as a computer, with a monitor, keyboard, and mouse (see
chapter six
). This
is just as valid as working off your personal computer. As with all workflow decisions,
the choice is yours.
•
Save versions of everything you do.
Especially when making big changes, don’t
simply overwrite the previous version of your patch; keep a working version that you
can go back to. Just in case.
Things Unsaid
In summary, we have covered all the messages that Organelle is either providing to or
expecting from your patch. By equipping your patch to use those remote busses, you are
enabling your patch to be Organelle-friendly and live well in this ecosystem.
But we have not told you how to make a patch. And again, this is by design. Aside from
being well beyond the scope of this document, using Pure Data and creating something
“useful” is truly an example of beauty being in the eye of the beholder.
Looking at the factory patches will give you a sense of certain possibilities, and studying the
Pure Data resources listed at the top of this chapter will school you in general methods of
working. If you do choose “to code,” the path forward is yours. Our only overarching advice
is to build something that you would like use, and then put one foot in front of the other.
Page
!
of
!
40
51