Using the A/D input as a means of showing the Envelope Follower is great - and I'm happy to see the content. One of my favorite "tricks" of utilizing the envelope follower, however, is to use internal sounds (PARTs) routed as inputs to the Envelope Follower. Usually, the "trick" I use is to route the PART -only- to the Envelope follower and not to any output - so the PART is serving only as a stimulus to an envelope follower. At the end, the envelope follower generates values 0-127 - so I can use a single PART to generate any value 0-127 by changing what that PART does.

Maybe I only want certain keys to generate a value. This would be difficult to manage with motion control (to map certain keys of the keyboard or key ranges to "map" to a curve - while others do not). This can be done as I would make only certain keys output a sound and some not (which is easy to do with a drum PART).

When I think of different ways to setup a "hidden" (silent) PART to just work to stimulate an Envelope follower, it usually provides a means of doing something that otherwise could not be done using the default controllers.

Then I use user curves (step) to allow to give a "range" of envelope follower values so I can filter out some of the flutter that may happen although the flutter may be put to good use a times.

PARTs do not, in motion sequence, have much of a chance to interact with each other. However, the output of one PART can link to the envelope follower input of another PART which gives yet another dimension of control. Most of the control paradigm presented thus far has been from the top down (super knob, to system-level assignable knobs, to PART level assignable knobs - or A/D input to envelope followers of each PART). That's great - but PART-to-PART interaction using envelope follower is a great option as well.

Thanks for providing some of the introductory material (buiscuits) which I'm sure will set the stage for the more advanced material down the road (gravy).