Drum Slicing Tip - How To Simulate Beat Detectives Trigger Pad Setting In Studio One

One of the biggest questions I get from former / current Pro Tools users with respect to Drum Slicing in Studio One, would be "Is there an equivalent to the 'Trigger Pad' setting when using the Slicing mode for quantizing Multi-track Drums?"

The short answer is no, BUT - I have come up with a simple workaround that I have begun using and just thought I would share it for those who may be interested. :)

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

How To Render Multiple Event FX In PreSonus Studio One

I love using Event FX in Studio One. Whether it’s a simple EQ change that needs to be applied across just one phrase - or working with tools such as Melodyne, Revoice Pro, and VocAlign - Event FX give user’s a way to quickly apply processing to specific Audio Events as needed.

That being said, I think there’s still something to be said about committing to a decision and rendering specific processing once you are happy. This of course leads me back to why I love Event FX so much, because a user is able to “restore” just as easy as Render.

But have you ever found yourself in a situation where you had multiple Audio Events - say, a vocal track for example, and you wanted to select ALL the Audio Events on the track, and Render ALL of the Event FX at the same time?

In this video I demonstrate a few different methods that can be used to Render Event FX across multiple Audio Events in PreSonus Studio One.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Processing and Converting Samples Using The PreSonus Audio Batch Converter

Working in a DAW such as Studio One gives users an enormous amount of flexibility and control over audio. But having said that, there are cases where someone may need to achieve a specific workflow that would be better off being done in a separate application. A great example of this would be when needing to convert or process a large amount of audio files.

In the case of working with multiple audio files, It’s often preferable to work with the actual files on a 1:1 basis vs having them laid out on a single track.

That being said, Studio does have various different options for converting, and processing multiple files, but its not quite the same as a stand alone application that’s specifically designed to batch process files.

If we take a few basic examples like increasing, or decreasing the gain of multiple files, or potentially normalizing to a specific loudness value, as well as processing them through a custom FX Chain - this becomes evident. In addition, there’s also the fie type to take into account. What happens if you need to export a specific format?

Studio One’s export Mixdown options do offer quite a few choices, but they don’t necessarily work well for processing the actual audio events (the files). They are designed to render an actual “Mixdown” of multiple files based on a specific duration of time.

We have some basic control over what types of files are rendered by adjusting the sample rate and bit depth of our song when using drag & drop workflows with Audio Events to the Studio One browser - but again, still not quite the same thing.

This is where an audio batch Converter comes in really handy. And it’s design factor is perfectly fit for purpose for the above tasks. :)

In this video I demonstrate how to use the PreSonus Audio Batch Converter to Process and Convert Samples in PreSonus Studio One 4.5 and above.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Studio One 4.5 - Activate Previous and Next Layer Key Commands

No need for a drawn out written explanation on this one - Here’s a simple one that some of you may find useful. :)

I love it when new Key Commands are added, especially when it's something I use. In this video, I demonstrate the Activate Previous / Next Layer Key Commands that were added in Studio One 4.5 - more specifically what they do, and when one might consider using them.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Exploring The Music Creation Macro Toolbar In Studio One 4.5 - Chord Up and Chord Down

At the time that I am writing this article, we have just seen a major update to Studio One (being Version 4.5) As I am primarily an “Audio Guy” - I tend to take a bit of time to fully explore new MIDI related features in Studio One. But one thing is for certain, is that I always find that with each update (especially the bigger one’s) I always find a handful of features that seem to resonate with the way I like to work.

One thing to point out is that we now have 2 new Macro Toolbar’s that specially have to do with working with MIDI. They are Music Editing, and Music Creation.

Needless to say, I've been exploring the both of them, and in the above video, I demonstrate the Chord Up & Chord Down Macro Button's. More specifically, what they do, and when you might consider using them.

Also worth noting that I plan to do some content on specific features in both of these Toolbar’s that I find useful, with respect to how they can be incorporated into one’s workflow. But in the meantime, Here are a few other Video’s from my good friend Lukas that showcase some of the New MIDI Macro’s in action.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Hidden Gems In Studio One 4.5

New Feature’s and improvement's on existing feature's are always appreciated in an update - but sometimes it’s the little miscellaneous improvements that "squeeze through the cracks" that can really make a huge difference in one’s workflow.

In this video, I take a look at a few of the “not so obvious” features that were added in PreSonus Studio One Version 4.5.

