OMG WHY IS IT SOOOOO HARD TO DELETE PLUGINS ON MAC???!!!!
- Thread starter Blend30
- Start date
johnathansmith1969
Member
I am having the same issue I have two versions of winsocket and can’t find them
MrDapperSam
New Member
I don’t have the OBS-studio file in Application Support. Where would it be?
Babs Johnson
Member
Like szxly1 said : on Terminal: cd "/Library/Application Support/obs-studio/plugins/" or click on finder, then click "Go" in the top menu bar and select "Go to Folder" and past this - Library/Application Support/obs-studio/plugins/
swaenboutu
New Member
Hey thanks for the answers here. I still have an issue, I have deleted the plugins directory but, every time Lunch OBS, the directories are automatically recreated. Is there a step I've missed and I need to do before deleting the directory?
Richywarbucks
New Member
Hey so what helped for me is going to
User/Library/Application Support/obs-studio/plugins!
to reveal Library in the "User" folder click View, Show View options, and check "Show Library Folder"
User/Library/Application Support/obs-studio/plugins!
to reveal Library in the "User" folder click View, Show View options, and check "Show Library Folder"
Zachary Crespin
New Member
I had some issues recently and I was able to find my plugins by going to "File" > "Show Settings Folder" inside of OBS
Lawrence_SoCal
Active Member
'cuz Apple and their walled garden ... seriously, that is why
And things are getting worse on Windows desktop OS side as Microsoft copies some of Apple's 'hide stuff from users so they don't mess it up' approach...
In this case, some of the posts above mention how to get around hidden file/folders structures. Same can happen on Windows OS side with NTFS permissions and user/admin rights, and default File Explorer views.
It’s a sensible approach. Most computer users are completely ignorant of system workings and should be let nowhere near. After 30+ years dealing with this kind of stuff it is better to keep things that can destroy computer operations out of reach of people who don’t know (or care to know) how it functions.
Walled Gardens save computer lives! (Or something like that).
You can still access it if you know what you’re doing but setting fences high is a good thing.
As you say, even Microsoft is doing it now. The approach works. Most people are not techies.
Lawrence_SoCal
Active Member
Oh I get it.. believe me as I also have many decades of experience in this and am well aware of the well-deserved IT Tech support acronyms for typical users. That said, there are times when that 'help/approach' gets in the way of reasonable (and sometimes necessary) actions ... no right answer
Jicori
New Member
I landed here looking for answers to these same concerns on my macOS Sequoia system running OBS. I dropped to a terminal and did a gren un the obs-studio directory/folder to look for where OBS code was still making reference to "ndi" and found some things in the obs-browser cache. See the following screenshot:
View attachment 116799
So, even though the plugin itself was removed, the OBS browser source was still depending on it. I had no Browser Source items configured in any scenes or profiles in OBS, though, so it was holding on to cache it didn't need.
What I did next was make sure OBS was closed, then removed both the "9761A96F922CBC77" subdirectory under the obs-browser directory, then removed those three specific files mentioned under Cache_Data. I honestly didn't care if I was going to break OBS. I'd saved my scenes and figured I would reinstall if needed.
When I reopened OBS, it still gave me the warning. I then changed up my grep to make "NDI" all caps and found a few more files to delete.
View attachment 116800
With reckless abandon, I repeated closing OBS, deleting the listed files, and attempting to reopen OBS again. But, alas, it's still giving me the warning.
So, it's not something in the OBS directories at all that's causing this on my macOS system, or at least not a text file that I can search with grep. I decided to take a look at my dotfiles (hidden files) in my home directory, and I did find a ".ndi" directory there (~/.ndi). I moved it to "ndi-backup" so it wouldn't be read as a dotfile/config file, and tried a third time to open OBS. Also unsuccessful.
I admit I'm at a loss now. No idea why the plugin browser is still showing a plugin that is not installed, not referenced in any source, and not even appearing in the OBS application's directory (at least not within a text file).
If I discover anything new, I'll return and post. Otherwise, assume I did some aggressive uninstalling and deleting of files to get this working again.
View attachment 116799
So, even though the plugin itself was removed, the OBS browser source was still depending on it. I had no Browser Source items configured in any scenes or profiles in OBS, though, so it was holding on to cache it didn't need.
What I did next was make sure OBS was closed, then removed both the "9761A96F922CBC77" subdirectory under the obs-browser directory, then removed those three specific files mentioned under Cache_Data. I honestly didn't care if I was going to break OBS. I'd saved my scenes and figured I would reinstall if needed.
When I reopened OBS, it still gave me the warning. I then changed up my grep to make "NDI" all caps and found a few more files to delete.
View attachment 116800
With reckless abandon, I repeated closing OBS, deleting the listed files, and attempting to reopen OBS again. But, alas, it's still giving me the warning.
So, it's not something in the OBS directories at all that's causing this on my macOS system, or at least not a text file that I can search with grep. I decided to take a look at my dotfiles (hidden files) in my home directory, and I did find a ".ndi" directory there (~/.ndi). I moved it to "ndi-backup" so it wouldn't be read as a dotfile/config file, and tried a third time to open OBS. Also unsuccessful.
I admit I'm at a loss now. No idea why the plugin browser is still showing a plugin that is not installed, not referenced in any source, and not even appearing in the OBS application's directory (at least not within a text file).
If I discover anything new, I'll return and post. Otherwise, assume I did some aggressive uninstalling and deleting of files to get this working again.
Jicori
New Member
Okay, I tried to edit my previous remark, but it apparently timed out... sorry about that. Here's the UPDATED version of that previous reply:
I landed here looking for answers to these same concerns on my macOS Sequoia system running OBS. I dropped to a terminal and did a grep under the obs-studio directory to look for where OBS code was still making reference to "ndi" and found some things in the obs-browser cache:
$ cd ~/Library/Application\ Support/obs-studio/
$ grep -i -r '*ndi*' .
The result was a bunch of files in various places. With reckless abandon, I closed OBS and deleting the listed files. Unfortunately, I'm still getting the warning on start and seeing this grayed-out plugin in my plugin browser that I can't do anything with.
Since some folks are saying they uninstalled and reinstalled and it was still there, I looked at the dotfiles (hidden files) in my home directory to see what configuration files/directories might be contributing to this. There was an .ndi directory there, and I moved/renamed it, but that made no difference. I'm not sure what else in my home directory might be contributing to this. It may take further investigation.
If I learn anything new, I'll return here and update you all. If I don't return, trust that I likely aggressively uninstalled and stripped out code until it worked again.
I landed here looking for answers to these same concerns on my macOS Sequoia system running OBS. I dropped to a terminal and did a grep under the obs-studio directory to look for where OBS code was still making reference to "ndi" and found some things in the obs-browser cache:
$ cd ~/Library/Application\ Support/obs-studio/
$ grep -i -r '*ndi*' .
The result was a bunch of files in various places. With reckless abandon, I closed OBS and deleting the listed files. Unfortunately, I'm still getting the warning on start and seeing this grayed-out plugin in my plugin browser that I can't do anything with.
Since some folks are saying they uninstalled and reinstalled and it was still there, I looked at the dotfiles (hidden files) in my home directory to see what configuration files/directories might be contributing to this. There was an .ndi directory there, and I moved/renamed it, but that made no difference. I'm not sure what else in my home directory might be contributing to this. It may take further investigation.
If I learn anything new, I'll return here and update you all. If I don't return, trust that I likely aggressively uninstalled and stripped out code until it worked again.