Do you use Pro Tools? If yes, you cannot keep on living without watching this video. We know you're not quite sure what the Pro Tools I/O setup window does, how it affects your sessions, and we know you are a little bit afraid of it. (We know everything). So, how does it work? What does it do? Is it really useful? In this video, Fab Dupont will answer these questions (and more).
In under 25 minutes Fab will make understanding the I/O Setup a piece of cake, explaining in detail what it does, and how to think about it in a simple way. The ProTools I/O Setup is not the complicated mess that you think it is. It's a very convenient and powerful tool that can be extremely useful, especially when working with large sessions or traveling from system to system
No more excuses for messy sessions, corrupted routing and weird inexplicable bus names, watch this video and become a true Pro Tools I/O Setup expert.
00:00:07 Good morning children!
Today, we're gonna talk about
the Pro Tools I/O Setup.
00:00:12 Wait! Don't go. Stay!
Stay in your seat.
00:00:17 No one's gonna get hurt.
Here we go!
Very important:
You must have Pro Tools 9 or 10
for any of this to make sense.
00:00:25 If you have Pro Tools 8 and before,
you have two options:
upgrade, or move on!
Here are the four main panes.
00:00:35 You can think of them as two groups:
the Input, Output and Insert panes
represent physical outputs
of your interfaces.
00:00:46 Now, I have four 192s right here,
but you may have two,
you may have three, you may have one,
you'll see the number of 192s
that you own.
00:00:53 But think of the Input, Output,
and Insert
as a physical representation
of your hardware.
00:01:01 The Bus pane is a different thing
we'll talk about in a second.
00:01:05 For those of you who don't know
what the Insert pane is about,
this is about the Pro Tools I/O system.
00:01:11 Pro Tools lets you turn
your hardware into a plug-in
by letting you connect
the same input and output.
00:01:17 Say for example I have a Chandler TG1.
00:01:20 I will connect it to both Input
and Output 1-2 of my Pro Tools rig.
00:01:25 What that's gonna let me do
is let me route
the signal from a channel in Pro Tools
to Output 1-2,
through my TG1,
back into Input 1-2,
back into that channel,
all in one go, and fully delay
compensate the whole path,
phase accurately. Very practical.
That's what the pane is about.
00:01:45 For example, say I had TG1
on that Input 1-2.
00:01:49 I call it TG1. Now in my session,
here in the insert,
where I would use TDM plug-ins
or RTAS plug-ins,
I can go to I/O and insert
my hardware TG1
as if it were a plug-in.
00:02:01 There's no settings here, because
it's a piece of hardware in my rack.
00:02:04 But the audio is coming from my track,
going out Output 1-2,
into the TG1, out of the TG1,
back into Input 1-2,
back into this track, and now
I can use a plug-in after that,
for example the Oxford Filter.
There you have it.
00:02:17 That is called
an I/O insert in Pro Tools,
and the name of those are controlled in
that pane called Insert in the I/O Setup.
00:02:26 If you look at it here,
I have a whole bunch of inputs,
a whole bunch of outputs,
a whole bunch of inserts, which use
the same inputs and outputs
as the Input and Output pane.
00:02:38 And then I have my Bus pane,
which is where all the magic happens
from Pro Tools 9 to Pro Tools 10.
00:02:45 These two last panes here are useful
if you own a PRE from Digi,
or any mic pre system that's compatible
with this remote control,
and this is in case you need to do
hardware delay compensation.
00:02:57 You will only need this pane if you do
complicated roundtrip I/O stuff,
which we'll discuss another day.
00:03:03 Of course, if you have
Pro Tools 9 or 10,
this could be an Apollo,
it could be an RME Fireface,
it could be anything.
00:03:10 You won't get the pretty icons,
but you'll get a different set of names,
and a different set of outputs.
This is the default Digi setup.
00:03:17 The principles are the same,
no matter what interface you own.
00:03:19 It's all the same idea.
You just have to have the right idea.
00:03:22 So what's the idea?
As of Pro Tools 9 or Pro Tools 10,
and all subsequent releases we hope,
the I/O Setup in Pro Tools
functions this way:
there are two ways
to save your I/O Setup.
00:03:33 It can be saved with the system, meaning
it pertains to the hardware you own,
and it can be saved with the session,
and I'm gonna show you that in a minute.
00:03:42 The first thing you need to do is learn
your personal system I/O Setup,
and custom design it
so it speaks to you.
00:03:51 The best way is to launch Pro Tools
with no session open
and open the I/O Setup window there.
00:03:58 This is not my HD IO setup at all.
00:04:01 This is an I/O Setup
from apparently a native interface.
00:04:05 Ok?
What I'm gonna do now is I'm gonna
load my built-in I/O Setup.
00:04:10 Since there is no session,
there is nothing in memory,
Pro Tools will let me do that
very easily.
00:04:15 As of Pro Tools 9,
they've changed something.
00:04:17 You can load a different I/O Setup
for every pane separately,
and that's now the default state.
00:04:23 If you want to refresh the whole thing
with your own preset,
what you have to do is
Option+Click on Import Settings.
00:04:30 If you Option+Click on Import Settings,
it will import the entire I/O Setup
for all the panes.
00:04:36 If you do not Option+Click,
it will only import that one pane.
00:04:40 I'll show you in a second.
00:04:42 So, Fabulous Room, today's date.
00:04:45 It is safe to delete unused paths.
00:04:47 I'll go over that in a second too.
So Yes!
This is my I/O Setup.
00:04:53 Meaning, you can see my four 192s,
you can see all the inputs,
you can see
that I own a Crane Song Hedd,
and a UA 2192.
00:05:06 You can see
that I own a 16-channel Neve console,
and a 16-channel Dangerous 2-Bus.
00:05:11 You can see that I tend to use
digital outs.
00:05:13 This is the default I/O Setup
for this rig.
00:05:17 And this is the Bus,
which we'll talk about in a second.
00:05:21 As you can see, I went in
and took the time to enter
for every physical output
in my Output pane,
the name of the piece of gear connected
to that output.
00:05:30 So the first 16 channels are my Neve,
it's a 54 Series,
I was too lazy to type 54, but I know
it's Neve channel from 1 to 16.
00:05:40 After that, it's my 2-Bus,
channel 1 through 16.
00:05:44 Then my Crane Song, my UA,
and my digital outs.
00:05:46 These down there I did not name, because
nothing is permanently connected to them,
so I had no name to give them.
I did the same thing with the Input.
00:05:54 The only thing that's permanent
on my Input
is my Crane Song and my UA,
everything else is hard-patched
depending on the song,
so I have no special names.
00:06:02 The benefit of taking the time
to name those inputs and outputs
is apparent when you start
opening sessions.
00:06:08 You open, say, the Output menu here,
now it makes sense.
00:06:13 It doesn't say Audio 1-2,
or Audio 78-79,
it says 2-Bus 1-2,
I know where I'm going.
00:06:19 That's basically the point
of doing that.
00:06:21 The other reason of doing that is that
it will make your life much simpler
when you start dealing with the Bus pane
of the I/O Setup in Pro Tools 9 and 10,
and subsequent releases.
00:06:29 Let's look at that.
00:06:31 It can be a little odd to see
Neve 1-2 here, and Neve 1-2 here.
00:06:37 Yes. But here's how you have
to think about it.
00:06:40 You named your physical outputs
so that you have some easy ways
to see where the signals are going.
00:06:48 Pro Tools then,
when you create your I/O Setup,
will look at those names and say:
"You know what?
It is most likely that my owner, when
he wants to route something to Neve 1-2
is going to want to see Neve 1-2
in the menu too!"
It makes sense?
I can't get angry at that.
00:07:04 Here's how you think about it.
00:07:06 These here are the busses on the left.
You have a whole bunch of them.
00:07:10 They can either be mapped
to a physical output,
or they can be just
plain old-school Pro Tools busses.
00:07:17 That's how you think about it.
00:07:18 The naming is just an added cherry on top
for you to not have to think too much,
and we like that,
because we don't like to think too much!
Sometimes, the I/O Setup can get
a little overwhelming
because a lot of stuff is going on,
you got a lot of legacy names
coming from elsewhere,
they stay in your session
and you can't get rid of them.
00:07:34 Here's what you should do.
You should create a new session...
00:07:39 and select Stereo Mix.
Save the session, whatever.
00:07:44 Whenever I create a session
that I know I'm not gonna keep,
I put it on my Desktop
and I call it "Trash me."
It sends a message.
00:07:52 It creates my session.
I open the I/O Setup.
00:07:55 In the I/O Setup right here, what I do
is I check that everything is kosher
and totally blank, from the beginning
as if nothing ever happened.
00:08:05 Creating a new session using the Stereo
Mix setup will do that for you.
00:08:09 Alright? Once that's done,
and you've checked that
everybody's happy,
you export those settings, and you call
them, guess what... Stereo Mix!
And save them. I'm replacing
the ones that were there before.
00:08:21 You've now created a blank I/O Setup,
that you can always get back to.
00:08:26 For example, say you've been working
for a week on a record from... wherever,
and there's a whole bunch of names
and a whole bunch of stuff
that makes no sense to you because
it doesn't belong to you.
00:08:36 You see a Mytek preamp,
you don't own a Mytek preamp,
why is the name there?
What you do is you open
the I/O Setup with no session open,
and then,
you Option+Click on Import Settings,
and import that Stereo Mix
you just created.
00:08:53 Delete unused paths.
00:08:55 You're back to a completely blank setup.
00:08:58 And that's a good blank slate.
00:09:00 If you have taken the time
to rename your stuff
like I showed you earlier,
then you should import that.
00:09:04 By the way, here's a cool trick.
00:09:06 You double-click on the first one,
you type your first name, say Neve 1-2.
00:09:11 If you hit Tab, it highlights the next one
so you don't have to click 700 times.
00:09:15 You can just click once
and just use Tab.
00:09:18 That's just a little trick.
00:09:20 It is very important
to not forget the Option button.
00:09:23 Say I want to reimport
my personal I/O Setup.
00:09:26 If my finger is not on the Option button
and I click Import,
and I open my Fabulous Room V5,
it's only gonna import the Bus.
00:09:36 The Output is gonna stay the same.
00:09:39 And it's starting to make a mess.
00:09:41 In the case where you're trying
to create your own environment,
and stay within your own environment,
it is really crucial
to always click+Option
when you import the setting.
00:09:50 Check it out! If I now import the setting
while pressing Option,
selecting the same thing,
deleting unused paths,
all of a sudden,
it makes a lot more sense,
we're back to where we were before.
Don't be lazy!
This is where
it can get a little confusing.
00:10:07 There are two ways you can import
an I/O Setup in Pro Tools.
00:10:10 You can import it pressing the Import
Settings in the I/O Setup window.
00:10:14 Simple.
00:10:15 But also, whenever you open a session,
that I/O Setup can be brought in.
00:10:21 That's why they've added
this little thing here.
00:10:24 It's called 'Sessions overwrite
current I/O Setup when opened.'
It's not that clear, but if you think
of it this way... Listen to this:
Session I/O Setup overwrites
system I/O Setup when opened.
00:10:39 Now that makes sense.
Meaning, if you click this...
00:10:43 whatever I/O Setup is in the session
will nil all the work you've done.
00:10:47 If you unclick this,
these two panes, Input and Output,
are safe.
00:10:53 Your system I/O Setup is safe
from being touched
by importing sessions,
when you have this thing here unclicked.
00:11:00 I strongly recommend
you keep it that way.
00:11:03 What happens when you open a session
that comes from a different system?
Very good question,
thank you for asking!
I just so happen to have one right here.
00:11:11 Here's my I/O Setup. This is mine.
I own it.
00:11:14 These are my names. They are mine.
00:11:17 This is my Bus.
You can see that everything is in order,
perfectly aligned!
And I have all these busses.
00:11:23 I'm gonna close my I/O Setup
and open that session.
00:11:26 It's called "Saving Myself", which is
completely irrelevant to our discussion
but still a good thought nonetheless.
00:11:32 What you're gonna see when you open
a session from a different system,
most of the time, is all this...
'Your I/O Setup has changed...' Beware!
'Check the I/O Setup window...'
'Please visit the I/O Setup dialog...'
'Some paths were made inactive...'
Don't freak out, it's ok,
just click No.
00:11:48 You can click Yes,
but nothing interesting happens.
00:11:51 When you look at this I/O Setup,
what has happened?
It seems that a lot of things have
changed in my Bus environment here.
00:11:59 But in the Output, nothing has changed.
00:12:02 Because this little thing here
is unclicked,
which means that all my names
are still in my system.
00:12:08 That's good news, because I spent
a lot of time entering those names.
00:12:11 If you look at the Bus pane,
it's a little messier.
00:12:15 Right now, if I press Play on this
session, I'm not gonna hear anything.
00:12:19 I'm not gonna hear anything,
because if you look here,
the last track to the right,
which is the main track,
is supposed to go to something
called 'Digital Out.'
But that's inactive. It's grayed out,
and it's italics.
00:12:32 The reason for that is
that on the old system,
it was going to a certain output,
and that output is not available
on this system.
00:12:39 What Pro Tools does when it opens
a session
is it looks at the I/O Setup
that's contained within the session,
the session I/O Setup,
and then it looks
at your system I/O Setup.
00:12:48 And then it tries to make sense of it.
00:12:50 It is most likely that
you do not have the same rig
as the dude who sent you the session.
00:12:55 What Pro Tools really does
is it looks at the names.
00:12:58 So... For example...
00:13:00 Say the guy has an SSL,
and you have a Neve.
00:13:04 It's very unlikely that Pro Tools is
gonna be able to map SSL 1-2 to Neve 1-2,
or SSL 3-4 to Neve 3-4.
00:13:10 Those don't talk to each other.
00:13:12 What you have to do is teach Pro Tools
what's going on.
00:13:16 The beauty is that there's a system ID.
00:13:19 Meaning that Pro Tools will know,
next time you import a session
from the SSL guy,
that you enjoy
routing SSL 3-4 to Neve 3-4.
00:13:29 And that's saved at the system level.
00:13:31 The first time you import a session
from a dude who has an SSL,
but you have a Neve,
you have to do it by hand.
00:13:37 The next time,
Pro Tools will do it for you.
00:13:39 Look at what just happened.
I just opened the session,
and I opened the I/O Setup.
00:13:44 1-2 from the session setup
is being routed to Neve 1-2.
00:13:48 Input 1-2 is an exception.
00:13:50 Avid knows that most people listen
to their music through Output 1-2,
so it will by default route Output 1-2
to your Output 1-2, no matter where
the Output 1-2 was on the original setup.
00:14:02 That's an exception. But...
00:14:04 if you go down here, apparently
the guy who sent me this session
did not have an SSL, he had an 'A'!
Because I see here A 3-4, A 5-6, A 7-8.
00:14:13 Apparently he had a 'B' too...
B 1-2, B 3-4, B 5-6...
00:14:16 This is somebody
who didn't name his I/O Setup.
00:14:19 Lazy!
Oh! He did name 'Digital Out.'
So now, check this out.
00:14:24 Pro Tools was not able
to route it to anything.
00:14:27 It says:
A 3-4 is not available.
00:14:30 I know that the big temptation
is to quit the I/O Setup,
go in here and say:
'Ok, you know what?
In my system, at the I/O level,
my Output is this!'
If you do this, you're not teaching
anything to Pro Tools.
00:14:44 What you need to do is
stay in the I/O Setup and say:
'Listen...
00:14:50 A 3-4 is really Neve 3-4.
00:14:54 A 5-6 is really Neve 5-6.'
And so on, on so forth...
00:14:58 Neve 7-8.
00:15:00 B 1-2 is Neve 9-10.
00:15:03 Etcetera, etcetera, etcetera,
as they say over there.
00:15:08 At this point,
I've remapped the old I/O Setup
to my personal system I/O Setup,
within the I/O Setup window.
00:15:16 If I click OK,
Pro Tools is gonna think for a second,
remap everybody,
and now my session is playable.
00:15:23 The added benefit, of course, is that
because of the embedded system ID
in every session, next time you open
a session from that dude, as I said,
you won't have to do that by hand,
Pro Tools will do it for you.
00:15:34 Now...
Here's where you need to pay attention.
00:15:37 Busses.
00:15:38 Not the ones that I mapped
to the outputs, the other busses,
the ones that you use for reverbs
and stuff like that.
00:15:43 Those get overwritten. Check it out.
00:15:46 See what's going on right now?
I have Horn Sub, Overhead, and then...
00:15:51 for the sake of demonstration,
I named a bunch of busses 'old,'
because that's coming
from the old session.
00:15:58 Those were the busses that were named
Bus 1-2, Bus 3-4, Bus 5-6...
00:16:02 Here is where it gets confusing.
00:16:04 There's nothing that looks more
like Bus 1-2 than Bus 1-2.
00:16:08 And nothing that looks more
like Bus 3-4 than Bus 3-4.
00:16:11 And... I'll stop there!
The idea here is that if you don't
really know what's going on,
that's where the confusion comes in.
It's all because of the naming.
00:16:19 The system is very reliable.
00:16:21 The naming is difficult, because
there's a lot of double use.
00:16:24 Let me show you.
00:16:25 This is what you need to keep in the back
of your mind when you open a session
that comes from a different system,
or an older session
from a previous version of Pro Tools.
00:16:36 If you look at my basic I/O Setup here,
I have all my physical outputs routed
and then I have 128 busses named
Bus 1-2 through Bus 128.
00:16:46 Fair enough.
00:16:48 I'm gonna close this I/O Setup
and I'm gonna open the same session.
00:16:51 Look at what happens to the busses
that I had in my default I/O Setup,
a.k.a. my system I/O Setup.
00:16:59 Open Recent... "Saving Myself" again,
that feels good...
00:17:04 No!
Here it is!
I've let this so that it looks
as if it were the very first time
I opened this session
from this older system.
00:17:15 As you can see,
Pro Tools is confused about A 3-4,
or A 5-6 and all that stuff.
We know how to deal with that.
00:17:21 These are the rest of my system
I/O Setup, that are at the bottom there.
00:17:25 In the middle right here are the busses
that came from the session.
00:17:28 Instead of naming them Bus 1-2
for the sake of demonstration,
I named them old 1-2.
00:17:35 Where are my Bus 1-2 through Bus 128?
They're gone!
That is why I don't default
name busses like, you know,
all my 3 reverbs I use all the time,
I don't have those default names
in my system I/O Setup.
00:17:49 I do a different thing.
Let me show you.
00:17:52 If you really want to have
a whole bunch of pre-named busses,
it could be useful
if you do a lot of big, big sessions,
or you have a lot of Auxes,
or you use a lot of different...
00:18:02 reverbs and delays,
it can be tedious to name everything.
00:18:05 The way you can do that
and not lose all those names
every time you import a session
from a different system,
is to create an I/O Setup setting file
with just busses in it,
and save it. I have one.
00:18:17 It's called... guess what?
"Basic Bus Names."
You open it.
00:18:22 It's always safe to delete unused paths.
00:18:26 And there you go.
00:18:28 For the sake of demonstration,
they're named 1 through 60.
00:18:31 What's going on is you added your names,
1 through 60 in my case,
to the existing names
that came with the session.
00:18:37 Because I clicked Yes
to delete unused busses,
you'll notice that everything
that's not used in the session is gone.
00:18:45 Meaning all those unused physical outputs
that came from my system setup are gone.
00:18:50 And this can be kind of cool. Why?
Check this out. The menus now,
especially the Output menu, are short.
00:18:57 Because you don't have every single
physical output available in my session
in the menu, because it was removed.
00:19:03 It's no big deal, you can recreate it
if you need to,
but it's really nice when you're working
fast to not have to wade through
this gigantic menu that goes like this,
just to find the output
that's usually at the very bottom.
00:19:13 Here's another note. In the I/O Setup...
the order of what you set up up here,
say for example this bus 10
is my Very Important Bus...
00:19:23 Ok? If it's done here,
when I'm gonna go to my session,
and I want to use it,
it's gonna be Very Important Bus
down here.
00:19:32 If I have 128 busses,
it's gonna be difficult to find.
00:19:35 The beauty of the new I/O Setup window
is you can take this Very Important Bus
and put it up here.
00:19:42 So now when you go back to your menu,
the Very Important Bus is at the top.
00:19:47 You can actually customize the order
in which the busses and outputs
appear in your menus,
from the I/O Setup.
00:19:54 It makes a lot of sense
for big sessions.
00:19:57 Here's something
that's probably gonna happen to you.
00:20:00 If you see here and I click on this,
and I go into Bus menu,
I see bus menu a, and bus menu b.
00:20:06 What's that about? That is a new thing
from Pro Tools 9 and Pro Tools 10.
00:20:10 If you go back to your I/O Setup,
you'll notice down here
that you have a bus count.
00:20:15 Right now it says Active Busses:
132 out of 256 possible busses.
00:20:21 If you've been wondering why you get
two menus, a and b,
here's the reason why.
00:20:25 The reason why is
you have more than 128 busses.
00:20:28 It's gonna put the first 128 in menu a,
and the second 128 in menu b,
and it's not necessarily very well
outlined in the manual, now you know.
00:20:36 Say I get rid of a bunch of busses here,
I delete them...
00:20:40 I now have 118 busses.
If I go back in that menu...
00:20:43 I only have one bus menu.
00:20:47 Here are the main things to remember
about this video, in short order.
00:20:52 The most important thing to remember
is that Pro Tools has
2 sets of I/O Setup,
the system I/O Setup that lives
with your hardware within your system,
and the session I/O Setup
that can travel.
00:21:04 The Input and the Output panes are
the basis of your system I/O.
00:21:10 They represent your hardware
inputs and outputs.
00:21:14 The Bus pane is more
of a virtual routing environment,
kind of your virtual patchbay.
00:21:20 That's how you think about it.
00:21:22 Pro Tools will look
at your physical system I/O Setup
and try and make something up
for your Bus I/O Setup automatically,
so you don't have to name
all those busses by hand.
00:21:33 It's a service.
00:21:34 And that's why you have twice the same
names in the left and the right columns.
00:21:39 Since you will keep
the 'Session overwrites I/O' button off,
nothing will never happen
to your internal, or system I/O Setup,
everything will happen
in the Bus I/O Setup.
00:21:52 Don't reroute sessions
in the session window.
00:21:55 Reroute your sessions in the I/O Setup
so that next time you get a session
from that dude with the SSL,
it will reroute automatically.
00:22:03 It's always ok to delete unused paths
when importing settings.
00:22:07 What Pro Tools is doing
is looking at your system I/O Setup,
your physical outputs
and your virtual busses,
look at everything that the session
does not need,
and gets rid of it. It's a good thing,
because it makes for leaner
Input and Output menus.
00:22:22 You can always recreate
whatever you deleted
in case you happen to need it,
in a minute.
00:22:27 If your Bus menu has Bus menu a,
and Bus menu b,
you're not doomed,
you just have more than 128 busses.
00:22:34 If you really want a blank slate,
you must Option+Import
your template I/O Setup settings
while there's no session running.
00:22:42 Otherwise, Pro Tools will keep
some names in there
and drive you baddy.
00:22:47 In summary, the Pro Tools I/O Setup
is your friend, and here's why.
00:22:52 This is what you used to have to do
when switching songs in between mixes.
00:22:58 Et voilà!
Once logged in, you will be able to read all the transcripts jump around in the video.
Fab Dupont is a award-winning NYC based record producer, mixing/mastering engineer and co-founder of pureMix.net.
Fab has been playing, writing, producing and mixing music both live and in studios all over the world. He's worked in cities like Paris, Boston, Brussels, Stockholm, London and New York just to name a few.
He has his own studio called FLUX Studios in the East Village of New York City.
Fab has received many accolades around the world, including wins at the Victoires de la Musique, South African Music awards, Pan African Music Awards, US independent music awards. He also has received Latin Grammy nominations and has worked on many Latin Grammy and Grammy-nominated albums.
Parts of this site and some files are only accessible to pureMix Pro Members or available to purchase. Please see below our membership plans or add this video to your shopping cart.
Thanks Fab, always been unclear about my IO Setup.
jean1123
2017 Jan 13
Merci! Ce vidéo répond à plusieurs de mes questions concernant les inserts et les bus!!!
Markedgeller
2016 Apr 22
I'd be very interested to know if there will be an updated video of this to cover the way it now works in Pro Tools 12. I'd got it all worked out with the help of this tutorial, then Avid went and updated it!
Audiogroupe
2016 Feb 20
Merci Fab ! C'est toujours un plaisir de regarder (et d'apprendre au passage...) tes vidéos !
drew_Stapleton@hotmail.com
2016 Jan 11
You have a HD 192 and Aurora 16s. How are you using them both? i.e., how are they connected and what are you using them for in your work?
ChrosRod
2015 Nov 28
This night Fab saved my life!
GavinS
2015 Sep 11
Thanks Fab! This was fab.
I knew there must be a way to keep I/O clean and still functional.
You're the best!
CCHorton
2015 Mar 25
Change the I/O in the I/O menu instead of the session! Thank you!! That alone will save me unimaginable amount of time!
NSpablo
2015 Mar 12
I mean the one u can incorporate gear.
NSpablo
2015 Mar 12
Is the I/O setup just for Pro Tools HD?
paulgioia
2015 Mar 04
Thanks Fab! As always 5 Stars. I have learned so much from you.
crash
2015 Mar 02
you answered my question !
merci Fab
sual
2015 Mar 02
Making the un-understandable, standable. Thanks, Fab!
bolupona
2015 Mar 02
Thanks. Always learning something new, even in setting up I/O. I had a default system but the idea about the buses makes sense. About to modified it right now.
Merci Fab!