Global Automation View vs Track Based Automation View In PreSonus Studio One

If you’ve migrated over from a different DAW such as Pro Tools or Logic Pro - there’s a good chanced you may be accustomed to working with Automation in a certain way. The great news is that Studio One is really flexible in terms of how it allows users to view (and edit) their automation.

In addition to creating weekly content here on this site, and working my day job as a Producer, Mixer, Engineer - I also do some training clinics for Studio One from time to time.

In the audience is usually a mix of people who have used either Pro Tools or Logic Pro - and each “group” of people will always ask me to explain how Studio One handles Automation views in general. So I thought this might make a good video.

In this video I demonstrate the basic differences and approaches for using a Global Automation View vs a Track based Automation view when working in PreSonus Studio One.

Working With Musicloop's In PreSonus Studio One

The Musicloop File Format In Studio One

When I first began to dip my toe’s in the ‘Studio One’ water’s - One of the first things I noticed when scrolling through the included content in the Browser was Musicloop’s. My first initial thought was - “oh, ok - these are MIDI loops” But they are actually so much deeper than that. Because the minute you drag and drop a Musicloop File to your timeline, you’ll note that a Virtual Instrument get’s loaded, the Preset used to create the Musicloop is loaded, and in addition, any plug-ins used to help create the “sound” of the loop get loaded as well.

In addition, you may also note that when selecting a Musicloop from within the Broswer, Studio One also has the ability to play an Audio Preview of the Musicloop without having to load the Instrument and FX Chain. This of course can also be auditioned at the BPM of your current Song in the case where the Tempo is different.

More Than Meets The Eye

The reason for this is because Musicloops are actually an encapsulated file format that contains multiple pieces of information under the hood so to speak. For example, if a user wanted to use the Musicloop in it’s entirety - they could simply drag it in, and everything need to re-constitute that “sound” would load. Or perhap’s, they just want the Note Data (MIDI) from that file, so that they could trigger another Virtual Instrument in their current song. Or maybe you just want to drag in a consolidated audio file of the Musicloop into your current song - again, entirely doable. Lastly, let’s say that you really like the FX Chain / plug-in’s used in a Musicloop - yep, that’s accessible too.

View fullsize

Right Clicking a Musicloop in the browser and clicking “Show Package Contents”

A Slight Refresh - Musicloops and Pattern Parts

It’s also worth mentioning that something not shown in the video, is that as of the launch of Studio One Version 4 - Musicloop’s got an update. For example, not only is it possible to create Musicloops from instrument Parts, (AKA MIDI Regions/Events) but we can also do the same with Patterns! So take a moment to think about how powerful this aspect can be… As you know, Patterns, can hold Multiple variations, all contained within a single Pattern. So essentially a simple Drag & Drop has the ability to load a preset, and FX Chain, a Pattern with Variations, and in addition - in the cases where you’re working with Virtual Instruments that support Multi-Out configurations (ie: Impact XT), we can also have Custom Named channels.

View fullsize

Take a look at how Musicloops can work with Patterns! It includes, it’s an incredibly powerful tool - all this information is contained in ONE FILE.

In the video I demonstrate the basic's of working with Musicloop's in PreSonus Studio One. More specifically - what they are, what's included in the Musicloop file format, and how they can be used in productions.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Working With Instrument+FX Presets In PreSonus Studio One

Working With Presets

Working with presets is a great way to speed up the creative process and enhance your workflow when working in the studio. The obvious reason being that “some” of the heavy lifting is already done, and essentially there’s no need to start from Ground Zero. A simple analogy that comes to mind would be doing some prep work before cooking. Having everything “ready to go” makes the whole process go a lot smoother.

My guess is that many of you are already doing this, and have your favourite plug-ins set up with a handful of useful presets that can act as a great “starting point” to build upon. But this doesn’t just apply to plug-ins.. Having some basic Instrument’s that are set up and ready to go is also extremely useful. But in this case, we not only have to consider the preset within the V.I. - but also any additional FX processing that we’d like to add in our DAW.

Working With Virtual Instrument Presets

One question that I get asked a lot by colleagues and some of my viewers is “what’s the difference between Storing/Exporting a Preset vs Storing/Exporting an Instrument+FX Preset?”

