12.7 Install = Assertion

[Brian in Charlotte]

Yea, I did that and no luck. The only thing that has worked is: Upon launching ProTools initially, I hold down the "N" key, then the dialog box appears whereby it has defaulted to "Pro Tools Aggregate I/O". I then change it to my correct interface and then each session opened after that is fine. If I do not do this, it will corrupt the initial session that's opened and never open it again no matter what the Playback Engine is.

[Darryl Ramm]

That assert has been seen a little in the past. It is very likely complaining about low-level audio file corruption in the session.

Unless all your sessions are related/share content etc then it's hard to imagine this happening unless 12.7 is corrupting stuff or has done sort of complex bug. Do not just assume, check your sessions do not have shared audio source files and everything is neatly packaged in the session folder.

Those sessions that will no longer open you need to try going back to your backups/archives or start with just looking if the session audio is where you expect it to be and if those raw wav or aiff files play at all, next step is importing stuff into a new session.

See past threads like... http://duc.avid.com/archive/index.php/t-379471.html

[Brian in Charlotte]

Will do....thanks for the note! Happy New Year to you.

[GregoryGuns]

Hey Guys, So I'm getting this same problem BUT It's only happening on one song (of course one that needs to be done asap).

I just installed 12.7 and updated my Mac OS hoping it would work but no dice.

I've tried every option I see posted and nothing works.
Help? G

[Brian in Charlotte]

If you are having the issue whereby the session won't open, I'm sorry to say it is corrupted and it's gone - at least that's my experience. Any session I tried to open had to be trashed, no way I could find around it. I have had to hold down "N" on start up ever since and AVID doesn't give too hoots about it. VERY SORRY you had to deal with that.

[Stephen Bond]

I'm pretty sure I've seen a couple of these errors since going from 12.6 to 12.7. I'll grab a screen shot and stuff if it happens again.

Stephen

[TOM@METRO]

As Darryl mentioned, if you don't have backups, you can always create a new session and start importing session data from the corrupted one. Do a few tracks at a time, looking for the corruption. I've had to do this a few times in the past. It takes a little time, but you do wind up with a nice clean session.