MacOS Portable Mode Troubles

I'm pretty clueless about all this, but I managed to do the minimum command line-wrangling required to get Portable Mode running on MacOS (to anyone stuck on that, it took a sudo to get past the "Failed to create directory ../config/obs-studio/basic").

My issues are that:
1) I can't actually get the thing to run "portably." If I try to run OBS from a flash drive, I'm told that the file is damaged and needs to go in the trash. Is there a way around that?
2) The MacOS Portable Mode isn't actually saving the profiles/scenes to the same file as the app, it's shoving them into the Users folder, which...isn't super portable, as far as I know.

Basically, I want to be able to let someone else use my profiles/scenes with as little setup as possible—I'm in charge of streaming for my institution, and I hope I can train someone to be my backup without them having to know everything about setting OBS on their own computer. The ideal is that they can just open up a file on a flash drive and it (mostly) just works, and if there are any other or better ways to make that happen with MacOS, I'm all ears.

I haven't run into your first problem, but I run two instances of OBS - one to do a stream, one to handle a Zoom call - with shell scripts. It seems like OBS saves its data to "../config", so you need to be in the Contents/Resources/MacOS folder when you run it.
Here's what I use. I put it in the same folder as the .app:

@fastfourier - why does your bash script refer to a Zoom folder? I tried this and it did not work as I am not using Zoom ... Thanks

@salmiak He's running OBS in such a way that it creates some (most? all?) of its configuration files in the `.app` folder.

He's copied `OBS.app` as `OBS Zoom.app` so that `/Applications/OBS.app/Contents/MacOS/basic/profiles` and `/Applications/OBS Zoom.app/Contents/MacOS/basic/profiles` can be entirely separate.

Unfortunately on the latest versions of macOS, Gatekeeper gets confused and associates screen and accessibility capture with the Terminal rather than with OBS when run that way.

As far as I can tell there is no way to pass the config directory as an option to OBS so that multiple instances can be run as its own Application rather than as "Terminal".

The closest I've gotten is this:

#!/bin/sh set -e set -u # add --multi to allow multiple instances, but be warned: # they all write to the same config files, which may corrupt them # so backup ~/Library/Application\ Support/obs-studio first! open -n -a "OBS.app" --args \ --profile 'Dummy 1 Profile (1440p@30)' \ --collection Dummy 1 Scene Collection' \ --scene 'Dummy 1 Scene'

Click to expand...

I can successfully run two instances at once with `--multi` (or just clicking Okay on the warning), but after that the config files become corrupted and neither load.

BACKUP `~/Library/Application Support/obs-studio` BEFORE ATTEMPTING THIS!

#!/bin/sh set -e set -u open -n -a "OBS.app" --args \ --multi \ --profile 'Dummy 2 Profile (1440p@30)' \ --collection Dummy 2 Scene Collection' \ --scene 'Dummy 2 Scene'

Click to expand...