Advanced Scene Switcher 1.28.1

[ContentDeveloper]

I am developing an OBS environment that relies heavily on Advanced Scene Switcher, for other users to use.
Is there a way to lock out users from changing anything in AdvSS, so they don't access to "the code".

• Perhaps a password mechanism to be able to make changes?

Also, I am already planning to load the "master" settings file whenever OBS is loaded -- perhaps that is sufficient -- as in if a curious user messes things up for themselves, they would be instructed to restart OBS?

• Where is the settings file located, that is loaded upon OBS launch?

 

[AaronD]

I am developing an OBS environment that relies heavily on Advanced Scene Switcher, for other users to use.
Is there a way to lock out users from changing anything in AdvSS, so they don't access to "the code".

• Perhaps a password mechanism to be able to make changes?

Also, I am already planning to load the "master" settings file whenever OBS is loaded -- perhaps that is sufficient -- as in if a curious user messes things up for themselves, they would be instructed to restart OBS?

• Where is the settings file located, that is loaded upon OBS launch?

You can start with:

• File -> Show Settings Folder
• File -> Show Profile Folder

Adv. SS is part of the Scene Collection, which should be close by, but you probably want to back up ALL of that and restore it before each launch anyway. (don't launch OBS directly, but have a script that restores the backup and *then* launches it)

I do something similar for digital sound in a couple of churches: A computer somewhere is on 24/7 (usually a Raspberry Pi), and when the sound board appears on the network, it pushes the standard settings into it. (there's a battery backup and some additional timing involved, so that a power hiccup doesn't completely wreck a service, but you get the idea) So it no longer matters how the last person left it. And if you want to continue how you left off, you need to explicitly save it, wait for the reset, and then load it again. Works really well!

I haven't done that yet with OBS - still changing things around too much myself - but probably the way I'd do it is to:

1. Have a Profile and Scene Collection that is known to work. I'll call it "Standard" for now.
2. Back that up, but only that, so that others can still have their favorite derivatives of it.
3. Have the launcher script restore the backup and point OBS to it:
   • obs --profile "Standard" --collection "Standard" and whatever other command-line options you want. obs --help in a terminal to see all of them.

Then if something doesn't work, you can tell them to restart, which has them run the script because you've modified the launcher(s) to do that. And if they want to keep their "special settings", they can do that too by the normal switching method inside of OBS, because the backup does *not* include that. But you don't support their derivatives. If they mess it up and don't know how to fix it, then they can reboot and use the standard.

 

[ContentDeveloper]

Thank you, @AaronD -- I am aleady storing off in a separate location the Profile, Scene Collection, and AdvSS settings file, and also using the --profile and --collection switches as you mentioned.

Sounds like my approach is inline with yours. :-)

Just to confirm -- you are saying that all the AdvSS settings (including macros) are stored in the Scene Collection file?

 

[AaronD]

Just to confirm -- you are saying that all the AdvSS settings (including macros) are stored in the Scene Collection file?

Yep. You can see that if you set some up, change Collections, and look again.

 

[Sambo3975]

Unfortunately, the minimum required OBS version for this plugin is currently OBS 30.1.2.

You still seem to be using OBS 27.
I think the last version of the advanced scene switcher supporting OBS 27 was 1.17.7.

I had installed OBS and this plugin through the Synaptic package manager. For some reason, it has OBS 27 as the latest version of the software, but it installed the version of the plugin for OBS 30.

I removed those versions and went ahead and installed from flatpak instead, so now the version incompatibility is resolved. Of course, now I've just moved on to another problem. OBS just hangs when trying to load the plugin. Here's the new log:

