|
|
Post by Tbone81 on Oct 30, 2022 13:34:39 GMT -6
I frequently freelance at outside studios yet somehow always struggle creating tracking templates in PT. I'm a cubase user but by no means a novice in PT, however I don't go under the hood very much and get a little lost with i/o settings etc. So here's my issue:
I create the perfect PT template at home, bring it to the studio, open it up and I/O settings change because I'm using different hardware...at this point there's always something screwy that prevents me from easily remapping the I/O on my tracks. I try to fix things in the I/O window, get frustrated, trash the template and build a new session from scratch and get on with the day.
Now I know its probably something stupid I'm doing on my end that makes screws with the I/O settings. And for reference, almost all the studios I work at have third party converters hooked up to their PT rigs (Symphony, Burl, Lynx).
So is there a quick fix? Or something I'm overlooking? If I just create a project file (instead of a template), assign no inputs or outputs, and open that in PT (at the outside studio) will that fix my issue? Does any of this make sense? Feeling like a dunce here.
|
|
|
|
Post by notneeson on Oct 30, 2022 13:57:41 GMT -6
I frequently freelance at outside studios yet somehow always struggle creating tracking templates in PT. I'm a cubase user but by no means a novice in PT, however I don't go under the hood very much and get a little lost with i/o settings etc. So here's my issue:
I create the perfect PT template at home, bring it to the studio, open it up and I/O settings change because I'm using different hardware...at this point there's always something screwy that prevents me from easily remapping the I/O on my tracks. I try to fix things in the I/O window, get frustrated, trash the template and build a new session from scratch and get on with the day.
Now I know its probably something stupid I'm doing on my end that makes screws with the I/O settings. And for reference, almost all the studios I work at have third party converters hooked up to their PT rigs (Symphony, Burl, Lynx).
So is there a quick fix? Or something I'm overlooking? If I just create a project file (instead of a template), assign no inputs or outputs, and open that in PT (at the outside studio) will that fix my issue? Does any of this make sense? Feeling like a dunce here.
I don't use templates much, I tend to just import session data instead. But, in that situation I typically delete all the old IO, import the latest .pio file for the studio I'm working at, and the I'm pretty much up and running with minimal reassigning. |
|
|
|
Post by drumsound on Nov 1, 2022 12:29:19 GMT -6
I had an issue when I migrated computers, upgraded PT and added an RME MADI face earlier in the year. I'm not sure if this will work for you, but it's worth trying.
Go to the I/O setup menu and hit the bus tab. On the first mono Bus Out hold option and command then click output 1 of the studio's interface. This should migrate all the successive mono outs in sequence. Do the same for the first stereo and select the first stereo pair of the studio's interface. My genius buddy figured this out for me, and I don't remember why it works...
I've not tried for input...
|
|
|
|
Post by Blackdawg on Nov 1, 2022 14:11:16 GMT -6
Yep Importing session data is the trick for you. You can still make all the templates you want, then just import them in as needed or pieces of them if you want/need. Then making sure you have your I/O saved so you can import that as well. Super fast and easy. See here: www.pro-tools-expert.com/home-page/2020/5/21/import-session-data-and-match-tracks-in-pro-toolsThis is one of Protools Super powers that I don't think any other DAW can do or do as well. And why it's still wildly popular in Post Production mixing. |
|
|
|
Post by svart on Nov 3, 2022 6:58:04 GMT -6
It amazes me that Protools still does not have a designated template function.
Reaper:
File->Project Templates->save project as template.
Done.
|
|
|
|
Post by drumsound on Nov 3, 2022 7:38:01 GMT -6
It amazes me that Protools still does not have a designated template function. Reaper: File->Project Templates->save project as template. Done. It does, and that's exactly how you do it in PT |
|
|
|
Post by svart on Nov 3, 2022 7:58:44 GMT -6
It amazes me that Protools still does not have a designated template function. Reaper: File->Project Templates->save project as template. Done. It does, and that's exactly how you do it in PT Then why are you guys explaining very convoluted ways to do it if it's that simple? |
|
|
|
Post by notneeson on Nov 3, 2022 8:01:38 GMT -6
It does, and that's exactly how you do it in PT Then why are you guys explaining very convoluted ways to do it if it's that simple? The issue we are primarily addressing is routing new io configurations when freelancing at another studio (aka not your own). |
|
|
|
Post by svart on Nov 3, 2022 8:17:47 GMT -6
Then why are you guys explaining very convoluted ways to do it if it's that simple? The issue we are primarily addressing is routing new io configurations when freelancing at another studio (aka not your own). So the template doesn't bring your routing along? Or are you talking about if the studio has some kind of setup that needs re-routing from hardware streams to the DAW input streams? |
|
|
|
Post by drbill on Nov 3, 2022 8:43:37 GMT -6
It does, and that's exactly how you do it in PT Then why are you guys explaining very convoluted ways to do it if it's that simple? Templates can be extremely simple - or incredibly complex. Your choice. For instance, I just made an incredibly complex template that allows me to simultaneously write with VSTi's, track/record to my mix audio tracks (automated and effected), print/record to my "print" tracks for a 100% instant hybrid recall (all at unity), buss/sum/record to "stems" tracks for client delivery, and print/record to my final 2 channel mix track. All in one pass if I prefer and all with the press of one key. It's one of the most complex session I've ever created, and I wanted to streamline 4-5 production processes into one step for speed and tailored to a specific clients need. Hundreds of tracks, hundreds of busses, hundreds of plugins, over a hundred hardware inserts - and one simple process now. The intricacies of pro tools are not obvious sometimes, and generally seem lost on those who have not pushed its limits or used it for years. |
|
|
|
Post by drbill on Nov 3, 2022 8:45:30 GMT -6
The issue we are primarily addressing is routing new io configurations when freelancing at another studio (aka not your own). So the template doesn't bring your routing along? Or are you talking about if the studio has some kind of setup that needs re-routing from hardware streams to the DAW input streams? The PT session or template DOES bring your routing along. The issue is that the studio you're visiting may have a different brand of interface, more/less channels, may have named their busses differently, etc.. |
|
|
|
Post by svart on Nov 3, 2022 8:47:53 GMT -6
So the template doesn't bring your routing along? Or are you talking about if the studio has some kind of setup that needs re-routing from hardware streams to the DAW input streams? The PT session or template DOES bring your routing along. The issue is that the studio you're visiting may have a different brand of interface, more/less channels, may have named their busses differently, etc.. I see. It was my misunderstanding of what was being asked. It wasn't about creating a template, it was about importing routing to a session. |
|
|
|
Post by Blackdawg on Nov 3, 2022 9:31:12 GMT -6
The PT session or template DOES bring your routing along. The issue is that the studio you're visiting may have a different brand of interface, more/less channels, may have named their busses differently, etc.. I see. It was my misunderstanding of what was being asked. It wasn't about creating a template, it was about importing routing to a session. yes, which you can do via a seperate file. Protools allows you to save/import/export I/O settings. Plus import track templates ect. Or make and start sessions. |
|
|
|
Post by damoongo on Nov 3, 2022 10:19:29 GMT -6
...at this point there's always something screwy that prevents me from easily remapping the I/O on my tracks.
I guess until we know exactly what "gets screwy" it's hard to suggest a fix other than just import session data from your template into a blank session with the house I/O, But if you tell us what gets screwy exactly, there might be an easy fix? |
|
|
|
Post by Tbone81 on Nov 16, 2022 16:18:48 GMT -6
So I tried the "import session data" function at a session last week and it worked great. I made a template at home and other than creating busses for cue mixes I left all the I/O in the session empty. Then created a new session at the studio, imported the session data and just cascaded the inputs/outputs...worked pretty great with very little fussing around, and for subsequent songs just imported the data from the first song and was off and running. Thanks guys!
|
|
