You’re probably familiar with Studio One’s Micro Edit view, where you can expand/collapse an effect in the Insert Device Rack. However, Studio One 6 extends this ability to third-party plug-ins. You can treat the Insert Device Rack as your plug-in GUI, and tweak or write automation for parameters without having to open a plug-in’s interface. The Micro Edit view is ideal for quick tweaks, but also, for effects that interact with each other, like EQ and compression. Instead of having to bounce back and forth between two different plug-in UIs, all the necessary parameters are laid out in front of you.

Fig. 1 shows an example of using a Micro Edit view in the master bus. The processors are Waves’ UM226 stereo-to-5.1 surround upmix plug-in, followed the IK Multimedia’s Stealth Limiter as a post-master fader effect. Although the UM226 is designed to synthesize surround, I also use it as a “secret weapon” to give more of an immersive feel, and sense of space, to stereo mixes. Its UI is relatively large, so this lets me tweak it while doing a mix with other plug-ins open. Micro Edit view lets you choose the parameters you want to include from third-party plug-ins. The ones shown are the ones I edit most often.

You can choose as many or as few parameters as you want, and all of them are automatable. However, also note that the standard automation options don’t have to overlap with these parameters. For example, I use standard automation for switched functions that might only be needed to change once or twice during a song. There’s no need to have them take up space in the Micro Edit view.

Serious Micro Edit Automation

Opening the view in the Insert Device Rack limits the fader length. That’s okay for tweaking parameters, but for automation, it’s better to have a longer fader. Version 6’s Channel Overview takes care of that (fig. 2).

Assigning Parameters

With PreSonus plug-ins, Micro Edit View parameters are pre-assigned to the most-used functions. With third-party effects, you select the Micro Edit view parameters, similarly to how you choose automation parameters.

Right-click on the effect name in the Insert Device rack, and choose Setup Micro Edit Parameters. Click on the parameters you want to add in the right pane, and choose Add. Now the parameters will be in the left pane, and visible as Micro Edit view parameters.

Fig. 3 shows how this can save a huge amount of screen real estate when mixing. The Ampeg SVT suite bass plug-in’s UI takes up a lot of space. So, I assigned all the parameters for the amp being used to Micro View parameters. Now tweaking the parameters simply requires expanding the Micro Edit view, and collapsing it again when done (expanding and collapsing are both one-click operations).

This is the kind of feature that may not seem like much of a big deal—until you start using it. Micro Edit view makes for a less cluttered, more compact, and visually streamlined mixing experience.

Heads-up: Version 1.3 of The Huge Book of Studio One Tips and Tricks is now available! This 637-page book with 230 innovative tips is a free update to owners of previous versions ($19.95 to new buyers). Download the update from your PreSonus or Sweetwater account the same way you downloaded your previous version. For more information, check out the series of Studio One eBooks. Please note: version 1.3 does not cover the new features in version 6, although there will be a free update in the future. If you have questions about the tips, suggestions for future updates, or want news about the next version, please visit the dedicated support forum.

Quantizing audio works best with short, percussive sounds—like drums. Rhythm guitar is more of a challenge, because the attacks aren’t always defined well, and volume fluctuations can add spurious transients as a chord decays. I know quite a few guitarists who set up their quantize parameters, hit “Apply,” and then wonder why the guitar part sounds worse, not better. So, they hit “Undo” and assume quantizing doesn’t work well for guitar. But it can, if you know the two tips in this week’s blog post.

To start the quantization process, select the event, open it in the Edit view, right-click on it, and choose Detect Transients. Do not choose Quantize, because we’ll need to edit some of the transient markers prior to quantizing. Then open the Audio Bend panel. The default transient detection is Standard analysis, with a Threshold of 80% (fig. 1). These are good initial settings for guitar.

Tip #1: First, Do No Harm

With complex chords and lots of strings vibrating, Studio One may dutifully identify each attack with a transient marker. However, when listening, you might not hear any attacks in those places. Applying quantization to places that don’t need to be quantized can degrade the sound.

In fig. 2, after playing back the part, it didn’t seem the markers colored red (top view) needed to be there—only the marker between the two chord attacks correlated to an audible transient.

