Pro Tools Path Definitions - Any way to reset?

Line666

Fendurr
Sep 2, 2006
3,342
1
36
Hello all,

This may be a simple question and I may be missing something stupidly obvious, but whenever I start a project on one interface and move it to another studio in pro tools the existing path definitions get carried over - for instance if I start on a Profire then switch to a HD rig the main outputs 1/2 are still labelled as - FW 2626 SW Return 1-2. This is a gigantic pain in the arse because these definitions are mislabeled and often counter intuitive to the routing setup I need to run to get things working, is there any way I can default to the new setups IO path mapping without creating a new project?
 
Should say the IO settings themselves don't actually change so it's not an "Sessions overwrite current IO settings" kinda deal, they're just mislabeled.
 
i often have the same problem as i tend to track on on HD and mix on native, as far as pro tools 9, i just have an I/O preset saved for each system and import I/O in the I/O window, is as for setting a default i haven't found importing I/O settings that inconvenient to have even looked into it yet
 
i often have the same problem as i tend to track on on HD and mix on native, as far as pro tools 9, i just have an I/O preset saved for each system and import I/O in the I/O window, is as for setting a default i haven't found importing I/O settings that inconvenient to have even looked into it yet

This only changes the overall routing though - you can avoid that by just making sure the session doesn't overwrite the IO. I'm talking about the naming convention in the mix window which doesn't seem to change regardless of whether you import the correct settings or not. You can change it in the Bus window by just renaming or removing paths but that's clunky and it doesn't change on settings import like the IO does; all I want is for the previous mix window IO naming convention not to carry over to the new system.

protools.jpg
 
It's fine dude, thanks for your help anyway, it wouldn't be that big a deal but I've got one studio I use that this totally flies with but then theres another that's got some weird 5.1 setup going on and every time I import my project and try and get a headphone mix running it kicks it into mono and all the outs are labelled funny so I can't negotiate whats happening. I jump about a lot for overdubs and stuff so I really need sessions to work fast and not spend ages fixing something to just try and get a 1 track vocal overdub session on the go.
 
I jump around a lot too and that hasn't come up before. It's always re-set the paths automatically when I import any new i/o. If for some reason I haven't set it up to not overwrite, it should be a 3 second fix. That seems weird. Take it to the DUC maybe? Is it only doing that on the one system, or is it doing it each time you go somewhere different? Is it multiple sessions or just one? Maybe a corrupted session file?

What does the Bus tab look like?
 
It carries over on different projects, I'm jumping between 11(at home) and 10(in studio), this is the bus tab and you can just see how its inherited different naming conventions based on where its been used and isn't tidy at all:-

bus.jpg


Even when I default it to remove the unused outputs it still lists stuff as the wrong name.
 
Well that looks like a giant clusterfuck. For some reason it bothers me when studios pre-route and name all their outputs. I find it easier to just number everything and patch where I want for cue sends and the like. I've never had that kind of issue.

So it still carries the wrong name if you delete all the weird paths and then hit default or import the studio i/o? If so I dunno what it could be. May be some issue with going from 11 to 10….
 
Well that looks like a giant clusterfuck. For some reason it bothers me when studios pre-route and name all their outputs. I find it easier to just number everything and patch where I want for cue sends and the like. I've never had that kind of issue.

So it still carries the wrong name if you delete all the weird paths and then hit default or import the studio i/o? If so I dunno what it could be. May be some issue with going from 11 to 10….

As you can kinda see it's like an 8 channel mono feed headphone setup so performers can control their own monitoring levels for individual parts of the mix; honestly I'd prefer to just keep it simple and have just a stereo cue and that is possible but the project fucks with the routing so I'm getting everything everywhere with no clue if its right.

Haven't tried in the studio doing a full delete and default of the busses in the studio actually; just a default but that could work - pretty sure a lot of the busses have custom names though so it might throw it off - worth a try at least!
 
Yeah We actually have the same thing, I just send out any number output and patch it into our headphone mixer. I set up our default i/o specifically so that it wouldn't have any pre-determined weird path names which might throw off peoples setups. just the default buss settings.

For some reason I feel like I've had one or two issues with someone coming in and having an i/o problem similar, and that might have fixed it. Lemme know if it works!
 
delete all the old routing then hit default which will go to the current interface otherwise is just adds default to the pre exisiting routing and does nothing. takes me like 2 seconds everytime i take a session into or out of my place
 
delete all the old routing then hit default which will go to the current interface otherwise is just adds default to the pre exisiting routing and does nothing. takes me like 2 seconds everytime i take a session into or out of my place

Thanks for confirming! Seems dead stupid and obvious now but I'm not much of a Pro Tools enthusiast - I mostly use it out of necessity. Can't work without my slip editing. :)