Clips suddenly referencing wrong audio

[Tim R.]

ADMIN EDIT:
This is fixed in v2020.3.
avid.force.com/pkb/articles/readme/Pro-Tools-2020-3-Release-Notes
avid.force.com/pkb/articles/Error_Message/Clips-linked-to-incorrect-audio

****************

I'm editing in a sumation of this thread's discussion at the beginning for those who might not stick through it to the end. It appears to be a particularly heinous bug that a number of users have now experienced:
1. Create session in 19.12 (from template or not)
2. Import session data from another session that had last been saved in a PREVIOUS version of PTs
3. Work happily for as long as the session stays open
4. Close session/reopen session
5. Get warning "Some clips had invalid bounds and were adjusted or deleted"
6. Now many clips in the imported tracks refer to the incorrect audio files, or have just been deleted.

There is NO way to recover the tracks that have corrupted. You can't "save copy in" (this crashed PTs every time in my case). You CAN import remaining tracks (that weren't imported in step 2) into a fresh session to salvage THAT work.

To AVOID the issue (I think), is to open all sessions in current version and "save as" before you try and import session data between them.

Bellow is my original first post:

I was working on a session. Closed and opened a different session. When I returned to the first session I got a warning dialogue "Some clips had invalid bounds and were adjusted or deleted". Now a number of clips in the session (that were imported from a different session originally BTW) are playing the wrong audio, or have been deleted. All indications in the clip list and clip info say it is the right audio, but they are pointing to the wrong files. Dug into the session backups and all appear to be corrupted as well. Anyone else experience this?

[Tim R.]

Happened again in new version of the same session. Doing more testing now.
UPDATE 1: "Save Copy In.." command crashes Pro tools every time. Trying to import tracks to new session now.
UPDATE 2: Imported into new session and appears to have resolved the issue for now.
I've attached a pic of the clips list to show what it is displaying.

[Tim R.]

Bump. Anyone know of a way to re-point a clip to the correct file?

[Ale]

You could try:
Put the wrong referenced files into a separate folder.
Protools does not find them anymore on session load.
Do relink manually. Let pt search by id or name in the folder where the right files are (and only in this folder). When pt found the file then relink it. You can also try to put the correct files into a new folder before relinking.

The problem is that protools if you saved over the session has maybe also the wrong file Id saved so relinking would only work when you search by name.

Ale

[SFXgeek]

Just had this happen too and it is very troubling, just updated recently to 2019.12 and now having tons of import audio issues.
This one was a session in our edit room which i had just opened multiple times in the edit room, then imported the session data into our mix room and on import gave the message about " invalid bounds etc.." same message as this user is reporting and it replaced a bunch of audio within the session. Did not save, went back into the edit room and now the edit room session is giving the same message and we now have lost a lot of work that is due to be mixed tomorrow!!

[Tim R.]

Originally Posted by SFXgeek

Just had this happen too and it is very troubling, just updated recently to 2019.12 and now having tons of import audio issues.
This one was a session in our edit room which i had just opened multiple times in the edit room, then imported the session data into our mix room and on import gave the message about " invalid bounds etc.." same message as this user is reporting and it replaced a bunch of audio within the session. Did not save, went back into the edit room and now the edit room session is giving the same message and we now have lost a lot of work that is due to be mixed tomorrow!!

Ugh. Was hoping this was an isolated issue. I had thought perhaps it might be related to naming a track with a "/" in the name, which I thought was a no no (and the app prohibitted), but it allowed me to do it this time. I'm bouncing stems (DX/MX etc) to be safe, and now may bounce back to my previous version (12.4 I think it is) since someone else is experiencing same problem.

[SFXgeek]

I have a feeling it may be that I was running 2019.10 when I created the session and was working on the session, then updated to 2019.12 and then opened the session again and continued working and somehow it doesn't like that session now.
Also had issues after upgrading a couple machines to 2019.12 and tried importing "session data" from the 2019.12 machine into a machine running 2019.10, it couldn't find any of the audio even if I pointed the "Relink" to the exact piece of audio, would only accept the file if I told it to only match Names which is really unreliable as it tends to grab wrong audio sometimes. Relink using the UIDs is really the only safe way to go but won't work.

[SFXgeek]

Just working on a 2019.12 session and went to import clip group (which was created in a 2019.10 or earlier session) and got this message (see attached JPG) after that message came up I got that other dreaded message and now a bunch of my clips are referencing the wrong audio!!!!

[MikeReganNoise]

This seems like a similar issue to something I've run into running 2019.10 (and.6) and Mac OS Seirra 10.12.6.

Here's a link to a thread from earlier this year. I hadn't experienced the error most of the year until it happened again to me today. The main symptom is a corrupt session file and several corrupted back ups. The corruption is evident by the size of the session file back up. After the error, it's much smaller than before. All of the back ups have missing audio and/or clips addressing the wrong audio, but there is no way to re-link anything.

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

[Tim R.]

Originally Posted by MikeReganNoise

This seems like a similar issue to something I've run into running 2019.10 (and.6) and Mac OS Seirra 10.12.6.

Here's a link to a thread from earlier this year. I hadn't experienced the error most of the year until it happened again to me today. The main symptom is a corrupt session file and several corrupted back ups. The corruption is evident by the size of the session file back up. After the error, it's much smaller than before. All of the back ups have missing audio and/or clips addressing the wrong audio, but there is no way to re-link anything.

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

Thanks for chiming in Mike. After reading your other thread I noticed a smilarity in that my corrupt session also had tracks imported from a coworkers session (not outside the US though). Those imported tracks were the problematic ones that had clips pointing to wrong audio. SFXGeek, can you confirm a similar scenario with your problematic session?