Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save global spout output setting in OBS profile #55

Open
Wiethoofd opened this issue Feb 22, 2023 · 0 comments
Open

Save global spout output setting in OBS profile #55

Wiethoofd opened this issue Feb 22, 2023 · 0 comments

Comments

@Wiethoofd
Copy link

I like to run multiple (& portable) OBS instances, ideally multiple profiles from the same folder, so I only need to update one and get plugins in a single folder. Running multiple profiles for various purposes currently all share the same Spout output setting from the Tools menu option. If one profile sets a name and auto starts it, the other profiles all share the same name and setting.

This is mainly an issue when running with --multi, however the same problem exists when swapping between profiles after having launched with one with a name and autostart it will be enabled and started a second OBS even if it is not necessary, and in case of a 2nd instance it will have same name (it correctly adds a numeric _x suffix, but should be an entirely different name if possible).

Describe the solution you'd like
Save the Tools > Spout Output Settings defined settings in the profile and recall those when swapping between profiles. Something similar is already the case for websocket settings, which are stored per profile.

Describe alternatives you've considered
Copying my portable install folders and running OBS instances out of those, increasing unnecessary disk space to be used, defeating the point of the --multi launch option and needing to update plugins across multiple folders.

Additional context
Used versions: OBS 29.0.2 & Spout v1.8 (no version info is output in the OBS log or in the dialog popup for settings about the plugin)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant