Issue w/ Pro Tools 10 upgrade - input/definition path errors (?)

[FreshBlue]

Clean install of Windows 7.. (created system image prior to install)

Installed Pro Tools 9 from DVD-ROM - had hardware firmware/drivers up to date

* Authorized iLok licenses, downloaded 'Pro Tools 10.2 installer' and 'Virtual Instruments'

Uninstalled Pro Tools 9 w/ HD Driver

Installed Pro Tools 10.2

Installed Virtual Instruments

(Restarted computer after every install/uninstall)

--

I open a blank session template, save session w/ no edits - reopen it, and loads the program with no issues (plug-ins, DAE etc.), but when its loading the saved session - restoring tracks; activating inserts it is prompted with the following message:


'Session Notes:
Some paths were made inactive because they could not be assigned to existing path definitions.

Would you like to save a detailed report?'

.txt report
'----notes-----missing stems--- the input path "A 1" was made inactive because its stem is missing.The input path "A 1" was made inactive because its stem is missing.The input path "A 1-2" was made inactive because its stem is missing.The input path "A 1-2" was made inactive because its stem is missing.he input path "A 1" was made inactive because its stem is missing.'

* The only thing I adjusted after installing Pro Tools 10 was relocate the directory for Xpand plug-in w/ new folder

- does anyone have any idea what is causing this and how to amend?

Thanks in advance

[martthie_08]

Some paths were made inactive because they could not be assigned to existing path definitions.

I get this error message on 90% of all the sessions I am working on nowadays, sometimes I/O paths get messed up and I feel really insecure when doing mix recalls. This came after moving from PT9 to PT10 on Mac OS 10.6.8, so kind of the wrong forum section, but just wanted you to know that I am having issues too on the other side, really frustrating...

[FreshBlue]

bump

Anybody? Still encountering the same issues

[uQbar]

Originally Posted by FreshBlue

bump

Anybody? Still encountering the same issues

Is it really an issue or just a nuisance message? Has it impacted your work in any real way?

I get the same errors, but all they seem to indicate is that under the new install my input paths are named differently. Not really an issue since, if I go to record, I just select the appropriate new path name from the list and record enable.

[albee1952]

For me, its just a nuisance message. Sometimes, opening Setup>IO and clicking on the Buses tab; scroll down the right side of the list and look for anything in italics. Uncheck those. Look at your IO settings across the MIX window and anything that is grey'd out, I would change to something that works, or to none(if you don't need an input for a track that's already recorded). As said, sometimes it because I have renamed inputs or outputs(constantly fine-tuning my setup). In any case, I never bother with a detailed report

[Bill@Avid]

Hi,

There was a change in the default settings for the preferences in the I/O Setup dialog between version 9.x and 10.x. In 9.x the preference "Sessions overwrite current I/O setup when opened" is selected by default this changed in 10.x and it is now no longer selected. This may account for the behavior you are seeing from a fresh install of 10.x and why you are getting the notification about your I/O changing.

If you are opening existing sessions or creating sessions from a template and are receiving warning that tracks do not have a valid input or output look in Setup>I/O Setup and try it again with "Sessions overwrite current I/O setup when opened" is selected. This may get you back to what you were used to seeing.

Hope this helps