Well - Here’s the simple answer. Most Virtual Instruments offer built in effects such as EQ, Reverb, and Delay. So these would obviously be recalled when storing a preset. But in certain cases, it may be preferable to utilize additional plug-ins and FX chains. An example of this would be using either 3rd Party plug-ins, or Native Studio One plug-ins for the above tasks.

Furthermore, if we take a look at Multi-Out V.I.’s then there are other aspects to take into consideration as well, such as the multi-Out routing, Channel names, etc.

In this regard, using Instrument+FX Preset’s can REALLY come in handy.

In this video I demonstrate how (and why) to work with Instrument+FX Presets in PreSonus Studio One. More specifically, how they differ from using traditional Presets.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Mixing With The CTC-1 Pro Console Shaper In PreSonus Studio One

Mixing In The Box

Mixing in a DAW can be both a blessing and a curse. On one hand, we have pristine digital audio, with no noise, non-linear artifacts, or colour added to our tracks. On the other hand - well… we have pristine digital audio, with no noise, non-linear artifacts, or colour added to our tracks. All kidding aside, the bottom line is that sometimes things can be so clean - that they begin to lack a certain character. I might also add that there is such thing as “too clean”.

Hands On Control

But first, let me set the record straight - I love mixing in a DAW. That being said, I think it’s worth mentioning that I mix using a Faderport 16 and a Console 1 - with a handful of my favourite plug-ins. Both Native (Studio One) and 3rd Party. In the end, I love the feeling of ‘grabbing faders’ and massaging things into place. Actually to be honest I didn’t realize how much I missed it until I fully embraced the Faderport 16 into my workflow and got off the mouse all together. Quite simply, I find that my mix comes together in a much different way then it does if I’m just moving faders with a mouse.

Injecting Some Character

Having said that, I will also add that I really love using tools that give me a certain “colour” or vibe that I can impart upon my tracks in their digital world. As mentioned, I use a Console 1 by Softube - and this is a great place to start. But it’s not the only option. In fact, I will often use the Console 1 in addition to using the CTC-1 Pro Console Shaper (made by PreSonus).

The purpose of this article is not to explain everything there is to know about Mix FX - or how they work, but more specifically, just going over how I will typically use the CTC-1 in a mix.

Essentially, PreSonus changed the way we can approach Mixing in a modern-day DAW with Mix FX Plug-ins when they were released in Version 3.2. In this video I demonstrate my basic workflow when mixing using the CTC-1 Pro Console Shaper in PreSonus Studio One.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Studio One Quick Tip - Removing Plug-Ins & Sends By Click + Dragging

Today’s video is a super simple tip! If you've ever wanted a quick and easy way to remove plug-ins and sends from your Studio One Song (besides Right Clicking and choosing "Remove") - then this video might be of use.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Studio One Quick Tip - Using 'Create Ranges On Tracks' To Simplify Automation

Any time I'm doing Studio One training clinics or seminars - I always get stopped by someone whenever I use one particular shortcut in Studio One. So I figured it would be worth covering this feature in detail. In this video I demonstrate the 'Select Ranges On Tracks' function in PreSonus Studio One. More specifically what it does, and how it can be used to simplify editing automation when working.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Working With VCA's In PreSonus Studio One - Part 2 - VCA Automation Demystified

One of the biggest feature requests in Studio One (especially from former Pro Tools users) was VCA Faders. Having said that - Studio One added VCA's in Version 3.

I find that it’s kind of tough to explain to people exactly why mixing with VCA’s is such a killer way to work. The usual responses are something along the lines of “Well how is that different then creating a group?” or “Isn’t that that same as creating a BUS Channel for selected tracks?”

My answer is always the same. Once you fully understand (and start using) VCA’s - it’s hard to imagine NOT having them. So with that being said, I wanted to do a 2 part series that would (hopefully) get people accustomed to using VCA’s and explain some of the advantages in terms of incorporating them into one’s workflow.

Before I go any further - If you haven’t already seen the first video - You can watch Part 1 by clicking here.

In this 2nd video of a 2 part series, I demonstrate how to work with VCA's with respect to automation. More specifically, how to render VCA Automation into source tracks - as well as how to merge VCA Automation (static offsets) when needed.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Working With VCA's In PreSonus Studio One - Part 1 - VCA Basics and Setup

One of the biggest feature requests in Studio One (especially from former Pro Tools users) was VCA Faders. Having said that - Studio One added VCA's in Version 3.

