ProTools 12 Open Session Assertion error

[bakydd]

I just installed ProTools 12 and every time I open a session, it errors out and displays the following message:

Could not complete the Open Session... command because Assertion in "..\ ..\ Sys\ Win32\ Sys_VolumeWin32.cpp", line 237.


If I load the same session with ProTools 10, the session is just fine. Any idea how to resolve this issue.

Thanks

[djdopus]

I am having a similar error, ending in line 339:

Sys_FileLocUtilsWin32.CPP Line 339
no Idea why or what they cause is yet.

[Southsidemusic]

Just a quick question, what windows versions do you guys have?

[kanyehobbitkind]

Has anyone found a fix for this yet?

I've just installed Pro tools 12.1 upgraded from 8 onto 17- 64bit windows 7 PC's and it comes up with the error message 'Assertion in "..\..\Sys\Win32\Sys_FileWin32.cpp" , Line 422.

and nothing i've tried will fix it, Avid didn't have a clue when i rang up to ask for help and the deadline to get this fixed is vastly approaching.

any help would be appreciated,

Thanks.

[kanyehobbitkind]

Managed to get the previous error message off but now it comes up the same as the OP's error message

Could not save "" because Assertion in "..\ ..\ Sys\ Win32\ Sys_VolumeWin32.cpp", line 341.

Again any help would be amazing

Thank you

[guitardom]

Assertion errors are typically due to either a corrupted session, a corrupted install, or bad luck. If you are having session specific issues, try creating another session and import the tracks in 1-2 at a time. If it is all sessions, uninstall PT, clean up the registry and junk files with a utility like ccleaner and try again.

[GoGoJoe]

Corrupted session? how does it become corrupt and also i get this error but it's not session specific. It's happening on any session i try to open. I haven't changed anything from the moment it was last working until now. Just time in between.

[Nirvana5253]

Every time I've had an assertion error it's because the playback engine is set to something silly that freaks pro tools out. Might check that. Can start pro tools while holding down "N" to bring up the playback engine dialogue before any session loads - select the proper playback engine and then you're off.

[digi98]

Could be the switching sample rates issues as well. See threads on that - might need to create new session at new sample rate before opening existing session at new sample rate. Check Windows sound playback/recording tabs to either disable or set to same sample rate.

[Maesedonoso]

Hi everyone,

I'm very new here. This is actually my first post. And I wanted to join you as I was having exactly the same problem. Found an answer in Duc but, even if it helped the other user, didn't help me.

But what Nirvana5253 said about holding N and changing the playback engine fixed my problem.

I'm using an Mbox3 Mini, and Pro Tools 12 was showing the same error. So I opened the Playback Engine and changed it to Build In. That fixed the problem. Or at least let me opened or create a session. But also showed me where the problem was.

Apparently I had to upgrade the drivers on the Mbox3 Mini. Did that and now I don't have any issues.

Hope it’s not too late for this reply.

Thanks