7.2 BUG-Import (see error message) +region bin bug

[Charles Deenen]

(1)
Upon trying to import a music session from a contractor (which opens fine in protools by itself) into 7.2, I get the following error message:

assertion in /volumes/development/vbvd/AlturaPorts/PT4_app/MacBuild/../PtSess/PsSess_converter_5_1.cpp", line 990



(2)
Symptom: Protools gets confused about what file-name a file has

To reproduce:
- set bin to sort by date Modified
- Create or import a few files named 'Blah' (i.e. blah 1, blah 2 etc.)
- do a search for "BLAH" (make sure you have some files named blah1, blah2 etc.)
- record a new stereo or 5.1 file in protools
- name it 'blah 100'

now, notice that the newly named file PLUS the previous un-named file are in the region bin, and both get selected when you select the 'blah 100' region

- another search for 'blah' make that file go away.

Pretty damn annoying when you try to export files after a record.

-charles d

[Charles Deenen]

So after a bit more investigation, turns out that this sessions also won't load (sorry, I thought it did). So, this just changes the bug

Instead of being able to load the session and it gracefully bowing out, I got the above error-message.

-cd

[Halstein]

Got almost the same error when trying to save or quit after installing 7.2. Error message that started as yours, but ended up with line 164. Found the solution on the answerbase (and that had nothing to do spesific to the 7.2 update!) - you have to trash all your volume databases!! Remember that all your active drives (after using PT) got a "Digidesign Databases" folder. Trash the content in each of those folders!

Since the error refers to a volume fault, I just guess that this solution could work for you as well. Good luck!

[Charles Deenen]

DUH ! didn't even think to look there. Will try. I must be sleepy, that's what I've been telling everybody to do for years, and now it's biting me in the *ss and I throw up my hands...

lol !

cheers

-cd

[pat yacono]

Hey Charles, there is a music contractor right here whose sessions will not generate that error. Lol... How have you been?