View Single Post
  #6  
Old 07-03-2022, 02:10 PM
Darryl Ramm Darryl Ramm is offline
Member
 
Join Date: Nov 2010
Location: USA
Posts: 19,657
Default 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.
Reply With Quote