Question / Help Preset Settings
- Thread starter 21Dodge
- Start date
koala
Active Member
You want to package and distribute OBS within your organization and include a configuration.
This is a highly complex topic, depending on the exact kind of customization you want to implement, the number of clients your rollout includes, and the kind of hardware your clients have.
The only general thing that can be said without knowing all this is the location of the configuration files. It is in %appdata%\obs-studio.
You can create a master configuration on a master workstation and copy the contents of the %appdata%\obs-studio directory to your clients. This has to be extracted to the %appdata%\obs-studio directory of your users to preload a configuration.
Keep in mind that this configuration contains hardware-dependent information. If devices of the master workstation are referenced that do not exist on the client workstation, your configuration will not work. That includes hardware encoders, monitor definitions or audio devices. And if the master workstation is more powerful than the client workstations, test recordings may seem run fine on the master workstation but not on the client workstations.
Usually, the result isn't worth the effort unless you are supporting hundredths of workstations which all have the same hardware. If you want to support less, it is probably easier to create a documentation how to do it manually, and if the user isn't able to cope with the documentation, he calls support and the support configures OBS for him manually.
If you just want to help a computer-illiterate friend and give him a all-singing-all-dancing default setup: forget it. Visit him and do the configuration for him at his PC.
This is a highly complex topic, depending on the exact kind of customization you want to implement, the number of clients your rollout includes, and the kind of hardware your clients have.
The only general thing that can be said without knowing all this is the location of the configuration files. It is in %appdata%\obs-studio.
You can create a master configuration on a master workstation and copy the contents of the %appdata%\obs-studio directory to your clients. This has to be extracted to the %appdata%\obs-studio directory of your users to preload a configuration.
Keep in mind that this configuration contains hardware-dependent information. If devices of the master workstation are referenced that do not exist on the client workstation, your configuration will not work. That includes hardware encoders, monitor definitions or audio devices. And if the master workstation is more powerful than the client workstations, test recordings may seem run fine on the master workstation but not on the client workstations.
Usually, the result isn't worth the effort unless you are supporting hundredths of workstations which all have the same hardware. If you want to support less, it is probably easier to create a documentation how to do it manually, and if the user isn't able to cope with the documentation, he calls support and the support configures OBS for him manually.
If you just want to help a computer-illiterate friend and give him a all-singing-all-dancing default setup: forget it. Visit him and do the configuration for him at his PC.