Assertion in line 230 error Please help

[macdummy]

Hello Avid Pro Community,

Protools has been running well until recently.
I open a session and It runs fine, but, I can only create a new audio track. If I try to use the drop down menu to create a new Instrument track or midi track or master fader track I get this error:

Assertion in "/Volumes/Development/protools/release/2020/r1/ProTools/NewFileLibs/Sys/MacOS/Sys_FileLocMacOS.cpp", line 230.

I'm guessing it is a plug in issue?

Here's what I have tried: Restart, Update protools, I also gave read and write permission to my documents folder as instructed by this avid knowledge base answer i found.
Here is a link https://avid.secure.force.com/pkb/ar...on-in-line-230
Any Ideas? I haven't tried to "trash preferences" can someone instruct me on how or if i need to try that.

Thanks in advance.

[Darryl Ramm]

First, welcome to DUC.

The thing when getting an assertion error is to always search (Google or maybe DUC search) for keywords in the error message. Almost all such errors will have solutions posted already on DUC or elsewhere.

Like the first hit on Google had you tried a search is ...

https://avid.secure.force.com/pkb/ar...on-in-line-230

[macdummy]

Thank you for the quick reply Darryl,

I did google the error message, I got the same results as you did.
I included the same link in my original post. Thanks for searching for me.

I did what the Avid knowledge base said to do, but the problem persists.

I did not however do the second part of what they said to do. moving the protools folder from documents to the desktop. I must say, i don't really understand the procedure. (can anyone explain it to me?)

Does this sound like a solution to you?
Any advice would be helpful.

Thanks again for the reply

[Darryl Ramm]

Doh sorry, I did not see that part of you reply, missed it on the bottom of my iPhone. What version of Pro Tools are you using and on what macOS version (still Mojave like your signature)?

BTW that actual solution posted by Avid is totally brain dead from a basic security viewpoint. They should be frigging embarassed.

[Darryl Ramm]

I've tried to reproduce that problem on Pro Tools 2020.3 standard on Mojave and cannot. Not at least from folder or file permissions in the session folder and I also tried messing with the ~/Library/Application Support/Avid folder permissions. I just can't make this assert happen, maybe Avid addressed this issue after whatever version you are running.

I've sent a message that will hopefully get through to Avid folks that this knowledge base article is awful, it is just dangerous from basic file security view point to be telling users to make all their files and documents viewable to everybody. Also I expect the note there about this appling to Ultimate (only) is a mistake.

What I would try in your case is to move the session someplace else, but first trash prefs and see if that helps. Use Pete Gates' utility here http://petegates.com/pg-pt-prefs.html. You always want to start troubleshooting by trashing prefs.. see if that fixes anything. If not then...

If your session folder before was say called foo in your Documents folder then in Terminal type ($ is the bash shell prompt, you don't type that).

$ cd ~
$ mv Documents/foo .

Try to run Pro Tools and then use File>Open Session to find that foo session in its new location (would normally be in <your home directory>/foo/foo.ptx).

Open this session and seeing if it works. If not I can you run this (change "foo" to the name of your session folder).

$ cd ~
$ find foo -exec ls -ld {} \;

And paste the output of that command here. If somethign looks out of whack there I might be able to suggest other stuff to try.

I am also curious if you are just running an old version of Pro Tools not supported on Mojave. So what exact version are you running?

[macdummy]

Thanks again Darryl for being so responsive. I really appreciate your time.

Sorry, I was away from my computer today. I am using PT 20.5.0.207 most up to date version. The rest of my stats are in my signature.

I will try trashing my prefs tonight. using the link provided.

Could this be the problem?
My mac book pro is relatively new, got it in February.
Somehow I had created 2 users?
My name as a user(administrator) and i had another folder with another name i've used.
One Documents folder sits in the side dock. part of icloud i think. contains a protools folder with plugins etc.
and i also had a documents folder in the other user's folder. with a protools folder.

could this be the conflict??

[macdummy]

Thanks again Darryl for the replies and your research. I appreciate your time.

I am running ProTools 20.0.5.270 the latest version of PT.
The rest of my stats are in my profile.

I will try to trash my prefs using the link to the program you provided. Thank you.

could this be a problem?
My MB pro is pretty new. I got it in February. Somehow, I've created 2 users.
My name, Is the administrator folder. It has a documents folder in the sidebar that contains a protools folder with plugin maps preset settings etc. i think it is part of icloud.

Another user folder with a nickname i use. It also contains a documents folder with a protools folder that has plugin maps, preset settings etc...
Maybe this is causing the issues?

[Darryl Ramm]

Originally Posted by macdummy

Thanks again Darryl for the replies and your research. I appreciate your time.

I am running ProTools 20.0.5.270 the latest version of PT.
The rest of my stats are in my profile.

I will try to trash my prefs using the link to the program you provided. Thank you.

could this be a problem?
My MB pro is pretty new. I got it in February. Somehow, I've created 2 users.
My name, Is the administrator folder. It has a documents folder in the sidebar that contains a protools folder with plugin maps preset settings etc. i think it is part of icloud.

Another user folder with a nickname i use. It also contains a documents folder with a protools folder that has plugin maps, preset settings etc...
Maybe this is causing the issues?

Sure it might be a problem.

What do you mean by "My name, Is the administrator folder"? What are you looking at? Do you have a user called "Administrator" with a folder /Users/Administrator? And you have a home directory under that user's home directory?

Now I even more want to see what are in your session folders.

So logged in as the user you are trying to run Pro Tools as. Assuming your session folder is named foo and is under your Documents folder, then run this in Terminal and paste the outputs here.

$ id
$ cd ~/Documents
$ pwd
$ find foo -exec ls -ld {} \;

What does Systems Preferences > Users & Groups show for both users? Do they both show up there with Admin privileges? Post a screen shot if not sure.

Why did you create these two account? Do you remember what you were trying to do/how this happened? You probably should be fixing this regardless and removing one of the accounts.

[macdummy]

Ha.Darryl forgive me, I'm hanging on by a thread, but I can do this.

I'm definitely a musician and not the recording engineer/computer guy, so bear with me.

I dont know how i did it. but. What i believe is my real home folder. has a house icon. uses my name T********

I also had another folder under users that said T's macbook pro. it had a documents folder in it that had a protools folder with preset settings etc

I copied it to an external and I deleted it. Now i only have one user.

I've enclosed a photo of what my user folder looks like.

I'm gonna try and cut and paste the terminal thing and send you the results now.

my session file is named PRO TOOLS SESSIONS so i assume i replace the foo with that?

[Darryl Ramm]

Maybe hang off deleting any stuff and just give me the output of the commands in Terminal I asked for. I want to see which user owns all these files.

In the screenshot you attached there is no Documents folder for your user account. What happened to that? Where are your sessions actually stored?

You have both Dropbox and OneDrive folders, I hope your sessions are not in either folder (you can copy backups to those folders, you should not be running sessions from them).