Protools 10 and 10.0.1 does not save input routing

[Ale]

I have a session that has the following problem

140 active Tracks, Some of them I want to switch "NO INPUT"
Whenever I load this session again the old inputs are in again.

The original session came from an other HD native.
Because I have on my machine another In/Out configuration some In/Outs are greyed out. Those greyed out tracks are not possible to save to no input.

There is a workaround when I save session first with inputs switched something else and after reopen then switched to no input. That works!

Ok! Not a real problem.
I am just wondering if someone has similar errors.
Good, that it does not happen on my aux tracks. Otherwise my mix would be broken!

Ale

[Bushpig]

Ale,

This is a known bug. But you've successfully discovered the only known fix for it. It was discussed at length on this thread some time back:

http://duc.avid.com/showthread.php?t=303229

Not really a total show stopper, so once we all figured out the solution, we just moved on. A bit annoying, but it's OK.

Cheers

Steve Bush
www.music180.com/pros/5887

2 x Systems: MacPro 4.1 (Nehalem) 2.26 8 Core, OSX 10.6.8, PT10HD, 14 Gig RAM, PCIe HD3, 192's, Sync I/O, Midi I/O.

[Ale]

Thanks Bushpig

Did not know this.

Sorry for coming with an old issue
I did a search before, but did not find anything.

Ale

[Numi]

I am having this problem too. I recently received a project to mix from a friend and upon changing the inputs to (No Input) and saving.. when I reopen the project I get a message saying the same old thing about the inputs not being there that were on his rig even though I saved "No Input" on all those Tracks. Then it proceeds to somehow remember what his input settings were and puts them back to that greyed out. Not a huge deal, just annoying.

[[email protected]]

Workaround doesn't work for me... I assign existing IO to the 'bad' inputs, save the session, then save as a new one. In the new one, I assign NO Inputs and keep working. Next time I open the session, the 'bad' inputs are back.
Anyone else?

[LarsSlate]

I am surprised they have still not fixed this. I have 10.3 and new system just setup this week and I have that issue.

[MixerGuy]

Jan 2015 - same bug STILL HERE

PT HD 10_3_9

Mac 10.8.4