Assertion in "UTrackList.cpp" file

[viaspiaggia]

adding to the list here, will submit a bug report shortly.

Not every time, but often when duplicating or adding tracks, especially within a basic folder, I'm getting the following error

Assertion in "/Users/autobld/gitlabci/PT_COLOR/ProTools/App/Tracks/UTrackList.cpp", line 1551

Sometimes I can save and quit PT, but often I get a spinning beachball and have to force quit. Once in a blue moon the tracks are actually there after a restart of PT, but usually not. A fresh boot usually allows me to make the track and move on.

PT Ultimate 24.10.1
Mac mini M4 Pro (16,11) 48GB RAM
Sequoia 15.2

[jambander]

same issue. I get the same error message you mentioned, "/Users/autobld/gitlabci/PT_COLOR/ProTools/App/Tracks/UTrackList.cpp", line 1551 and the session completely freaks. Every time I try to commit a track it triggers this behavior.

Plz Avid, fix this.

[Darryl Ramm]

Originally Posted by jambander

same issue. I get the same error message you mentioned, "/Users/autobld/gitlabci/PT_COLOR/ProTools/App/Tracks/UTrackList.cpp", line 1551 and the session completely freaks. Every time I try to commit a track it triggers this behavior.

Plz Avid, fix this.

And absolutely no info about your system or any troubleshooting you have tried.

Especially if an M4 system then have you tried the workaround of running under Rosetta? Even if some other Apple Silicon processor I'd try that.

There is a lot more info in other threads specific to the M4 on DUC, including https://duc.avid.com/showthread.php?t=430144&page=16

And especially if that does not help, then get a case open with support. Provide any log/trace info they need and push to find out if this is covered by one of the known bugs or is something different. Getting the same assert error does not mean the same root cause, it might, it might not.

[Brettster]

Getting this same error every time I try to "cut time" or "add time". Never once gotten this error before 2 minutes ago, and it's on every session I open now.

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

[Darryl Ramm]

Originally Posted by Brettster

Getting this same error every time I try to "cut time" or "add time". Never once gotten this error before 2 minutes ago, and it's on every session I open now.

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

Andddd.... what exact Mac are you running on?

See my immediate prior comment in this thread.

[fredmant]

I am and have been receiving the following assertion error re-opening a master template that I am building. There's little to no audio recorded in the session. My profile says this, but I'm Mac Mini Sequoia 15.4.1 M4 Pro 14 core 2TB 64GB PT 2024.10.2 - I don't use/want Rosetta.

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

At first I thought the problem was being caused because I would save the session, then close PT, without closing the session. But now I've encountered the error again with closing the session before closing PT, upon re-opening PT.

Following advice online, it was suggested re-opening a backup would restore things. This worked.

Also suggested, was opening a new session and importing from the seemingly corrupted session. This also worked (sometimes I believe, it didn't, but my memory is foggy and I wasn't keeping notes at the time).

If I choose to ignore the error and PT stays open, I find that I cannot even create a new session. Instead PT freezes at the "Building Mix Window" phase.



So does this mean that without a session loaded, PT has got some bad memory issues? Hopefully this is a clue.

I have sent this latest info to PT via a dialog box that comes up when PT crashes just now and offered my assistance in debugging.

In the meantime, without a reboot, I am able to start PT and open the session that caused the Assertion error, without importing, without going back a few sessions.

I wish PT would figure out what is causing the problem, or at least offer a "details" button to expose some of the memory stack values or variable names, whatever, that would make this more useful to the community in troubleshooting.

Originally Posted by Darryl Ramm

And absolutely no info about your system or any troubleshooting you have tried.

Especially if an M4 system then have you tried the workaround of running under Rosetta? Even if some other Apple Silicon processor I'd try that.

There is a lot more info in other threads specific to the M4 on DUC, including https://duc.avid.com/showthread.php?t=430144&page=16

And especially if that does not help, then get a case open with support. Provide any log/trace info they need and push to find out if this is covered by one of the known bugs or is something different. Getting the same assert error does not mean the same root cause, it might, it might not.