Please help! "Some paths were made inactive..."

[midnightrambler]

"...because they could not be assigned to existing path definitions".

Can anyone tell me how I can clear this message when I open up a session?

Here's the deal : I'm opening sessions made in another studio, and I'm prepping them for mixing here. I've tried assigning all inputs and outputs on all tracks to "no input" / "no output", got rid of any busses, gone into I/O setup and made EVERYTHING "default" (inputs, outputs, busses), and I'm STILL getting this damn error every time I open it up. I just don't know what else I can do to get rid of it.

It's only a small thing, but it's really, really, REALLY annoying me.

[v9.0.2]

[midnightrambler]

Ok, I think it must be a bug.

Here are some inputs (not active) : http://imageshack.us/f/841/screenshot20110623at171.png/

Here's me changing them all to "no input" : http://imageshack.us/f/121/screenshot20110623at171.png/

I save the session, close session, re-open, and look! They're back! : http://imageshack.us/f/269/screenshot20110623at171.png/


God I hate this new I/O setup. It's nothing but trouble.

[Bushpig]

Midnight,

I've had this before when getting sessions from someone else's system. I pulled my hair out with the same reappearance after restart. The solution is to set these inputs to one of your own valid input sources, then make sure those 'ghost' paths are deleted from the I/O, then restart and now you should be able to switch them to "No Input" without further trouble.

Hope that helps.

Cheers

Steve Bush
http://music180.com/pros/5887

[Fix]

I've also recently been experiencing this problem with sessions from other studios. I had one particular session where resetting the inputs and outputs and deleting paths in the I/O setup did not help, even after a restart.

I even ran into an issue with one session that would actually block all audio outputs any time I created a new track. That one session was the worst! I actually didn't find a solid consistent workaround. I just had to completely delete and load my saved I/O setup each time I created a new track or Aux.

[midnightrambler]

Thanks Steve. Yeah assigning inputs and outputs to valid sources has cured it! Until I import a track from another session with the wrong I/O of course ;-)

[WernerF]

I've been having the same problems with this new IO situation. I would love to hear from Tech Support about what is the thinking behind this being considered new and better.

[jmo1112]

This completely worked. It's such a little thing but it was driving me absolutely crazy. Even though I wasn't the person that started this thread, thanks for the tip!

[ZEUSS]

Originally Posted by Bushpig

Midnight,

I've had this before when getting sessions from someone else's system. I pulled my hair out with the same reappearance after restart. The solution is to set these inputs to one of your own valid input sources, then make sure those 'ghost' paths are deleted from the I/O, then restart and now you should be able to switch them to "No Input" without further trouble.

Hope that helps.

Cheers

Steve Bush
http://music180.com/pros/5887

Yes. This is the workaround I have been using as well. Seems to be the only way. I wish they would fix this. Still many bugs hanging around.

[Breathless]

All they have to do is add a "do not show this message again" checkbox for those that cannot be bothered with it. It really is annoying.

[Dizzi45Z]

+1