Sorta. The overall mindset is to produce a single A/V stream, so the structure is geared towards that. But there are two ways to produce multiple different streams at the same time:
Multiple instances of OBS, each one being responsible for a different product. If they're on the same machine, you can use the --multi flag on the command line, or in a script, to tell it not to complain about the other instances. Other flags tell it what settings to use. Run `obs --help` in a terminal to see what all you can tell it on the command line or in a script. The downside of this is that a lot of systems, even today, restrict access to each video source to one app only for performance reasons, so each instance of OBS must use an entirely unique set of those. If your application is okay with that, or your system doesn't have that restriction, then this might be a conceptually simpler way to do it. Though if you need to coordinate live production decisions between multiple instances, it can become complex in a hurry!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
