If you are regularly swapping sessions with the same people, you can swap the session once, fix any I/O mapping problems, and then save that session as a template. TIP: This system memory is great for session templates. pio file, the original outputs can be restored. But, if you save a copy of your I/O by exporting it as a. This is because outputs contain hidden ID’s, and newly created outputs have new ID’s. It’s fine to rename an output, but if you delete and replace it, the memory will be lost. TIP: Because of this we strongly recommend that you do not delete your I/O settings to fix problems when the session you receive from another studio doesn’t map. If you delete your outputs and recreate them from scratch, the session will lose its memory of them too. However, this memory will only last as long as your output stays in the I/O Setup list. This still works even if the session leaves your system and is opened on several other systems before returning.

So if a mapping fails, and you fix it, those changes will stick and that session will open correctly from then on. Note that if Monitor subpaths exist in the session, Pro Tools uses the best matching format for the system monitor subpaths.Ī session will remember if it has been on a system before. It doesn’t matter if the name or format of the output assigned to the Monitor Path is different.

Pro Tools always maps the Monitor Path of the session or project to the Monitor Path of the current system. Output busses are mapped to system Output paths by unique ID if possible. When opening a session or project on a system that has a different I/O Setup, Pro Tools follows these rules to ensure the best possible remapping of the session’s or project’s I/O Setup to the new system…

Protools 12 multiple audio devices