|
|
Question about Drum Kit.qtz sample composition I am trying to find a description for "bouncy" a macro patch in this composition. This patch can be found under: [ Any of the top level Sound Pad Patches ] --> [Bounce MacroPatch] --> [/bouncy] I am trying to learn more about this patch as I educate myself on QC, but I can not find out where it lives. It is not in my Library yet it is colored like a standard QC Patch. It's description says Custom, but I can't find it with the other Custom Patches in the library. Any information / leads you can provide would be greatly appreciated. I feel like I am missing some basic atom of QC understanding in this question so if you can clear up my misunderstanding I would be much obliged! Cheer,s
|
It's a macro embedded in the composition. It doesn't actually get installed elsewhere.
Thanks for the quick response!
is it possible to see how it is working it's magic? e.g. the code. Or is this like a compiled Obj-C binary that is embedded in the composition? Can you also point me to a term to direct my reading of the literature for this feature?
( Apologies because my terms of art are probably woefully inaccurate. )
thanks in advance...
hmm... is this macro and example of a Virtual Macro? If so is there anyway to inspect the sub patches in a Virtual Macro?
Momentum Scrolling has the same functionality as bouncy and is possible to drill inside of. The Bouncy macro is just a feedback patch with an inertia i believe.
yup, momentum scroller demystifies the (or an ) implementation. Thanks!
To see what's actually going on in the composition, hold down the option key while browsing the save menu. There should be an option to "save flattened as" (or similiar).
That will take the virtual patch constructs and convert them into live editable patches.
Virtual Patches are pretty useful and provide you with a way of working on a composition and only updating parts, and it will update across every instance it's used in the composition.
If the Graphics folder doesn't have the actual virtual patch "qtz", it still has references to the patch organization inside the qtz file that it uses to put it back together.