The Helix Stadium Native plugin is, by default, set to a Helix Stadium/Helix Stadium XL Hardware Compatibility Mode, which incorporates Digital Signal Processing (DSP) management similar to that of the system used on the Helix Stadium hardware devices. That is, each Path 1 and Path 2 in a plugin instance has a maximum processing limit. This limit ensures presets are compatible across the plugin and Stadium hardware devices. Optionally, Hardware Compatibility can be set to “Off” in the Plugin Settings, allowing you to exceed the Stadium hardware minimum and maximum block-type limits in your Helix Stadium Native presets.* Note that disabling Hardware Compatibility allows you to create a preset in a single plugin instance that can place significant CPU demands on your computer system, and the preset will not be compatible on Helix Stadium devices.
*Note: The Helix Stadium Native Intro version does not include the Hardware Compatibility “Off” option. Its presets are always created to be compatible with Helix Stadium/Helix Stadium XL devices.
Dynamic DSP
Since some models require many times more DSP horsepower than others, fewer heavy DSP models can be included in a preset when Helx Stadium Native’s Hardware Compatibility mode is enabled. For most other modeling devices on the market, you are restricted to one amp, one reverb, one delay, etc. With Helix Stadium, we feel it’s important to let you keep adding whatever you want, even if you may eventually run out of DSP for the current preset. Stadium Native’s four paths (Path 1A, 1B, 2A, and 2B) each offer 12 block locations, for a total 48 block capacity.
That said, there are some rules governing the number of certain types of blocks you can add to a preset:
|
Block Type |
Maximum Allowable Block Instances |
|---|---|
|
Amp, Preamp, or Clone |
Any combination, up to four per preset (two per path maximum). |
|
Cab |
Up to eight Cab blocks per preset (four per path maximum). Note that each Cab block can include up to two Cab models, two Cab IRs, or one of each. |
|
Polyphonic (“Poly”) and high DSP type Effects |
Up to two Poly Effect blocks per preset (one per path maximum). These effect models include the Feedbacker (Dynamics), Poly Sustain (Delay), Poly Detune (Modulation), Poly Pitch, Wham, Capo, and 12 String (Pitch/Synth). |
To see which models can be added to the current Path, open the Model List. When Hardware Compatibility mode is enabled, grayed-out items cannot be accommodated and are not selectable.
Tips to Optimize DSP
-
Each of Stadium Native’s two primary Paths (Path 1 and Path 2) utilizes its own independent DSP. If all of your blocks are on Path 1 (or on its split/parallel Paths 1A and 1B), you’re only using half of your preset’s available horsepower! To use two or more amps and more than a handful of effects, expect to use both Paths 1 and 2. An easy way to accomplish this is to set the Path 1 Output block to “Path 2A” to route Path 1 into Path 2 as a contiguous, serial Path. In fact, we’ve created two template presets—Parallel Switch and Parallel Blend—with two Agoura amps in parallel spanning Paths 1 and 2 to optimize DSP, with plenty of room for pre (Path 1) and post (Path 2) effects. See the following Signal Path Routing page for details.
-
Some block types use much more DSP than others, with Amp, Clone, Reverb, and Poly effect blocks being the most DSP-hungry. Cab, EQ, Dynamics, Volume/Pan, and Send/Return blocks use relatively little.
-
Some models may use more DSP than others in the same category. This is especially true with Agoura Amp models.
-
Instead of a parallel Path with two sets of separate Amp and Cab blocks, try adding a single Amp block followed by a Cab block that uses two different Cab models/Cab IRs to provide some substantial tone variations.
-
The stereo version of an Effect model will use approximately twice as much DSP as a mono version of the same model. Typically, you should use mono versions of effects that are placed before an Amp block, since the stereo signal is collapsed to mono when entering an Amp block. And, of course, if you’re only using a mono output from Stadium, there is no need to use stereo models at all in your tones.
-
Some model categories have “Simple” blocks, which use less DSP than others.
-
Instead of toggling between two of the same Amp or Effect blocks (with different settings), use controllers or snapshots to instantly adjust parameters within a single block.