Unify Manual

Your complete reference to PlugInGuru's creative playground!

User Tools

Site Tools


embedded-unify

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
embedded-unify [2020/11/15 15:23] – [New features added in Unify v1.2] shaneembedded-unify [2023/05/08 18:59] (current) – external edit 127.0.0.1
Line 4: Line 4:
 In Unify v1.0.12 and earlier, it was necessary to register at least one of the Unify plug-ins (VST recommended) in Unify's [[scanning|Known plug-ins list]] and use that. As of Unify v1.1.x, however, Unify is now pre-registered as a built-in plug-in, and using this is now the recommended embedding technique. In Unify v1.0.12 and earlier, it was necessary to register at least one of the Unify plug-ins (VST recommended) in Unify's [[scanning|Known plug-ins list]] and use that. As of Unify v1.1.x, however, Unify is now pre-registered as a built-in plug-in, and using this is now the recommended embedding technique.
  
-**As of Unify v1.1.7 (released June 26, 2020), embedded Unify instances no longer allow their Macro knobs to be controlled directly by MIDI CC messages.** +This change leads to some new techniques for working with MIDI and macro parameters in embedded Unify instances: 
-  * To link Macro parameters of embedded Unify instances to the Macro knobs of the primary Unify instance, simply add appropriate links, e.g. in the linked-parameters editor for Macro1, add an entry for //inst/1/plugin/Macro1// and so on. +  [[midibox|MIDIBox]] can be used to play back MIDI CC message sequences. These won't be seen by the macro knobs of the outer Unify, but can be sent to an embedded Unify instance, and will control //its// macro knobs. 
-  * There are some new features to make this easier. See below under "New features in Unify v1.1.7" for details.+  * To link Macro parameters of embedded Unify instances to the Macro knobs of the primary Unify instance, simply add appropriate links, e.g. in the linked-parameters editor for Macro1, add an entry for //inst/1/plugin/Macro1// and so on. There are some new features to make this easier. See below under "New features in Unify v1.1.7" for details.
 ===== Converting patches made using the Unify VST/VST3/AU ===== ===== Converting patches made using the Unify VST/VST3/AU =====
 If you have made patches embedding Unify as VST/VST3/AU, you can continue using them as-is, for as long as you wish. If you have made patches embedding Unify as VST/VST3/AU, you can continue using them as-is, for as long as you wish.
Line 49: Line 49:
  
 ==== Settings view ==== ==== Settings view ====
-In the Settings view, you will find two new checkboxes, as follows: +In the Settings view, you will find three checkboxes next to the label **Embedded Unify**, as follows: 
-  * **Link ALL macro knobs to new instances** (default: checked) When checked, every time you create a new embedded instance of Unify, new parameter links will be created, linking the outer //Macro1// knob to the embedded //Macro1// parameter, //Macro2// to //Macro2//, etc. +  * **Link ALL macro knobs** (default: checked) When checked, every time you create a new embedded instance of Unify, new parameter links will be created, linking the outer //Macro1// knob to the embedded //Macro1// parameter, //Macro2// to //Macro2//, etc. 
-  * **Add Macro links when loading patches** (default: NOT checked) When checked, appropriate Macro links will be created automatically, whenever you load any patch that has embedded Unify instances. If you re-save the patch, those macro links will be saved into the patch, and hence will be there even if you un-check the box and load the patch again.+  * **Add missing Macro links** (default: NOT checked) When checked, appropriate Macro links will be created automatically, whenever you load any patch that has embedded Unify instances. If you re-save the patch, those macro links will be saved into the patch, and hence will be there even if you un-check the box and load the patch again
 +  * **Enable Master Layer** (added in Unify v1.8, default: checked) When checked, the Master Effects layer will be enabled in all patches loaded to embedded Unify instances, whether or not the patch had been saved that way.
  
-If you have several patches to update, you can either use //Add Macro links when loading patches// as just described, or new items on the "ops menu" for the [[realtime-params|Macro Knobs]] view.+If you have several patches to update, you can either use //Add missing Macro links// as just described, or new items on the "ops menu" for the [[realtime-params|Macro Knobs]] view.
  
 ==== Macro Knobs knobs view ==== ==== Macro Knobs knobs view ====
Line 69: Line 70:
 All of this might seem a bit overwhelming, but don't worry. All you need to do is ensure that when you adjust any active Macro knobs in the top-level Unify, the changes propagate downwards when necessary, to produce the intended effect. If you turn a knob and don't hear the effect you expected, check your links; you might have missed one. If you happen to have a few "redundant" links, don't worry; they're harmless. All of this might seem a bit overwhelming, but don't worry. All you need to do is ensure that when you adjust any active Macro knobs in the top-level Unify, the changes propagate downwards when necessary, to produce the intended effect. If you turn a knob and don't hear the effect you expected, check your links; you might have missed one. If you happen to have a few "redundant" links, don't worry; they're harmless.
  
-===== New features added in Unify v1.2 =====+===== "No pitch shift" status (added in Unify v1.2=====
 Unify v1.1.10 introduced the ability to open embedded Unify layers in "no pitch shift" mode (see [[playing-patches#using_the_patch_chooser|Using the Patch Chooser]], which ensures that the [[midibox#controls_relating_to_midi_input_output|MIDIBox Note->Coarse function]] is deactivated. Unify v1.1.10 introduced the ability to open embedded Unify layers in "no pitch shift" mode (see [[playing-patches#using_the_patch_chooser|Using the Patch Chooser]], which ensures that the [[midibox#controls_relating_to_midi_input_output|MIDIBox Note->Coarse function]] is deactivated.
 +
 +In Unify v1.2, each embedded Unify instance //remembers// whether or not it was opened in "no pitch shift" mode. A new "Load patches 'No Pitch Shift'" item is added at the bottom of the main "ops menu" (click the concentric-circles icon at the bottom center of the Unify GUI), like this:
 +
 +{{::unify-ops-menu.png|}}
 +
 +You can check/uncheck the item yourself using the menu. When it is checked, any patches you select using the embedded Unify's own patch browser will be loaded with the "no pitch shift" variation (if applicable). This allows you to, for example, load a drum-groove patch into an embedded Unify layer with "no pitch shift", then open the embedded Unify's GUI and try different groove patches instead, without losing the "no pitch shift" state.
 +
 +**Limitations:** Note the "no pitch shift" variation only affects the "Note->Coarse" setting in //MIDIBox//, so it will have no effect on patches that use e.g. //BlueARP// instead.
 +
 +===== Master Effects bypass (added in Unify 1.3) =====
 +Starting in Unify v1.3.2, the Master Effects layer features a new "whole-layer bypass" button at the left side. Unify will usually activate this automatically for embedded Unify instances, to ensure that any patches you load there will not end up passing through more Master effects than intended.
 +
 +{{::master-bypass-1.png|}}
 +
 +See [[master-bypass|Master Effects layer Bypass]] for details.
  
embedded-unify.1605453821.txt.gz · Last modified: 2023/05/08 18:59 (external edit)