Free Series - Studio One for Pro Tools Users
In this free video series - I take a look at learning Studio One coming from a Pro Tools perspective.
All Videos embedded / available on this Page!
In a recent post I made note of the fact that I had plans to do DAW specific content for Studio One Users. More specifically - New Studio One Users who are either making an effort to learn this new DAW, or transitioning over from DAW’s such as Logic, Pro Tools, etc.
Seeing that I have already created some specific content for Studio One User’s making the move from Logic Pro X - Today, I am happy to announce that my latest Youtube Playlist: Studio One One for Pro Tools Users (Embedded Above) has gone live.
As with the last one, a few notes on this Playlist:
This series (YT Playlist) will continue to be expanded upon. I will be adding additional videos as soon as they are ready. I already have quite a few recorded but not yet edited / exported, as well as more to record - So I would urge you to bookmark this playlist and subscribe to my Youtube Channel so that you can be notified as these new video’s become available.
If I’m being honest, these video’s are not necessarily aimed at beginners - but rather intermediate / advanced users who are coming from Pro Tools and are looking for direct comparisons (coming from the Pro Tools perspective)
I have created these videos (which in my personal opinion cover a lot of ground) in what I perceive to be the most logical order. Everything from a basic getting started, to setting up your interface properly to understanding how to monitor and record properly, to being able to edit and mix. I would advise watching these in sequence to get the most out of the series, but they can be easily watched standalone to brush up in specific areas.
I’ve chosen to omit certain areas that I feel don’t need to be overly explained. I think it’s safe to say that there are certain features in all DAW’s that translate across the board. With this specific series, I’m really trying to point out the things that aren’t immediately obvious. Or to put in into a different perspective - the things that I wish someone would have shown me when I made the move.
And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)
Cheers, Marcus
Workflow Tip - Transferring Your Studio One Song To Pro Tools - In Minutes
In this video, we take a Production created in Studio One - and open it up in Pro Tools in Minutes, complete with All Audio Files (Original Edit's in tact), Track Names, Track Order, Tempo Map, and Markers. AAF Export is a beautiful thing!
In addition to running my Music Production business, and creating content, I also do some work on behalf of PreSonus as a freelance Studio One clinician. Whenever I do any seminars, there are always a handful of Pro Tools users in the audience. And to be honest, the response I usually get is always the same. I’m paraphrasing here, but it goes a little something like this:
“I would love to use Studio One - and I do use it for my own production, but for certain projects, I have to work in Pro Tools - or at the very least, deliver a Pro Tools session. For this reason, I don’t use Studio One as much as I would like to.”
To which my reply is - In my humble opinion, Studio One has the best AAF Export workflow (with Pro Tools) that I have personally ever seen in a DAW. Meaning that I can get my whole entire Studio One Song - Over to Pro Tools, in minutes, no matter how complex it is, and whether I’m using Virtual Instruments or need to “Freeze” or “render” FX Plug-ins (such as Software Amp Simulators). It’s a really elegant solution.
Before I go any further, let’s address a few things quickly:
AAF is NOT a perfect translation - there is always something that needs to be taken into account.. This could be that it splits up stereo files to dual mono, or maybe the panning doesn’t always come across, or that it changes equal power Fades to linear. One BIG area for me, is that most AAF’s do not properly translate clip/region/event based gain - So your whole entire Gain staging could be off. This is just the way it is. And it has always been like this since I first starting using AAF’s. But In some cases, certain programs may handle one thing really nicely - but then they fail in other areas. But in all my time, I have never seen another DAW that can “hand off” an AAF to Pro Tools, and when it gets put back together - it’s not a complete disaster.
This is NOT about “DAW WARS” - I use Studio One because (for me) it’s the perfect fit, and I can work faster than I ever could in Pro Tools even when my Pro Tools chops were razor sharp. This is about a relatively painless workflow that can be used to get your Studio One Song over to Pro Tools when you need to! It’s also worth mentioning that I have done this (on the spot) in the middle of a session on more than one occasion when the situation called for it. ie: I was not able to track with my own interface, or computer, and had to use the Studio’s Computer / Pro Tools setup.
You don’t always need to deliver an AAF! - In fact, it may not be the best option. Before I create an AAF export, My first thought would probably be to Export Stems. This is a fantastic way to work, that’s used extensively in the industry. It’s super easy in Studio One, and there are also tons of different options in terms of exporting exactly what you need to deliver. If stems weren’t a good fit, then my next immediate thought would be to Export Raw Audio Files/Regions. In some cases, this may in fact be preferable. For example, If you were hired to deliver basic files, that are going to be mixed by someone else in another DAW all together. “Raw” audio Files consolidated to Bar 1 are great. BUT - When a song is in it’s production phase, where all the options are still on the table, and edits are not yet set in stone - nothing beats the flexibility of an AAF.
If this is something that seems like a familiar scenario, or you are someone that’s dabbling in Studio One, but still needs to deliver a Pro Tools session for your productions - then I hope this article / video helps!!
And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)
Cheers, Marcus
Importing A Tempo Map & Markers From Pro Tools Into Your Studio One 4 Song
In this video, I'll show you how to go about importing your Markers, Tempo Map, and any Time-Signature changes from Pro Tools into your Studio One 4 Song.
Picking up from where we left off in last week's video, I thought it would be good to do a "Part 2" with respect to AAF work-flow that talks about how to go about getting any additional information carried over from a Pro Tools Session into your Studio One Version 4 song.
If you did happen to catch the first video, you'll recall me saying that having the audio come over via AAF is great, as it allows us to essentially pick up from where we left off in Pro Tools. The benefit here of course being that we still have access to our original edit boundaries. So no need to consolidate files and find out down the line that you (or someone else) missed a bad edit.
But as you may or may not have noticed - one BIG thing that did not get translated during the process is your Markers, Tempo-Map, and any time signature changes!
Tempo Maps, Time-Signature Changes & Markers
Now first off, let me just state the obvious. If you have a basic song, in 4-4 - at 120 BPM, this isn't really a huge issue. Just recreate your markers manually, and it's not a big deal. BUT - if you have spent a great deal of time adding various Markers with specific names, and detailed tempo changes, it would be a shame to have to re-do them. The good news is you don't have to.
Using MIDI Files To 'Carry' The Information
As someone who has spent a great deal of time collaborating with various other engineer's and studio's, one thing I got into the habit of doing long ago is using MIDI files to carry over information that I wanted to translate to another DAW. Regardless of whether I was handing off my work to another studio, or simply working on my own productions, in most cases the material I work on can get pretty complex with respect to tempo changes and time-signature changes, so I really don't want to have to repeat that work, or hand someone else a session where they have no clue what's what.
So essentially this is pretty much the last step I take when exporting content, and this is something I do regardless of whether I'm printing consolidated stems, or using AAF work-flows.
MIDI Files & Markers
One thing that you may find is with specific DAW's, (not going to name any name's here - they all have a different approach) not all the information you would expect to translate over - comes across. A really good example of this would be with respect to Marker's.
In my experience, there is usually (again it depends) some little quirk, where for example creating a NEW SONG from that MIDI file will bring over the markers, where as Importing the MIDI file into an existing song will not. And like I mentioned, this isn't always the case, but I've encountered this with at least 2 major DAW's that I've worked with. (Studio One being one of them)
The Magic Of Import Song Data
I've said it before, and I'll say it again, Import Song Data is BY FAR at the top of the list for my favorite new features. The reason being because it essentially eliminates the whole concept of "not being able to bring something into an existing song". Again the keyword here being "existng".
Having said all that - In this video, I'll show you how to go about importing your Markers, Tempo Map, and any Time Signature changes from Pro Tools into your newly created Studio One 4 Song. Presumably created using an AAF from Pro Tools - but the work-flow works regardless of how it was created.
And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)
Cheers, Marcus
How To Open A Pro Tools Session In Studio One 4 - AAF Workflow
In this video, I demonstrate how to go about exporting an AAF from a Pro Tools 2018 Ultimate session - which can then be imported into PreSonus Studio One 4 via AAF Import. In addition, we will also talk about a couple things to be aware of when working with AAF's in general.
Pro Tools In The Audio Industry
Regardless of which DAW you choose to work in, one thing is pretty much certain. If you plan to make a professional career in the audio production industry - at some point you are going to be dealing with Pro Tools, whether you want to or not. Although some may argue with this statement (and that's completely fine) I'd personally go as far as saying that I cannot think of any other audio software program to date, that has made it's way into so many studio's across the world the way the Pro Tools has.
Now having said that, this does not mean that it's "the best" by any means. As has been said by many others before me, and will be said by many after me - the best software is the one that works for YOU. Another thing to point out is the huge paradigm shift we have seen in the recent years as native processing power has improved leaps and bounds. This in itself has had an impact on the whole concept of DSP powered rigs & accompanying software.
Native vs DSP - More Software Options
I think it's safe to say that at one point DSP powered rigs were absolutely essential in professional music production setups, but now with the reliability of High Speed thunderbolt interfaces such as the PreSonus Quantum, (and many others), this is no longer the case.
So where it used to be the case where people ran Pro Tools because the hardware required them to do so - In my opinion, there are now a lot more professionals running different software with 3rd party interfaces for their needs. Case in point: Studio One 4 Professional paired with a Quantum, a DP88, a handful of external Preamps, and a FaderPort 16 is a pretty Badass setup in my opinion...
Regardless of all this, the concept remains that you may very well be collaborating on a project with a colleague who is using Pro Tools. and now as of the release of Studio One 4 - we have a convenient & relatively painless way in which we can transfer a Pro Tools session over to Studio One.
AAF - Advanced Authoring Format
Without getting into too much detail, the AAF standard essentially allows users to share their projects and sessions with other's running different programs. I think it's also worth mentioning that the initial roots of AAF has to do with post-production vs music, and it's only really as a by-product that we can use AAF's for transferring music related content. But to be honest, I think that's about where I'll leave off with respect to AAF's, but if you plan on using them, I'd definitely recommend doing a bit of research. There's ton's of information available online.
From Pro Tools To Studio One 4
In this video, I demonstrate how to go about exporting an AAF from a Pro Tools 2018 Ultimate session - which can then be imported into PreSonus Studio One 4. In addition, we will also talk about a couple things to be aware of when working with AAF's in general.
And as always, if you enjoy this content, please - Share, Subscribe, and hit that like button. :)
Cheers, Marcus