Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
patch-variations [2021/09/03 22:30] – shane | patch-variations [2021/09/16 11:49] – [Patch Variations] shane |
---|
| |
To use the techniques | To use the techniques |
described here, you should be comfortable with creating and editing [[midi-controller-files#about_plain-text_files|plain-text files]]. | described here, you should be comfortable with creating and editing [[midi-controller-files#about_plain-text_files|plain-text files]]. However, the first example includes a link to a //.guru// file you can download and try, even before you understand all the details. |
| |
| **Important Note:** when loading a patch from a library, Unify always expects to find the variations-list file in //that library's own Media folder//. This means, if you re-save a patch into a different library, you will need to copy the original variations-list file into that library's //Media// folder (and you may need to create the folder, if there isn't one already). **This is a limitation in Unify v1.6.x.** It may be fixed in a future update, but this is not guaranteed. |
----- | ----- |
| |
===== Concept of patch variations ===== | ===== Basic Concept ===== |
| |
//Patch variations// were introduced in Unify v1.6.0. Any patch can optionally include a reference to a plain-text "variations" file (kept in the library's //Media// folder), which is simply a list of "variation names", one per line. The newly-added [[param-paths#top-level_paths|top-level parameter]] //variation// can be linked to a macro knob, and simply selects which of the variation names is displayed in white to the right of the patch name. | //Patch variations// were introduced in Unify v1.6.0. Any patch can optionally include a reference to a plain-text "variations" file (kept in the library's //Media// folder), which is simply a list of "variation names", one per line. The newly-added [[param-paths#top-level_paths|top-level parameter]] //variation// can be linked to a macro knob, and simply selects which of the variation names is displayed in white to the right of the patch name. |
{{ :unify_step_curves.zip |}} | {{ :unify_step_curves.zip |}} |
| |
The special "stairstep" curve presets were generated using a [[https://www.python.org/|Python program]], which you can also download here: | This //.guru// file also installs the special "stairstep" curve presets into the correct folder, so they're ready to use in your own patches. |
| |
| These special curves were generated using a [[https://www.python.org/|Python program]], which you can also download here: |
| |
{{ ::generate-step-curves.zip |}} | {{ ::generate-step-curves.zip |}} |
| |
| Both of these downloads are //.zip// files; you will have to unzip them after downloading. |
===== Example 2: Sample maps ===== | ===== Example 2: Sample maps ===== |
Patch variations can also be used in combination with one or more sample-maps in [[guru-sampler|Guru Sampler]], where the parameter //osc1SampleSelect// is linked to the same macro-knob as //variation//, and the names in the variations file correspond one-to-one with the available choices on the sample-select menu in //Guru Sampler//. | Patch variations can also be used in combination with one or more sample-maps in [[guru-sampler|Guru Sampler]], where the parameter //osc1SampleSelect// is linked to the same macro-knob as //variation//, and the names in the variations file correspond one-to-one with the available choices on the sample-select menu in //Guru Sampler//. |