Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
patch-variations [2021/09/03 22:40] – [Example downloads] shane | patch-variations [2022/02/08 20:12] – [Basic Concept] 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]]. However, the first example includes a link to a //.guru// file you can download and try, even before you understand all the details. | 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. |
----- | ----- |
| |
| |
//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. |
| |
| You select the variations file for a patch (if any) when saving the patch. As of Unify v1.6.0, the patch-save dialog includes a "Variations" section (which was expanded in v1.8) as shown below: |
| |
| {{::variations-0.png|}} |
| |
| To select (or change) the referenced variations file, click the //Variations// button to select the variations file you created from a pop-up menu: |
| * The first item allows you to //Clear// the variations file selection (if you decide you don't want to use one) |
| * After this, you will see a list of all //.txt// files in your library's //Media// folder, from which you can select. |
| * If you hold down Option/ALT when clicking the button, there will also be an //Open...// item near the top. This will pop pop up a standard file-open dialog, so you can navigate to any location to find the //.txt// file you want. //Note this will make your patch non-portable to other machines.// |
| |
| |
===== Example 1: Song sections ===== | ===== Example 1: Song sections ===== |
{{ :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 |}} |