2019.12 import issue

[SFXgeek]

We upgraded a couple of our systems to 2019.12 to test them out and came across an issue of importing a session created in a 2019.12 system to a 2019.10 system. Every time we tried importing we would get the message that all the audio was missing which we would then choose to manually locate the files, we could point the relink to the exact folder and see that the UIDs were exactly the same but relink would still say it couldn't locate any. The only way we could get it to recognize the files was if we only selected to "match names". We tried this with the files located on a server and also with the files copied to a local drive with the same result. The systems running 2019.12 are High Sierra, and the systems running 2019.10 are Sierra, not sure if that has anything to do with it. Has anybody else had this issue?

[peterle]

i cannot comment on 2019.10 regarding opening 2019.12 files,
at least my 12.7.1 (HD) on Windows 10 opens 2019.12 (Ultimate,Mojave,HDX)
fine. So the problem may be at 2019.10 and not 2019.12.

[bluskiff]

Figured out I was trying to import 64 bit files out of cubase. Went back changed the cubase session to 32 bit rebounced the file protools imported it perfectly.

[ehaber]

Yes, I've had the exact same problem with the Pro Tools at my desk at work which was 2019.10. To solve it, I upgraded to 2019.12. I did find in the release notes for 2019.12 (http://avid.force.com/pkb/articles/e..._US&fs=Searc_1) the following bug fix which may relate:
"Fixed an issue where some Wav (OMF) files would not display an ID in the Unique ID field, which would result in missing files when importing the associated AAF (PT-256790)"

[Ale]

Have a look to the sticky at the top of this forum and the possible workaround also explained on protools expert. Consider going back to 2019.6

Ale