I find that it’s kind of tough to explain to people exactly why mixing with VCA’s is such a killer way to work. The usual responses are something along the lines of “Well how is that different then creating a group?” or “Isn’t that that same as creating a BUS Channel for selected tracks?”

My answer is always the same. Once you fully understand (and start using) VCA’s - it’s hard to imagine NOT having them. So with that being said, I wanted to do a 2 part series that would (hopefully) get people accustomed to using VCA’s and explain some of the advantages in terms of incorporating them into one’s workflow.

In this 1st video of a 2 part series, I demonstrate the basics of VCA's - more specifically how to set them up, what they do, and why they're so incredibly useful.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Workflow Tip - Using Reference Tracks In PreSonus Studio One - Routing and Preferences

Using Reference Tracks

Using Reference Tracks is a great way to maintain objectivity when mixing - but it can also be a huge pain unless your routing is set up to accommodate. Furthermore, unless you’re using a Control Surface of some sort such as the Faderport 8 or 16 - attempting to solo one track whilst un-soloing another with a mouse at the same time is a dead end street..

So if we take a look at the 2 above issues, it’s safe to say that even though this concept is a rather simple one. ie: “I want to reference SONG A while I’m mixing SONG B” - It requires a bit of thought to put together a workflow that would allow references to be used. But first, a few more points.

Taking Loudness Into Account

It’s safe to say that a good benchmark to aim for is that of a commercially released track. That being said, if you’re planning on using a track that’s sitting on the current charts - it will most likely have been mastered and have that processing “printed” into the track. This leads to another issue.

Avoiding Double Processing

This is something I’ve spoken about before, but essentially - If you DO have a reference track in your mixing template, and it’s routed directly to your Main Outs, then there is the possibility of double processing your “already mastered” reference track.

What do I mean by this? Well, let’s say that you’ve got a great mix going, and perhaps you’ve got some Mix Bus Processing happening on the Main Outs. (something like iZotope Ozone). In order to get an accurate A/B comparison between your reference track, and your mix, you’d have to first bypass the plug-ins on your Main Outs, and solo your reference track (hopefully after adjusting the fader to compensate for the difference in level if there is any). Furthermore, you’d also want to be able to go back to listening to YOUR mix with the processing on the main outs. Back & Forth, as needed.

In addition, the ears can adjust to a Tonal Balance rather quickly, so in my personal opinion, being able to quickly toggle between your mix and your reference track is imperative to utilizing reference tracks properly. If it takes you 5-10 seconds to go through the A/B process - this isn’t really an efficient approach. Also, there is nothing more evident then the instantaneous epiphany of realizing you’re off the mark.

The Solution

Now that we’ve spoken about the problem, let’s talk about a possible solution that I personally use. Well, it involves some simple routing within your Studio One Song & enabling a preference within Studio One that can help make this process go a little smoother.

In this video, I demonstrate a workflow that can be used to smoothly incorporate using reference tracks when mixing in Studio One.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Studio One Quick Tip - How To Edit Adjacent MIDI Notes (Legato Phrases)

Not every tip needs a long explanation. :) This one is both extremely simple AND extremely useful. Have you ever found yourself in the situation where you needed to move the ending of one MIDI note and the beginning of another that were “butted up” against each other?

In this video I demonstrate how to edit adjacent MIDI Notes (AKA Legato phrases) in PreSonus Studio One - essentially allowing a user to move the beginning and ending position of 2 MIDI notes at the same time.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

How To Export Raw Audio Files (Regions) In PreSonus Studio One

If you’re collaborating with other engineer’s, producer’s, songwriter’s, or studio’s - then there’s a good chance that you’ve been asked to deliver “RAW Audio Files” (aka regions) before. If you haven’t - then my guess is that you will be eventually. :)

First off, let’s take a moment to talk about what this term means.. Well, essentially we can think of Raw Audio Files, as the actual files that are created when recording to your hard drive. Another term for RAW files could also be “un-processed” but in my personal experience, the term RAW is used more often. In fact If I had to narrow it down even further, I’d say “Raw Audio Files / Regions Consolidated from Bar 1” is the phrase I’ve heard the most.

Regardless of whether you are recording a vocal, a kick drum, or an acoustic guitar - whatever source is being recorded through the preamp (after it has passed through the A > D Converters) INTO your DAW would be the raw audio. It’s also important to note that the actual gain that the files have been recorded at will have been determined by your preamp’s gain settings, and the level at which you recorded them. So any fader levels and panning done within the console / mixer of your DAW - would not have any bearing on the levels of the files.