12:42:49.330: Using EGL/X11
12:42:49.352: CPU Name: AMD Ryzen 7 3700X 8-Core Processor
12:42:49.352: CPU Speed: 3600.000MHz
12:42:49.353: Physical Cores: 8, Logical Cores: 16
12:42:49.353: Physical Memory: 32035MB Total, 13597MB Free
12:42:49.353: Kernel Version: Linux 5.15.0-124-generic
12:42:49.353: Flatpak Branch: stable
12:42:49.353: Flatpak Arch: x86_64
12:42:49.353: Flatpak Runtime: runtime/org.kde.Platform/x86_64/6.6
12:42:49.353: App Extensions:
12:42:49.353:  - com.obsproject.Studio.Plugin.SceneSwitcher
12:42:49.353:  - com.obsproject.Studio.Locale
12:42:49.353: Runtime Extensions:
12:42:49.353:  - org.freedesktop.Platform.GL.default
12:42:49.353:  - org.freedesktop.Platform.GL.nvidia-535-183-01
12:42:49.353:  - org.freedesktop.Platform.openh264
12:42:49.353:  - org.gtk.Gtk3theme.Mint-Y-Dark-Aqua
12:42:49.353:  - org.gtk.Gtk3theme.Mint-Y-Dark-Teal
12:42:49.353:  - org.kde.Platform.Locale
12:42:49.353:  - org.freedesktop.Platform.GL.default
12:42:49.353: Flatpak Framework Version: 1.12.7
12:42:49.353: Desktop Environment: X-Cinnamon (cinnamon)
12:42:49.353: Session Type: x11
12:42:49.353: Window System: X11.0, Vendor: The X.Org Foundation, Version: 1.21.1
12:42:49.354: Qt Version: 6.6.3 (runtime), 6.6.3 (compiled)
12:42:49.354: Portable mode: false
12:42:49.399: OBS 30.2.3 (linux)
12:42:49.399: ---------------------------------
12:42:49.409: ---------------------------------
12:42:49.409: audio settings reset:
12:42:49.409:     samples per sec: 48000
12:42:49.409:     speakers:        2
12:42:49.409:     max buffering:   960 milliseconds
12:42:49.409:     buffering type:  dynamically increasing
12:42:49.410: ---------------------------------
12:42:49.410: Initializing OpenGL...
12:42:49.482: Loading up OpenGL on adapter NVIDIA Corporation NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2
12:42:49.482: OpenGL loaded successfully, version 3.3.0 NVIDIA 535.183.01, shading language 3.30 NVIDIA via Cg compiler
12:42:49.507: ---------------------------------
12:42:49.507: video settings reset:
12:42:49.507:     base resolution:   2560x1440
12:42:49.507:     output resolution: 1920x1080
12:42:49.507:     downscale filter:  Bicubic
12:42:49.507:     fps:               60/1
12:42:49.507:     format:            NV12
12:42:49.507:     YUV mode:          Rec. 709/Partial
12:42:49.507: NV12 texture support enabled
12:42:49.507: P010 texture support not available
12:42:49.507: Audio monitoring device:
12:42:49.507:     name: Default
12:42:49.507:     id: default
12:42:49.507: ---------------------------------
12:42:49.527: No AJA devices found, skipping loading AJA UI plugin
12:42:49.527: Failed to initialize module 'aja-output-ui.so'
12:42:49.545: No AJA devices found, skipping loading AJA plugin
12:42:49.545: Failed to initialize module 'aja.so'
12:42:49.723: [pipewire] No capture sources available
12:42:49.767: [obs-browser]: Version 2.23.6
12:42:49.767: [obs-browser]: CEF Version 103.0.5060.134 (runtime), 103.0.0-5060-shared-textures.2594+g17f8588+chromium-103.0.5060.134 (compiled)
12:42:49.780: NVENC supported
12:42:49.780: VAAPI: Failed to initialize display in vaapi_device_h264_supported
12:42:49.780: FFmpeg VAAPI H264 encoding not supported
12:42:49.780: VAAPI: Failed to initialize display in vaapi_device_av1_supported
12:42:49.781: FFmpeg VAAPI AV1 encoding not supported
12:42:49.781: VAAPI: Failed to initialize display in vaapi_device_hevc_supported
12:42:49.781: FFmpeg VAAPI HEVC encoding not supported
12:42:49.860: [obs-websocket] [obs_module_load] you can haz websockets (Version: 5.5.2 | RPC Version: 1)
12:42:49.860: [obs-websocket] [obs_module_load] Qt version (compile-time): 6.6.3 | Qt version (run-time): 6.6.3
12:42:49.860: [obs-websocket] [obs_module_load] Linked ASIO Version: 103002
12:42:49.864: [obs-websocket] [obs_module_load] Module loaded.
12:42:49.923: [adv-ss] version: 1.28.0
12:42:49.923: [adv-ss] version: 0ee6feb529930e0bc6458bd8b58ec983ea9d3d9b
12:42:49.924: [adv-ss] attempting to load "/app/plugins/lib/obs-plugins/advanced-scene-switcher-plugins/advanced-scene-switcher-base.so"
12:42:49.927: [adv-ss] successfully loaded "/app/plugins/lib/obs-plugins/advanced-scene-switcher-plugins/advanced-scene-switcher-base.so"
12:42:49.927: [adv-ss] attempting to load "/app/plugins/lib/obs-plugins/advanced-scene-switcher-plugins/advanced-scene-switcher-opencv.so"
12:42:49.937: [adv-ss] successfully loaded "/app/plugins/lib/obs-plugins/advanced-scene-switcher-plugins/advanced-scene-switcher-opencv.so"
12:42:49.937: [adv-ss] attempting to load "/app/plugins/lib/obs-plugins/advanced-scene-switcher-plugins/advanced-scene-switcher-midi.so"

