M4 Mac Issues

[Darryl Ramm]

Originally Posted by SomeOtherGuy

Getting this message. Can't open the file after working all day on it.

"Could not complete your request because Assertion in "/Users/autobld/gitlabci/PT_COLOR/ProTools/App/Tracks/UTrackList.cpp", line 1551.

(Use the Copy button to copy this message to the clipboard.)"

On an m4? Can you *please* open a support case with Avid and post the incident number here. Any problems opening a case please speak up. It would be really great to make sure Avid captures any needed info. Maybe make a complete copy of the whole session folder and don't touch that copy it in case Avid wants that or parts of it, and anything else you do might "fix" the problem.

If you import that session into a new session can you get going again? I'd also try moving all plugins out of the plugin folder, trashing prefs (use the latest PT Prefs 2). Can that now at least open the session?

[SomeOtherGuy]

Will do. Yes, this is on a M4 MacBook Pro, 128 GB RAM, 8 TB SSD internal.

[SomeOtherGuy]

and yes, importing tracks into a new session was initially successful, but then it crashed PT and won't open.

[SomeOtherGuy]

Had a feeling this issue for me was caused by a bad plug-in. I removed REV6000 Cinematic Reverb from Relab Development and it solved the problem. I was able to open the session.

[Shadow Puppets]

That is the exact same error that I keep getting (word for word), in the exact same scenario… opening the project. Same as you, importing into a new session initially worked but then the error returned. I also initially thought I’d fixed it by removing some plugins, but then it returned again. It happens to me on completely empty sessions now too.

[Darryl Ramm]

Originally Posted by Shadow Puppets

That is the exact same error that I keep getting (word for word), in the exact same scenario… opening the project. Same as you, importing into a new session initially worked but then the error returned. I also initially thought I’d fixed it by removing some plugins, but then it returned again. It happens to me on completely empty sessions now too.

Have you tried to move *all* plugins out of pro tools plugin folder, then trash prefs (using the latest version of PT Prefs 2.. just want to make sure the new style plugin caches all get whacked) and then restart and see if this happens with only the Pro Tools core plugins installed (that get reinstalled when Pro Tools restarts). I'd also try fully restarting Pro Tools each time you see this problem (why: see ASLR comments below, each restart gets things laid out inside Pro Tools memory in different places).

These sorts of assets that seem to strike some users and not others worry me, one guess/fear here is we have a plugin related problem (which does not mean a coding error is in the plugin, it may be in Pro Tools) where stuff scribbles over memory, maybe just leaking a little bit past some data structure and then an assert is fired because of that corrupted memory. Those problems can be really hard to track down, can change depending on things like Address Space Layout Randomization (ASLR), can seem to change or be hard to reproduce for the most unrelated stupid reasons. All reasons why it's great if we can get logs and crash dumps etc. to Avid support, anything their engineering folks ask for.

ASLR can be an especial thorn in the side (ok ass) with memory corruption problems, one reason to try fully restarting Pro Tools and see if that seems to work better.

I have had this same assert going back several versions old PT on a Intel Mac and it hit me for a while and then I was never able to reproduce it. Like adding an inst track in a very small session and IIRC once just creating a session. And then nada, never saw it again. And it's possible there are multiple unrelated things that cause this particular assert to fire.

[Eric Lambert]

Originally Posted by SomeOtherGuy

Had a feeling this issue for me was caused by a bad plug-in. I removed REV6000 Cinematic Reverb from Relab Development and it solved the problem. I was able to open the session.

VERY interesting. And good job finding that.

[Eric Lambert]

Originally Posted by Shadow Puppets

That is the exact same error that I keep getting (word for word), in the exact same scenario… opening the project. Same as you, importing into a new session initially worked but then the error returned. I also initially thought I’d fixed it by removing some plugins, but then it returned again. It happens to me on completely empty sessions now too.

Is there anything different about the session specs of the existing session and the new one? Sample rate, audio file type, bit depth, video frame rate -- are all these the same in both sessions?

It's as though something about the new session was changed during (or after) the import and PT doesn't like it. And by no means would the change be limited to only those things listed above.

[SomeOtherGuy]

Confirming that after completely removing REV6000 Cinematic Reverb plug-in from Relab Development, still no more Assertion errors with that PT file. I alerted Relab but so far have not gotten a response.

[thin ice]

Originally Posted by SomeOtherGuy

Confirming that after completely removing REV6000 Cinematic Reverb plug-in from Relab Development, still no more Assertion errors with that PT file. I alerted Relab but so far have not gotten a response.

They spent years getting that plugin out, so it would be a difficult one to take.