There are certain cases where having access to the RAW audio files (vs exported stems) may be preferable, but without getting into too much detail, the main reason would be to have maximum flexibility/control in terms of mixing or producing. Case in point, you’ve done some vocal tracking, and someone has requested that you deliver RAW tracks so that he or she may continue to work on the song, and have full control over any processing that may be added.

“Translation - Don’t do any mixing, I’ll handle that on my end… Just record the tracks as best as you can, and send them to me..”

One last thing to point out, is that I think it’s also important to note that in most cases - even when delivering RAW Audio files, it’s pretty common practice to do some basic house keeping, such as deleting unwanted sections of audio in between phrases, and adding basic fade in’s & fade out’s. But the end goal is to usually render a new contiguous audio file that starts at “Bar 1” with no additional processing.

In this video I demonstrate how to export Raw Audio tracks (Regions) in PreSonus Studio One 4 using a Drag & Drop workflow from the Arrange Window to the Browser.

Although this video was done using Version 4, the same concepts can be applied to previous version of Studio One.

Exporting Stems In PreSonus Studio One - Follow-Up Q & A Video

Its safe to say that although it sounds simple enough, exporting Stems can be a tricky subject. Especially when there’s parallel processing, FX Returns, & Mix Bus Processing involved. That being said - In last weeks video we covered the basics on using the ‘Export Stems’ function in Studio One, and more specifically - the difference between using Tracks vs Channels.

In this weeks video, I wanted to dig down a little further into some of the questions and comments I received from last weeks video "Tracks vs Channels - Exporting Stems In PreSonus Studio One”.

So essentially - a Q & A Video Response that will hopefully help clear things up a bit more for those who had further questions.

Furthermore, last week was all about how to export Stems from your Studio One Song - (and the difference between Tracks vs Channels) whereas this week I wanted to focus more on routing options, and how to go about structuring your Studio One Song to ensure that exporting Stems doesn't become a tedious process. Not necessarily any hard rules - but more along the lines of some guidelines and tips that I’ve picked up over my years of having to deliver stems for various clients.

However - one thing that I do want to mention with respect to exporting Stems, is that the minute you involve ANY Mix Bus Processing (on your Main Outs) the whole entire concept of ‘Stems’ kind of goes out the window.. Or to be more clear, Specifically when dealing with things like Mix Bus Compression, or any dynamics processing that may be potentially reacting to the whole mix vs individual elements.

Case in point: If you have some epic SFX Tracks that are kicking your Mix Bus Compressor or Limiter into overdrive - if you muted those tracks and played back the same mix - you would most likely note that your levels would be different. This is because the tracks are summing together and effecting the cumulative level that your dynamics processing is responding to.

This can also be the case when dealing with saturation as well.. It’s a cumulative effect. So the short answer is that “usually” (not all the time) this is something to be taken into consideration when printing stems. In my personal experience, things like basic EQ curves usually translate pretty well and don’t drastically alter the sonics - unless of course you are aggressively pushing gain or drive to saturate the Mix Bus on purpose.

At the end of the day, your deliverables will usually provide the best insight as to how to deliver your stems, and how to set up the routing in your DAW. So if it’s a matter of having to deliver stems that perfectly match your Stereo Mix Down - there are way’s to accomplish this. And in some cases Getting your stems to come ‘close’ to your final mix might be good enough as well.

But regardless, there is NOTHING worse than getting an email AFTER you’ve mixed a track saying “oh yeah, by the way, we’re gonna need stems printed for this mix” and having to go though your mix and find a way to print stems that even remotely resemble your finished Mix. Needless to say, you will only need to go though this once to see how much of a pain it is. And my guess would be that once you do have to go through this, you will most likely find a way to structure your songs to avoid being burnt a second time.

All in all, Stems are a regular part of my world - I deal with them all the time, but they don’t have to be a pain, as long as you think ahead, exporting stems can be a breeze.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

Tracks vs Channels - Exporting Stems In PreSonus Studio One Demystified

Working With Stems

If you’ve spent any time working in a DAW then you’ve most certainly heard of the term “Stems” before. Without getting into too much detail - the concept is actually pretty simple. If you are looking to collaborate with another person, whether that may be a producer, a mixer, or an artist, you will most likely be asked to deliver Stems to them - so that they may import the audio files into their DAW of choice and continue working on the song.