Quantizing with all the markers in place created awkwardly stretched audio (middle view). After removing the markers in red and quantizing (bottom view), the quantization occurred exactly as desired.

Bottom line: If a transient marker doesn’t correlate to a transient you can hear, you’re probably better off deleting it. Sometimes, lowering the Threshold percentage in the Audio Bend panel takes care of removing unneeded markers for the entire Event.

Tip #2: Simplify Double Attacks

This is a big problem with rhythm guitar, because it’s physically impossible to hit all 6 strings at the same time. In fig. 3’s top view, note the doubled attack just before 3.4 (one of the attacks is colored red for clarity).

The middle view applies quantization. Studio One has dutifully shifted the two transients to 16^th notes, as instructed by the quantization parameters. But this overstretches the audio between the two transients, and doesn’t sound good.

The bottom view shows the audio after removing the transient shown in red in the top view, and then applying quantization. Studio One has shifted the remaining attack transient to the nearest 16^th note, which is what we want.

Here’s another tip that relates to fig. 3. Note how the quantized transients at 3.4 and 4 seem a little late, like they missed the first part of the attack. However, I’ve found that if Studio One doesn’t have to deal with double attacks, it makes good judgment calls about where to define the chord’s attack. I’ve tried placing the transient closer to where the attack starts and quantizing, but most of the time, the chord then sounds a little late. Trust the force.

In any case, a little manual tweaking prior to quantization can make the difference between a natural-sounding part that doesn’t seem quantized, and quantized audio with unwanted glitches. I never quantize a rhythm guitar part without looking over the transients first, and making sure they don’t exhibit any of the issues described here.

For me, the gold standard for sound isn’t what comes out a studio, but live music. One of the reasons is that mono sound does not exist in an acoustic environment—it’s always interacting with the acoustic environment.

Sure, we can add reverb to give a mono instrument like electric guitar a static position in a stereo field. However, that will always require some kind of time-based manipulation. For a recent song project, I wanted a background guitar part to have motion within a stereo field—but without using any kind of delay, reverb, panning, or EQ. In other words: dry, electric, mono-output guitar with a stereo image. Impossible? Let’s find out.

The Track Setup

The way this works is so simple I’m surprised I never figured it out before. Fig. 1 shows the track layout.  The guitar (with added chorus, as required by the song) pans full left, and has two sends. One send provides the guitar’s audio to a bus. The other send controls the sidechain of a Compressor inserted in the bus. The bus is panned full right.

As the Compressor’s level changes, there’s a sense of motion as the dynamics and levels in the left and right channels change. Even better, these changes are tied to the instrument’s dynamics. This makes for a more natural effect.

This audio example plays the guitar by itself, panned to center, and going through the PreSonus chorus.

Now let’s hear the magic stereo effect. Although it’s most obvious on headphones, you’ll hear the effect on speakers as well.

The final audio example plays it in context with the mix. It adds a sense of animation to the guitar you can’t get in any other way. I also included this example because the drums are following the chord track. It has nothing to do with this tip, but I love the cool melodic quality it adds.

Compressor Settings

The Compressor settings are crucial. The ones shown in fig. 2 are a good place to start.

Adjust the settings by panning the source track full left. Increase the processed track’s level until both channels are at about the same level. Experiment with the Compressor’s Threshold to find the sweet spot between the compressor having no effect, or having too much of an effect. The Release can also affect this—too short or too long a release neuters the effect.  You’ll likely have to readjust the processed channel’s level quite a bit as you zero in on the ideal settings.

With 15 ms Attack, both channels have their attacks hit at the same time and with the same intensity. So, the attack sound appears in the center, has the advantage of center-channel buildup, and helps anchor the part. As the audio decays and the channels are more dissimilar, the audio “wanders” more in the stereo field.

This technique is also great with background vocals. I didn’t use it in this song because there was so much motion going on overall I wanted the background vocals to be a constant. However I’ve used this technique with other songs, and it’s very effective—especially if you have multiple tracks of background vocals, and you apply individual magic stereo processing to each one.