Assertion : utickunit.cpp", line 149.
 

Hello, I have to go back to Pro Tools and I'm happy with its qualities, but I also find its bugs...

Context: Multi-track Midi clips with real-time properties.
Action: Alt-4 (pad): Write on clips.
Message: Assertion in "d:\ protools\ release\ 2020\ r3\ protools\ app\ element_properties\ utickunit.cpp", line 149.

I tried everything: clear preferences, import tracks into new sessions, disable instrument plugins, remove my interface from Windows audio preferences (Atlas Prismsound), reinstall Pro Tools and then reinstall my driver. + Simplify my MIDI track by removing the clips already modified. Nothing to do.

Thank you for helping me. If possible!

(AMD, Win 10, PR Vanilla 2020.7) Correction: PT STUDIO 2022.6

Re: Assertion : utickunit.cpp", line 149.
 

Really no one can help here? While using realtime MIDI editing on clips, every 5 minutes Pro Tools freezes with this same message! What a waste of time!:mad:

I tried everything, delete preferences, export session, re-import tracks, etc. It always comes back. It always comes back.

Re: Assertion : utickunit.cpp", line 149.
 

You are on an old version. This potentially is fixed in the latest as a bug. So that leaves no one to "help you" other than to say go to the latest.
This isn't surprising -- how the software world works now.

Re: Assertion : utickunit.cpp", line 149.
 

Are you on 2020.7 or 2022.6?????

What is “PR Vanilla” you mean Pro Tools standard? Pro Tools Studio? Pro Tools Artist?

Re: Assertion : utickunit.cpp", line 149.
 

Sorry, this is a mistake. I'm on the last version of Studio: 2022.6.

And the bug is there.

Re: Assertion : utickunit.cpp", line 149.
 

The best thing with assert errors is to google them. And find out what people did in the past to solve or if the bug was fixed etc... e.g. Google

Assert "utickunit.cpp"

which in this case turns up nothing except your error. So no go there, and maybe it's a new bug introduced from all the changes/other bug fixes done to MIDI recently (which means you might try this on 2021.12 or 2022.4 to see.. even if not to run on that might help Avid engineering fix the issue).

If you tried before importing the MIDI into a new session, probably the only other thing I'd try is starting with a completely empty session and not importing anything and try to replace it there.

But even if a previously unknown ASSERT the nice thing is it should be relatively easy for Avid engineering to make progress on. They might want/need other log information, or a copy of the session from you, so at this point file a support case and get them the info needed. Hopefully support won't waste your time too much going over what troubleshooting you've done already. I'd really get that report in now while Avid seems to be focusing so much in improvements in MIDI.

Re: Assertion : utickunit.cpp", line 149.
 

Okay, I'll do that. Note that this is a problem I've had with earlier versions. But this is worse than ever. I can barely work (as far as I work with these functions). Anyway, I'm making a ticket to the technical support.

p.s. Maybe you can see this yourself: take a complex midi file. Copy it to 3 tracks (or more). Change the real time properties of the track. Then go and randomly change the realtime properties of several clips on the 3 tracks. Try to compute, as if you were hours editing to find what you want. At some point, Pro Tools can't take it anymore. And if you try to simplify at that point, it doesn't work anymore. There's something in the file that's corrupted forever.

Re: Assertion : utickunit.cpp", line 149.
 

It's unusual you've had this for a while on other versions and there are no posts from other users findable on Google. Do all the past ASSERT occurrences all name the exact same file "utuickunit.cpp"?

Don't worry about the file path or exact line number. This is the C++ source code file that a developer has put an ASSERT macro in to check something, and it's failing that ASSERT test and deliberately crashing Pro Tools with this error.

Others not reporting it with that error message doesn't mean folks are not seeing it. I just suspect here are very few user making much use of real-time MIDI effects. But maybe it's something in your environment or workflow tripping stuff up. All good reasons to start a support case.

Re: Assertion : utickunit.cpp", line 149.
 

Naturally, the first thing I did was to Google. Nothing. I'm alone in the world with this assertion. But as you say, it may be more general if we stick to the essential message.

I make extensive and complex use of the real-time options in Pro Tools. Pro Tools doesn't have a good reputation at MIDI, but that's not fair. It offers unique, intelligent and very well done features. The only problem is when it crashes. It seems to me that since I bought an AMD computer, it's worse. We'll see.

Thanks for your support.

Follow-up: The technical support is informed, with all the usual elements. I am surprised at the speed of the response. I am told I will hear back on Thursday (the technical meeting is Wednesday).