Agreed Slau,
I use that "session notes" text doc all the time when I bring in a session that
has a Billion plugs in it that have been made "inactive".
Then I can go to the tracks in question and remedy the inactive plug thing. :)
Talk soon
Chuck
YMMV
On Mar 22, 2014, at 3:30 PM, Slau Halatyn wrot
That's actually a good idea which I neglected to point out. Looking at the
session notes report to determine specifically what the problem is (like
unavailable outputs or busses, etc.) helps in planning a course of action in
the I/O Setup dialog.
Cool,
Slau
On Mar 22, 2014, at 12:54 PM, Krist
Ok, thanks so much. I think i actually managed to get rid of at least some
messages by deleting some bus paths and then clicked "default", maybe i
shouldn't have done that, but i don't see the bus paths that annoyed the
program. BTW i went to my session notes text file and read the report there
Hi Krister,
By what you're describing, it sounds to me like you're opening a session that
was previously (at some point) either created or modified on a Pro Tools system
with a different I/O setup. Thus, the input and output paths were different.
One way to fix the problem would be to go to the
Hi,
Here comes a couple of stupid newbie questions to brighten up your friday:
So, i'm in this session notes dialog that pops up everytime i open Pro tools
11. There's a text grid view list that says something to the effect that some
plugins have been disabled because they couldn't be found in th
