Managing busses/outputs - Deleting, etc...

[bchrismar]

Rudimentary question here...

I never mess with outputs, and I never delete busses. I create them within sessions or in my template, and I basically leave everything alone.
I have to create some 5.1 templates now, and I'm wanting to be sure I don't goof up.
Are buses (and labels) in the I/O tab stored in each session? Meaning, if I delete all busses from the I/O tab in a session, does it just delete those from that session/template? Or does it affect any other sessions?
Outputs - When I've worked on sessions from other places, sometimes the output assignments have to be redone. No problem. I simply switch them to my normal output routing. But later when I open *different sessions, it seems to be out of whack again. It's almost like injecting that one change starts to affect other sessions.

I guess the question boils down to... which I/O and BUS assignments are STATIC, and which travel with and only inside the session itself?
Hope this make sense. I'm a set-and-forget mixer so I want to ensure I'm doing things correctly as I go about making new templates, changes, etc.

[junkgear]

I/O settings are not static and different configurations can be both exported and imported in PT so that you can move those settings between systems or recall them on your own system.
One area people get tripped up is when opening a session they leave the I/O setting on ‘Last Used’ which will load up whatever configuration you used on your last session.

For a better understanding, look at the I/O settings section of the PT Reference Manual. Page 87 is a good place to start.

[its2loud]

To add to the above, an easier way to understand this is that BUSSES will travel with your session in a very clear and obvious state. OUTPUTS generally stay the same for the hardware and room that you are working in.

Therefore, if you make a template with 5.1 busses for outputs, sends, etc, those will travel with that session no matter where you take it.

If bringing to a different facility for a 5.1 mix. As long as you have a 5.1 MAIN buss or MONITOR buss path, that will, and should be, most likely automatically routed to that facilities 5.1 OUTPUT path. As long as the name stays consistent or matching.

If not, you can always go into your I/O setup page and route your 5.1 MONITOR buss path out the facilities 5.1 OUTPUT. You NEVER want to import your studio's output configuration into another facilities room. This will indeed mess up any internal routing they have already done. Nor do you EVER want to open your session in another facility and click on the "Restore from Session" button in the IO Setup (see pic). This will also wipe any OUTPUT settings that facility has already configured.

For your own room. Setup the IO OUTPUTS for the widest available path you have in the room. So if you have a 5.1 speaker setup. Your static room OUTPUTS should always be the 5.1 monitor paths. You can have subpaths if you'd like to accomodate for any other configurations you'd have.

Whether you're working in Stereo or 5.1, this should never need to change. You only work in the template you want to work in and as long as your OUTPUTS are setup accordingly you should never need to worry about loading or reloading an OUTPUT configuration.

[bchrismar]

Originally Posted by junkgear

I/O settings are not static and different configurations can be both exported and imported in PT so that you can move those settings between systems or recall them on your own system.
One area people get tripped up is when opening a session they leave the I/O setting on ‘Last Used’ which will load up whatever configuration you used on your last session.

For a better understanding, look at the I/O settings section of the PT Reference Manual. Page 87 is a good place to start.

Last used has probably gotten me many times. Great reminder thank you!

[bchrismar]

Originally Posted by its2loud

To add to the above, an easier way to understand this is that BUSSES will travel with your session in a very clear and obvious state. OUTPUTS generally stay the same for the hardware and room that you are working in.

Therefore, if you make a template with 5.1 busses for outputs, sends, etc, those will travel with that session no matter where you take it.

If bringing to a different facility for a 5.1 mix. As long as you have a 5.1 MAIN buss or MONITOR buss path, that will, and should be, most likely automatically routed to that facilities 5.1 OUTPUT path. As long as the name stays consistent or matching.

If not, you can always go into your I/O setup page and route your 5.1 MONITOR buss path out the facilities 5.1 OUTPUT. You NEVER want to import your studio's output configuration into another facilities room. This will indeed mess up any internal routing they have already done. Nor do you EVER want to open your session in another facility and click on the "Restore from Session" button in the IO Setup (see pic). This will also wipe any OUTPUT settings that facility has already configured.

For your own room. Setup the IO OUTPUTS for the widest available path you have in the room. So if you have a 5.1 speaker setup. Your static room OUTPUTS should always be the 5.1 monitor paths. You can have subpaths if you'd like to accomodate for any other configurations you'd have.

Whether you're working in Stereo or 5.1, this should never need to change. You only work in the template you want to work in and as long as your OUTPUTS are setup accordingly you should never need to worry about loading or reloading an OUTPUT configuration.

Thanks for this input! Going to develop new I/O templates with this in mind.

[zedhed]

The import/export feature in the I/O menu is a great way to back up your studios configuration, as mentioned by junkgear.


Export settings to a location on your computer and if anything gets changed involuntarily, just import I/O settings back.