OBS won't start in normal or safe mode after accidentally selecting virtual camera in settings. Getting segmentation violation

[qsg001]

I use OBS on a Macbook Pro which was working with my Elgato 4kx, but I accidentally selected the virtual camera while troubleshooting a problem. After I restarted OBS it is failing with a segmentation violation on startup. I have tried safe and normal mode startup, but neither work. I have also uninstalled OBS studio and re-installed. Same issue.

Any help resolving this would be appreciated.


Regards,
qsg001


Full Crash log can be found at pastebin: https://pastebin.com/HsArMbFF

The following is the header of the full crash log posted at the above URL:

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process: OBS [4894]
Path: /Applications/OBS.app/Contents/MacOS/OBS
Identifier: com.obsproject.obs-studio
Version: 30.1.2 (8576208847)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2024-04-24 11:35:20.5267 -0500
OS Version: macOS 14.4.1 (23E224)
Report Version: 12
Anonymous UUID: 6ED1D2DB-18B4-9A7B-807C-C48E853A82E5

Sleep/Wake UUID: 8E3EE800-6218-4EC6-BC7A-6BFD6F7166D3

Time Awake Since Boot: 32000 seconds
Time Since Wake: 55 seconds

System Integrity Protection: enabled

Crashed Thread: 9 Dispatch queue: session queue

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000328
Exception Codes: 0x0000000000000001, 0x0000000000000328

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [4894]

VM Region Info: 0x328 is not in any region. Bytes before following region: 4299062488
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 1003e8000-1007ac000 [ 3856K] r-x/r-x SM=COW /Applications/OBS.app/Contents/MacOS/OBS

 

[qsg001]

The problem is solved. The trick was:

1. open Finder
2. press Command-Shift-G or do Go->Go To Folder
3. paste in the following and hit enter: ```~/Library/Application Support/obs-studio/basic/scenes```
4. remove the .json and .json.bak files for your scene collection out of the folder

 

[Lawrence_SoCal]

Ouch if that is what is actually required (blowing away your scene setup completely)
I'd hope there would be a way to go into the JSON (settings) file and hand edit something to get passed the problem

 

[qsg001]

There may be, but I don't know enough about it to know which setting fixed it. This is the exact posting on Discord that I followed:

to solve this you'll need to remove your scene collection unfortunately. it's been addressed but hasn't made it to an OBS release yet