Best way to import I/O settings?

[Lawson]

I've gone and re-labeled the I/O names in the I/O dialog window. I exported the settings and am now trying to import them into older sessions that used a default set. When I try to import the new settings some old redundant used paths remain as well. When I try to delete these old I/O paths that are competing for the same I/O as some new ones I've imported; it tells me that I might lose some path references and automation in the session. I'm wondering what the most efficient way is, to import those new settings without disturbing the session I/Os.

[Rail Jon Rogut]

There is no "Merge" option... this is the worst dialog in Pro Tools and IMO needs a rewrite... The easiest method is to set all inputs and outputs to "none" before importing an I/O setup.. but then you'll have to reassign all your I/O.. if you end up with duplicates, after importing the new I/O, reassign the I/O manually, then delete the old I/O.

Yes, I know, it sucks!

Consider using Import Session Data to change I/O if you have multiple sessions with similar setups.

Rail

[filmixer]

>it tells me that I might lose some path references and automation in the session<

On multichannel paths, you'll loose some pan automation if you select a new path that has fewer channels or you delete the path. Fader and send automation will be unaffected. If you have duplicate paths in your I/O setup after an import, just uncheck the paths that overlap the ones you want to use. It doesn't really hurt anything that they are there. If some unused paths are in the way or you just want to see the new ones, drag the unused paths down to the bottom of the list. After you reassign things to the new paths and everything is how you want it, just delete any unused paths that you don't need anymore.

[Howardk]

I have often thought it would be much better if the system in/out names/IDs were more integrated. The names we modify would just be additional labels, and the system would allow the import of labels, which would just overwrite the current user labels in the session according to the system names. . . This would avoid duplicate paths when names didn't match etc. . . because the matching is at a system names level, not the user labels.

[JGuth]

Yes, ie we need an i/o mapping option: "map the inputs, outputs on this session in order on to my hardware i/o's
and their labels." Untill then Rail has described the easiest method.

[Howardk]

This brings another thing to mind. . . ProTools should really allow users to edit the I/O and Buss names directly in the Edit or Mix Windows, just by double clicking on the label. I find it a pain to open the I/O dialog to change names as I develop my session --> assigning inputs to tracks, setting up mix busses, FX busses, etc. . . A quick double click on the label to make the name meaningful would be a great addition. At this time, for the most part, I just leave the names as stock because it is too much of a pain to open the I/O Dialog as I go. If the labels could be updated with a quick double click I know I would have very clearly annotated sessions which would make it faster to make adjustments, especially when coming back to a session from weeks ago. I dropped this suggestion with Digidesign a year back and have not heard anything. . .

It would also be a time saver to be able to drag-duplicate Aux sends to other tracks (just like we can do with plugins). If I have a group of BG vocs or toms, I generally want the same FX send, at the same level on each. Creating one, adjusting it, and then dragging a duplicate to each track would same considerable time. . .

[PMoshay]

Not to mention the 192's analog in/out hassle. (especially with the extra analog cards)
I wish i had a 16 ch ALL ANALOG in/out 192. (1-16 in & 1-16 out)

I'll bet thats the next release of hardware.....