Looking for advice on multi-user / multi-organization set up for livestreaming

[lornix]

Our church has another congregation that uses our sanctuary. We have recently installed PTZ Optics cameras to livestream our services using OBS - and the other congregation would like to use them. We are trying to figure out the best way to set things up for both congregations so that

a) Both congregations have access to the cameras - and a connection to the internet for streaming

b) Neither congregation's use of the cameras will mess with default settings for the other congregation.

(I hasten to add that we are not greatly concerned about preventing malicious activity by any party - we just want to minimize the chances of accidental changes - or that the way a camera is used or the software is configured by one user at time a does NOT automatically affect the way the camera and software works for another user at a later time.)

We are considering the following options

A) Installing a new hard drive in the computer we currently use for livestreaming - setting it up in dual boot mode - so each congregation has their own OS, Software, etc. on a separate hard drive - in a way that should minimize the chances that changes in the way one user uses cameras and software affects another user.​

B) Setting up separate user accounts (one for each congregation) within one installation of Windows - installing drivers, control software etc. for each user separately - giving each user permissions only to some of the directories on the hard drive - and so forth to use standard Windows user security features to control access. (In one variation of this - we might consider insuring that both congregations use DIFFERENT streaming software, in the hope that provides an additional layer of protection). Since both congregations would need to be able to maintain things for themselves, these accounts would have to have fairly broad levels of access, but we would hope to isolate the user directories, so that no user could accidentally make changes in the other user directory.​

C) (Not really considering this option - but this exists as the kind of baseline that makes us worry) -- Simply letting the other congregation use our existing hardware and software - maybe in a separate user account - but while all drivers and control software are installed for ALL USERS - in a way that we fear makes it very likely that every time a change is made to any aspect of camera or software configuration, it would become the new standard for all subsequent users.​

Do you have any advice that you can give on the relative merits of these approaches? It seems to us that approach A may be more secure, but might be an overkill kind of solution, and would still not prevent configuration changes that are stored in the cameras themselves. Approach B probably involves a slightly higher degree of ongoing work, but the work that is required is more "standard" - so any issues would be easier to identify and resolve - but would not help if any default configurations for the cameras or software are e.g., written to the registry, so defaults could change for ALL users. We have already noticed even with just a small number of users from one congregation that some settings seem to shift in ways we don't expect - so we are convinced that C is a bad choice, we just are not quite sure how much protection we need.

Both congregations are fairly small - and would rely on volunteers from the congregation for tech support - so we do not currently have true Systems Admins who are accustomed to dealing with all of the issues of maintaining dual boot systems, or managing user accounts, or ..., so a solution needs to be reasonably simple to implement.

Thanks for any suggestions you could provide - or other background information that would help us make an appropriate decision.

Setup

• Dell computer running Windows 10 (will shortly transition to Windows 11)
• OBS software for livestreaming (possibly transitioning to Vimeo Studio 6 - one congregation using Vimeo, and the other using OBS would be our "two livestream software" solution)
• 2 PTZ Optics SDI cameras (one 12x, one 20x) - using the serial HuddleCam HD control panel

Don Dresser

 

[Lawrence_SoCal]

Typical HoW scenario... and without solid documentation, 'drift' of a config is bound to occurr. even in single congregation scenario as you point out.

The challenge is that OBS is NOT designed for role-based access controls. OBS settings are in User Profile space, so you can't, by default, use a separate account per user without a LOT of hassle. In prior threads have been discussions of moving/mapping OBS settings folder to a Shared folder structure and adjusting NTFS permissions appropriately. But, that means any user, so enabled, can make change... which with typical lack of IT understanding, can make a mess.
To my knowledge, not really a good solution for a secure, multi-user setup for OBS.. unfortunately.
With that said, with proper planning on the part of someone who does know what they are doing, most of the multi-user challenges can be addressed with OBS Profiles and Scene Collections, associated backup routines, and solid training to avoid making changes in Global OBS Settings. And even then, there will be the odd issues with Windows OS and driver updates, most recently impacting some users and Audio. The reality is that a Windows OS and software streaming setup won't be low-maintenance. I use Win10 and OBS, and it is powerful, flexible, cost-effective, etc. but not simple....
I write from a position of being the one with a strong IT background, who setup our HoW OBS livestream environment 2+ years ago.

My recommendation
- stick with Win10 for now, and probably for at least another year?? I strongly recommend against a Win11 transition any time soon [see lots of threads with OBS and WIn11 issues. Std every-other desktop OS release from MS..]
- Considering small congregation and tech sophistication, I'd recommend using same streaming software so you have cross-training/learning opportunity and support [and no potential camera settings conflicts.. ie OBS requires X, and other s/w requires Y settings... not sure if that would happen, but why complicate matters?]

As there isn't a tracking of user changes to OBS settings, there probably isn't much use/benefit of creating individual user accounts, and a shared settings folder structure. And automating or manually replicating OBS configs across separate OS user accounts would be pointless, in my opinion [just regularly backup the OBS settings, as a precaution]. An admin account, then Congregation A and Congregation B OS user accounts, rotating passwords as appropriate, would be fine

Keep Global OBS settings limited. For example, I disabled all OBS Global Audio sources, and setup a Specific Audio Source only in the scenes required. Then train users on what things to NOT touch/adjust, and if they must, the documentation/communication requirement. And then be willing to block users that don't follow the rules [even if that means a congregation can't stream.. put the fear God into them, so to speak, if they screw things up... you are in a better position to judge if the personalities involved can handle 'following the rules'].
As for OBS, If need be, you could have a 'normal' OBS install for A, and a Portable OBS install for Account B

I use a Panasonic NDI PTZ camera, and its camera control software has user profiles. So presets, etc, would be user specific. I'm looking forward to checking out PTZOptics new (in Beta) PTZ camera control software as I'm not impressed with Panasonic's free offering. With OBS, PTZOptics already has an OBS plugin. Are you using that? [just re-read, and you are using serial HuddleCam controller... hmm, does that have user profile option? Or have you considered upgrading to network (instead of serial?) based PTZ control?]
And with same streaming s/w setup, there should be no need to change ANY in-camera settings. Presets, white balance, etc should all be handled from camera control s/w on PC, not in-camera. Any and all in-camera settings should be off-limits... set once, and then 'locked'. With my Panasonic NDI PTZ cameras, I have an option for separate user accounts on camera. So all settings can be locked behind an Admin account. I suspect PTZOptics has similar.
Are you currently controlling the cameras during a service from the camera browser interface? if yes, I'd advise to stop doing that.

For our setup, I have a Visio laying out the network, camera, Audio mixer connections, etc.
Then I have technical documentation, as well as a step-by-step user guide from PC power on to livestream, to post-live cleanup process (archiving recording) and system shutdown. This includes using a non-persistent stream key, acting as 'Digital Usher' during service, etc

Presuming non-technical Congregation B, I'd be inclined to
1. decide on shared OBS install (using OBS Profile/Scene Collection to separate) or using OBS Portable mode for 2nd install
2. create new user account(s) at OS level
3. Copy/Duplicate Congregation A's OBS Scene Collection as starting point for Congregation B

Feel free to DM if you wish to talk directly

 

[lornix]

Thanks very much for your thoughtful response. I am sharing it with the rest of our livestreaming team, and expect to get back to you with questions soon.