OBS for enterprise wide deployment

[morebit]

Dear forum,

I have developed scene collections and various profiles for my own purposes (business context: live teaching, small/medium/large meetings, conferences) . With more than 30 scenes, my main collection uses plenty of advanced stuff I learned here. Be it guest integrations with MS Teams-NDI sources or a self-hosted OBS Ninja, transitions, lower thirds, ... I tried a lot over time and will develop this system further.

This raised attention by other colleagues and I have meanwhile trained more than 100 colleagues in using OBS with my collections. Therefore I started to setup a versioning process, Q&A process, deployment process etc. As every PC is different, I created scripts for example to modify paths before importing collections etc. Key grabber assure that hotkeys work even with OBS in the background etc.

But what if we speak about 1,000s of colleagues?

I could imagine the following routes:

• Own Windows application which uses obslib. Simple GUI to select the screen to be shared and the cam with or w/o keying. Num pad for switching predefined scenes.
• Standard OBS, but in addition a simple local tool with subversion or git as a hub which manages the deployment of scenes in a consistant manner. So by releasing a new collection centrally, it can be deployed to everyone else... pull or even push
• or, or ...

I don't believe that writing a wrapper around OBS to allow it to run as a central server is scalable enough, even with WebRTC.. but maybe I am mistaken.

At the moment, the manual way was the most easiest for me and I am wondering if it's worth to start a multi-months/year journey to develop an enterprise'ish tool. I am just downloading Visual Studio 2019... ;-)

Any thought or advise is highly appreciated.

Thanks,
morebit

 

[koala]

OBS Studio is designed to run on standalone client PCs and to act as streaming client or recording app. It has no built in support for collaborative work at the producing (front end) part of creating a video. It has no permission/rights management (not even a hook). It has no support for company-like global configurations such as AD group policy and shared folders. It has no support for shared usage of the same configuration files (in case you think about using a configuration on a shared folder), not even a hook.

There is a plugin system you can use for building upon the original OBS, without the need to develop a complete new own user interface.
Keep in mind what OBS is not. OBS is no server. OBS is no service. OBS is no tool for screen sharing in a collaborative environment (use Teams for this, or Zoom, or whatever collaborative tool is especially designed for this). OBS is no stream recorder. OBS is not designed to be managed and to work in a corporate environment but for standalone PCs where the sole user of the PC is the administrator of that PC as well.