Inputs automatically reassigning after selecting "no input"

[BrianJArmstrong]

Hello,
I have a session (and many other sessions where this has happened) where I have assigned all my audio tracks "no input". After doing nothing in particular (sometimes it does it after I close and reopen the session, sometimes I'll just notice it's happened) the tracks have reassigned the inputs.

Known bug, or user error?

[Meads]

Got that, too. Since PT9.
And this results in this cursed window on every opening of every session that says:
""Some paths were made inactive because they could not be assigned to existing path definitions."

And you can't get rid of it, because if you select "no input" to rule these cases out, this is just not being saved.

Oh, the stupidity of this piece of software!

[Kasper]

Have you tried unchecking "sessions overwrite current i/o" in the i/o setup window?

kasper

[Rich Breen]

Originally Posted by Meads

Got that, too. Since PT9.
And this results in this cursed window on every opening of every session that says:
""Some paths were made inactive because they could not be assigned to existing path definitions."

And you can't get rid of it, because if you select "no input" to rule these cases out, this is just not being saved...

You need to first assign the inputs to a path that *exists* in your current I/O, then save the session, close, and reopen. *Then* you can assign to "no Input" and it will stick. And yes, it's a PITA....

best,
rich

[Meads]

Originally Posted by Kasper

Have you tried unchecking "sessions overwrite current i/o" in the i/o setup window?

kasper

I always have that unchecked.

And the way to make it work is ridiculous. Thanks though, Rich.