The general concept with Stems is that certain elements may be ‘grouped together’ and rendered out as an audio file. In some cases, this may be quite simple, such as: Drums & Percussion, Bass, Guitars, Keys, Vocals, FX.

In other cases it may be more complex, such as: Kick, Snare, Hats, Toms, Over Heads, Room, High Percussion, Low Percussion, Bass, Acoustic Guitars, Electric Guitars, Lead Vocal, BG Vocals, etc etc..

In addition, Stems can also have different channel width’s as well. Such as 4.0, 5.0, Stereo, Mono, etc etc.. But for the sake of today’s example, let’s keep it simple and deal with stereo.

**Before we move on, I also want to point out that there is another approach to exporting audio files as well, which would be “Raw” tracks.. Meaning that NO processing is applied during the exporting - but this is something that I plan to tackle on another day. For all intents and purposes - let’s assume that we want our Stems to have any plug-ins, Fader level’s, and Panning rendered into the Stereo File.

The Benefit’s of Stems

There are many different reasons why stems are a preferable way to work. The most obvious being that in the case where someone is using a different DAW - they would quite obviously NOT be able to open up a session from YOUR DAW (we do have AAF options available - but that’s a different article all together). Another good example would be when someone may have the same DAW, but NOT the same plug-ins.

And lastly, In all honesty it’s just a great way to keep things clean, tidy, and simplified when collaborating with others, or archiving your productions. Case in point, if you are 100% completely happy with your drum sound - then why complicate things any further? Just print a Drum Stem and be done with it. Your Drums will now be 1 Stereo track and 1 Fader in any DAW that the stem was imported into.

Conversely if you feel the need to leave your options open, then perhaps it’s better to “Stem Out” the drums into all of the individual elements to allow for additional processing and mixing further down the line.

But regardless, using Stems is a fantastic workflow - that simplifies the production / recording / mixing process immensely.

Exporting Stems In PreSonus Studio One

If we take the above into account - it’s quite easy to see how having different methods of exporting Stems can be useful. And thankfully - Studio One offers a plethora of different options for rendering audio depending on what needs to be accomplished - whether it’s a simple Stereo Lead Vocal Stem with ALL the FX and processing rendered in, or discrete Stems for each element of the Vocal.

The 'Export Stems' option in Studio One is an extremely useful way to quickly render out Stems from your Song. But did you know that there are some fundamental differences between using Tracks vs Channels?

In this video, I demonstrate the key differences between the 2 methods - as well as when (and why) to use one method over the other.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus

How To Embed Chord Track Metadata Into Audioloops In PreSonus Studio One 4

Since it’s introduction in Studio One Version 4 - I’ve been trying my best to make use of the Chord Track wherever I can. Although I must admit that with the exception of using “Import Song Data” features, (chord track information on Audio Events will come in when using Import Song Data) this is usually on a song by song basis. ie: I use it in certain songs as a production tool - but it’s not yet 100% engrained into my workflow. I also haven’t seen any Soundset’s that make use of this feature - (yet).

Then one day it dawned on me - “Wouldn’t it be nice if I could export all my Audioloops with the Chord Track metadata already having been detected… There MUST be a way to do this!”

This would save me the step of having to detect chords (and verify they’re all correct in the Editor) if I wanted to use the chord track in my production workflow. Also, depending on how I have the tracks in my Studio One Song setup, those Audioloops could potentially “auto-conform” to my Chord Track (in my source Song) when dragged in. ie: if I had some blank tracks setup in a template for dragging in Audioloops - and they were set to follow the Chord Track.

furthermore, my guess is that we will eventually be able to audition Audioloops in the Studio One Browser against our Chord Track in our Studio One Song. IMHO - This seems like the next logical step to take. That being said, I’m simply hypothesizing here, so don’t quote me on this.. (Although it would be pretty cool).

However if that DOES end up happening, I thought to myself - wouldn’t it be nice to “future proof” all my Audioloops I’ve been creating by embedding the Chord Track data into them before exporting. In addition, this could also prove to be useful in the meantime for my own productions. But all of that depends on whether or not this is even possible!

Well the short answer is, Yes - it is..

In this video I demonstrate how to export Audioloops with Embedded Chord Track Metadata In PreSonus Studio One.

And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)

Cheers, Marcus