Once it gets to this line, the process just freezes and the UI never appears.

Be aware that if you decide to update OBS, the change from v27 to v28 not only breaks pretty much all of the plugins, but also wipes out their settings even if you downgrade back!

• Some of their functions became native, so you don't need the old plugin anymore. The WebSocket server is one of those.
• Some died because they were already abandoned but still continued to work until then.
• Some, like this one, were rebuilt for the change and thus continue to work.

There is a way to upgrade without losing settings - essentially upgrade both OBS and all the plugins before trying to run it at all, and hope that you did it all right - but it's much more straightforward to document all of what you have, let it wipe out, and then rebuild it from your documentation.

It's generally recommended to keep things up to date, but do be aware of that version in particular!

I thankfully don't need to worry about this, because I didn't have an install of OBS before I started trying to set this up.

 

[Sambo3975]

I was able to get OBS to launch by manually deleting the advanced-scene-switcher-midi.so from the folder. I figure it's for reacting to inputs from a MIDI controller, which I don't need. Still, I'd like to have a solution to this so I don't have to navigate through the rather human-unfriendly directory structure used by Flatpak to manually delete a file every time the plugin is updated.

 

[AaronD]

I had installed OBS and this plugin through the Synaptic package manager. For some reason, it has OBS 27 as the latest version of the software, but it installed the version of the plugin for OBS 30.

I removed those versions and went ahead and installed from flatpak instead, so now the version incompatibility is resolved. Of course, now I've just moved on to another problem...

...navigate through the rather human-unfriendly directory structure used by Flatpak to manually delete a file every time the plugin is updated.

I really don't like Flatpak, or any other container, for OBS. The entire purpose of a container (secure, private sandboxing; universal self-contained compatibility; etc.) runs counter to what OBS needs to really work well (direct access to good hardware, efficient execution, etc.). It might be the only way to make it work reliably on some distros, but if that's the case, you should probably look at switching distros, even if you end up multi-booting just for OBS. Always run OBS natively if you possibly can.

I believe Mint is based on Debian, right? If so, then I think the official PPA should work:
sudo apt-add-repository ppa:obsproject/obs-studio
Then a normal sudo apt update && sudo apt upgrade should get the actual latest version with all the features.
Or if you've removed the native version, sudo apt update && sudo apt install obs-studio will finally get the right one.

 

[AaronD]

...I didn't have an install of OBS before I started trying to set this up.

If this is a fresh OS install with nothing else set up either, then you might look at Ubuntu Studio instead:

Ubuntu Studio – A free and open operating system for creative people.

ubuntustudio.org

It's designed specifically for media production, with a low-latency kernel by default and a TON of apps preinstalled and already working! OBS is one of them, albeit an old version. But once you install the PPA and do a normal update/upgrade, you'll have the right version, native, and you can build from there.

 

[Warmuptill]

Hi,

Hotkeys for macros has stopped working for me, and I have no idea why.

I have macros for managing whether sources are enabled in scenes, and have them linked to hotkeys. It was all working fine until about a week ago, when now they don't.

The macros still work - I can run them manually. Hotkeys still work, e.g. for doing transitions. There are no conflicting hotkeys. I've removed and reassigned the hotkeys, and tried using other hotkeys. No upgrade have been done (at least not intentionally). I've restarted OBS and the computer. I've switched profiles.

I haven't yet looked at logs. I only just thought of that, and the computer is not with me.

Anything else I can try next time I am at the computer?

Thanks @Warmuptill for a great plugin.

I think providing an OBS log with verbose logging enabled will have the best chance at providing a hint as to what the problem might be.

 

[tonyl]

I think providing an OBS log with verbose logging enabled will have the best chance at providing a hint as to what the problem might be.

Yep will do in a couple of days

 

[RobertWilliams]

Does anybody know what the "Save Time remaining" under Timer conditions does?