Multi-Instance Editing Overview
Multi-Instance Editing allows a single GUI editor to effectively be shared by many instances of the plug-in, showing data from many instances and allowing parameter changes to be made to any or all instances within the current Edit Group. When using Multi-Instance Edit Groups, parameters on the GUI apply to the Selected Instance, which may or may not be the instance that was opened from the host (i.e. the Host Instance).
Multi-Instance Editing is most convenient when using Breeze together with Precedence, where the Position Display in Precedence will show the current position of all instances within the Edit Group, and simply clicking on any instance shown within the Position Display can change the instance selection. Instance selection in Breeze can be made to follow selections in Precedence using Selection Sync, as explained below. Instance List Panels are also available in Breeze and Precedence and instance selection change be changed in this way was well, even without using Precedence.
For sake of illustration, let’s consider a simple example: you have two tracks, Guitar and Bass, and they are part of the same Edit Group. If you open the Guitar instance from the host mixer, you will see not only the Guitar instance in the Instance List, but also the Bass instance. As a matter of convention, when you open any GUI editor, the Selected Instance will always be initialized to the instance that was opened from the host (i.e. the Host Instance). If you open the Guitar track instance, the Guitar instance will be selected and all parameters on the GUI will belong to the Guitar instance. If you make any edits to any parameter they will apply to the Guitar instance because that is what is currently selected. So far, this is the standard way of working with plug-ins.
If you change the selection from the Guitar Instance to the Bass instance however, the GUI will now display the parameters from the Bass instance even though the Guitar instance is what was opened from the DAW. If you change parameters while the Bass instance is selected, you are editing the Bass instance parameter data, NOT the Guitar instance, even though the Guitar Instance GUI Editor is what was opened from the Host.
The primary workflow of Multi-Instance editing involves using Precedence with its Position Display as a “control center” to manage many instances. This workflow is described in more detail in the Precedence manual.
In absence of Precedence, Multi-Instance editing can also be a simple matter of ergonomics and convenience, since it is generally much faster to change instance selection within a Breeze Edit Group than it is to close the current instance GUI, navigate to the host DAW’s mixer, open another GUI editor for the desired instance, and potentially reposition the GUI window every time you want to make a quick parameter change.
Global-Broadcast also depends on Multi-Instance Edit Groups, and has tremendous value in reverb applications.
To facilitate the learning process of becoming familiar with the concept of Multi-Instance Editing, the Host Instance name (ie the instance the you opened from your DAW host’s mixer) is also displayed on the Info page of the GUI in case you somehow become confused.
Tip: All parameters on the GUI follow the current instance selection. All parameters for any and all members of the Group can change from within a single GUI window simply by changing the Selected Instance. Any instance within the Edit Group can be opened from the DAW mixer, and it can be used to edit ANY or ALL group members.
Tip: An Edit Group may have tens or even hundreds of instances within it. Parameter data for all instances in the group is exceptionally fast to access and extremely simple to edit!
To use Multi-Instance Editing, instances must be part of an Edit Group. Breeze offers 8 edit groups, as well as the ability to disable Multi-Instance Edit Groups and use Breeze in the traditional single independent instance workflow. These modes can be used at the same time: i.e. some instances can be part of an Edit Group while others can continue to be used independently. For simple to medium complexity projects a single Multi-Instance Edit Group may be sufficient for the entire mix. For complex projects multiple Edit Groups are offered to allow users to create different sub-mixes within large projects, where it may be desirable to group similar elements into Edit Groups instead of showing the contents of the full mix within a single Multi-Instance Editor. A few examples include, but are certainly not limited to, the following:
• Modern Scoring and Film, TV, or Game Mixing
• Orchestra Group
• Synth Group
• Ambience and FX Group
• Dialog Group
• Modern Orchestra
• Strings Group
• Brass Group
• Woodwinds Group
• Percussion Group
• Choir Group
• Non-Traditional Element Group
• Electronic Music
• Synths Group
• Drums Group
• Real Instruments & Vocals Group
• FX Group
• Grouping by Linked Reverb o Breeze 2.5 Group
• B2 Group
• Aether Group
• 3rd Party Verb on Send Group
There are many other ways to use Groups. We recommend to start with using only one group to become familiar with the Multi-Instance Editing and Precedence Link workflow first, and then as your needs expand perhaps consider using multiple Edit Groups if and when needed.
When using Precedence Link to establish inter-plugin communication between Precedence and a linked Precedence Aware reverb engine such as Breeze 2.5, it is possible to keep the Multi-Instance Edit Selection synced between Precedence and the reverb. When using this feature, the Precedence GUI may be kept open alongside the reverb GUI, and instance selection for both can be made from the Precedence Position Display. The selection will be automatically changed in the reverb engine when a new selection is made in Precedence. This allows an ultra fast editing workflow that is dramatically more convenient than having to open many instances from the Host. Selection is synched in both directions, so selection changes are possible from the reverb GUI as well, but we find it more convenient to use Precedence as the “command center” for Multi-Instance selection do the instance visualization found in its Position Display. See the Precedence manual for additional details.
Dealing with many instances of a plugin can be tedious historically. Multi-Instance Editing makes it much easier already, but often it would be convenient to be able to change a parameter or two, or an entire preset en-masse for an entire Edit Group. This is what Global Broadcast accomplishes.
Tip: When Global Broadcast is on, any changes made to individual parameters, or even changes to all parameters via preset change are applied not just to the Selected Instance, but also to the entire Edit Group!
Global Broadcast within Breeze is extremely valuable. Breeze establishes a virtual acoustic space, and Precedence positions elements within this space. In this paradigm many instances of the same general Breeze preset are loaded across all tracks. Each instance has built-in variations, but the entire set of many instances remains part of a unified whole. Users establish a relative spatial mix with the space created by Breeze via position information from Precedence, and use Precedence Link to communicate this information to the reverb instances, creating additional per-instance variations in the Breeze instances.
This level of realism is simply not possible with a single shared instance on a Send Buss. It is comparable to the difference between having one impulse response of one exact point in a concert hall versus hundreds taken at many different locations! The first method applies this single impulse response to every instrument in the mix, inevitably conveying that each instrument has originated from the same point with the environment. The second method allows each instrument to occupy its own unique space within the environment. In the case of Precedence and its linked reverb engine, we are not dealing with hundreds of impulse responses however; the variation is infinite, and time varying in an organic manner as well!
Once a relative spatial mix has been established however, it could also be desirable to make global changes to the environment. Perhaps we would like to hear how the mix sounds transported from Boston Hall to an LA Scoring Stage. Global Broadcast allows users to browse reverb presets to find the perfect environment for our mix. The relative spatial positions will remain intact, but the mix will be transported into a new virtual acoustic space! We can change our Hall to a Chamber or anything else imaginable. The environment changes just as easily as if it were a single instance on a send buss, but it is NOT just a single instance we are dealing with. We may have tens or hundreds, each with its own variable position, and its own innate random variations.
Tip: Global Broadcast makes managing many instances just as fast and convenient as managing one instance on a bus!
Tip: Global Broadcast allows you to change the positioning rules and macro aspects of the virtual acoustic environment, while retaining relative positions and automatically introducing variations in each and every instance even if they happen to have the same position.
The Global Broadcast method does not enforce sync to be maintained between Edit Group members. You are free to turn on Global Broadcast, make a preset change, cascading the changes to all instances in the Edit Group, then disable Global Broadcast, and finally make any per-instance adjustments you might like! You will end up with an Edit Group that is mostly similar, but may have some important per-instance variations to further optimize specific tracks with special needs. In the Breeze this could mean slightly adjusting the reverb gain level for specific tracks, or changing the EQ filter for specific tracks, or any other possibility.
Tip: Breeze Alg-Randomize can even be used with Global Broadcast to introduce a new random behavior for all instances in the Edit Group! Even without doing this, there are already innate differences between instances, but these features allow even larger mutations within the Edit Group.