Advanced Scene Switcher 1.29.3

[AaronD]

Thank you, for explaining that. Right now, my use case scenario is that I have already set a hotkey to capture a short clip (using the source record plugin), which plays in a replay scene and I use Adv. SS to switch to that replay scene and then back to my game capture scene after a few seconds. (Hence the 2 same hotkeys.) Is there a way, I can do this is in the macro?

I thought you were switching scenes with the hotkey, and using the same hotkey to trigger some other stuff in a macro. I don't know that you can trigger other plugins, though I think it'd be really handy to have "virtual hotkeys" that can be sent from here to any other plugin and don't conflict with anything else. (you can hit the same key on the keyboard, and it doesn't do anything)

In the absence of that, one idea might be to use OBS's native recording function, set to a static name and to overwrite the old file, and then the replay scene connects to that. Adv. SS has actions to start and stop that recording.
(I think the replay buffer works the same way, but it stays in RAM, never a file. Never actually used that one though, so I could be all wet.)
Either way, you'd be limited to recording the stream output, not an arbitrary source, but maybe that's okay?

 

[AaronD]

Two minor issues:

---

1.
Collapsing / folding a group takes one too many with it:

As you can see, it has an easy workaround, but it would still be good to fix.

---

2.
Several times, the Macro -> Run Actions actions changed all of my Volume... macros to --select macro-- after a reboot, but the Gate... ones have always stayed correct. I had to put the Volume... ones back several times and it looks like they're finally staying, but it still makes me wonder how long they're going to last.

I was still grouping, ungrouping, and renaming during that time, so maybe that has something to do with it? But I think one of them was triggered only by having the group expanded or not.

 

[Warmuptill]

Collapsing / folding a group takes one too many with it:

Thanks for pointing that out!
That is an issue that should already be fixed on the main branch, e.g. in this build:

Enable assigning value of scene item transform to variables · WarmUpTill/SceneSwitcher@826bee8

An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

The group size was not updated properly when removing macros that are currently part of a group.

I was still grouping, ungrouping, and renaming during that time, so maybe that has something to do with it? But I think one of them was triggered only by having the group expanded or not.

That was likely related to renaming / grouping, etc.
Handling references to other macros within macros still needs to be cleaned up.

This plugin is incredible. Over the past two years of using OBS, it's completely taken over my workflow. If you were to incorporate math into variables or text fields, I see that opening a new world of possibilities for dynamic design. Thank you for everything.

A build containing a first version of this functionality will be available here in a few minutes:

Variable and http action · WarmUpTill/SceneSwitcher@11ac9bd

An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

(Updated build link to fix a crash if the expression was empty)

Please note that this build might be unstable or have bugs as it contains a lot of variable related changes (not just for this particular functionality).
So before testing or using it make sure to back up your settings.

Please do let me know if you encounter any issues!

 

[rusty1]

Thanks for pointing that out!
That is an issue that should already be fixed on the main branch, e.g. in this build:

Enable assigning value of scene item transform to variables · WarmUpTill/SceneSwitcher@826bee8

An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

The group size was not updated properly when removing macros that are currently part of a group.


That was likely related to renaming / grouping, etc.
Handling references to other macros within macros still needs to be cleaned up.


A build containing a first version of this functionality will be available here in a few minutes:

Variable and http action · WarmUpTill/SceneSwitcher@78b7fb6

An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

Please note that this build might be unstable or have bugs as it contains a lot of variable related changes (not just for this particular functionality).
So before testing or using it make sure to back up your settings.

View attachment 92379

Please do let me know if you encounter any issues!

It's working perfectly for me!! ♥

 

[khaver]

Something I've noticed when using the macro, Video "has changed" "For at least", even with a static webcam shot with no movement, the video noise of the webcam will trigger it. I have to create a clone of the source using another plugin, apply a color correction filter and adjust the gamma so the area that is being check is totally black, in order to keep any video noise from triggering the macro. I had problems when I checked the box "Use pattern matching". I would have to adjust the threshold down a bit, but then if any movement I was trying to trigger only slightly moved, the macro wouldn't be triggered.

Darkening a cloned source does work to mitigate the video noise problem, but it would be nice if there was some sort of adjustment in the macro itself to affect the image (darken, blur, contrast or ?) before sending it to the OpenCV functions.

 

[jegadk]

Hi.

Having 2 macro's. Macro1 before gamestart and macro2 after game break.

When Macro1 is finished, i pause this macro and unpause Macro2.
Pause (Uncheck) Macro1 works, but it will not unpause Macro2 (Check Macro2)

Jesper

 

[jegadk]

Hi.

Having 2 macro's. Macro1 before gamestart and macro2 after game break.

When Macro1 is finished, i pause this macro and unpause Macro2.
Pause (Uncheck) Macro1 works, but it will not unpause Macro2 (Check Macro2)

Jesper

Found the mistake.

When PAUSE a Macro, it does not run to end.

Solution: First do the unpause of Macro2 then Pause Macro1 as the last step

Jesper

 

[MagnuzTG]

Hi, I uppdated to 29.0.2 on OBS and is has destroyed the plugin. I have managed to fix most of but miss one thing. Every time I take a new replay it dosent change to the new one but keeps the previous one. Is there maybe a macro or something I dont know how to do or a setting?



OBS: 29.0.2
Advanced Scenbe Switcher: 1.20.5

 

[Warmuptill]

Hi, I uppdated to 29.0.2 on OBS and is has destroyed the plugin.

First of all, I apologize for the issues you are encountering!

Just to clarify - did you upgrade from an OBS version <= 27 to 29 and lost all your settings (due to the Qt framework version change)?
Or are you referring to another issue with "destroy"?

Every time I take a new replay it dosent change to the new one but keeps the previous one. Is there maybe a macro or something I dont know how to do or a setting?

Sorry I don't fully understand what you are trying to do. :(
Can you elaborate a bit on what is not working as you would expect?

 

[adrianabootie]

Aargh. So I upgraded from OBS 28 to OBS 29 on a M1 MacBook running Ventura 3.2.1, and.... now Advanced Scene Switcher doesn't even show up in the Tools menu of OBS. I've tried re-downloading and re-installing to no avail.

The plug in which is called -- advanced-scene-switcher.plugin -- is installed here:
~user/Library/Application Support/obs-studio/plugins

Does this plugin need to be installed elsewhere? Is there a way to automatically install it correctly? Am I downloading the wrong plugin for an M1 Mac running OBS 29?

HELP!

Everything was working fine on the same machine running OBS 28. Now Advanced Scene Switcher won't even show up as an option under the Tools menu.

 

[Warmuptill]

Aargh. So I upgraded from OBS 28 to OBS 29 on a M1 MacBook running Ventura 3.2.1, and.... now Advanced Scene Switcher doesn't even show up in the Tools menu of OBS. I've tried re-downloading and re-installing to no avail.

The plug in which is called -- advanced-scene-switcher.plugin -- is installed here:
~user/Library/Application Support/obs-studio/plugins

Does this plugin need to be installed elsewhere? Is there a way to automatically install it correctly? Am I downloading the wrong plugin for an M1 Mac running OBS 29?

HELP!

Everything was working fine on the same machine running OBS 28. Now Advanced Scene Switcher won't even show up as an option under the Tools menu.

Can you share an OBS log?

I think the most likely situation is that you accidentally installed the x86 version of the plugin while OBS is arm based or vice versa.
That should be visible in the log.

 

[adrianabootie]

Can you share an OBS log?

I think the most likely situation is that you accidentally installed the x86 version of the plugin while OBS is arm based or vice versa.
That should be visible in the log.

Sorry for not knowing how to access an OBS log, but where would I find that?

 

[AaronD]

Sorry for not knowing how to access an OBS log, but where would I find that?

Include a log file if you have a problem: here's how

To upload a log file, go to the Help menu -> Log Files -> Upload current/last log file. The current log file is for the currently active running session. The last log file is for the last time you ran the program. We recommend always including it just in case.

obsproject.com

 

[LexXxusTV]

I was wondering kinda off topic, but not.
Is there any way to have OBS listen when you get killed in PUBG to auto change your scene?
Kinda the way Geforce Experience records highlights and end game deaths?

If you don't think it's possible, who would be best to send this request to, PUBG and ask them to make the plugin also?
I think this option for streamers could be possible if we had access to the codes PUBG is sending out to trigger that.

Thanks for all your help and advice Warmuptill

 

[Warmuptill]

I was wondering kinda off topic, but not.
Is there any way to have OBS listen when you get killed in PUBG to auto change your scene?
Kinda the way Geforce Experience records highlights and end game deaths?

If you don't think it's possible, who would be best to send this request to, PUBG and ask them to make the plugin also?
I think this option for streamers could be possible if we had access to the codes PUBG is sending out to trigger that.

Thanks for all your help and advice Warmuptill

You might be able to achieve this using the "Video" condition, assuming there some sort information available visually that this event has occurred.
For an example how on how to use the video condition you can check out this guide:

Activate overlay to hide parts of the screen

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

For more general information about the video condition have a look at this wiki page:

Video condition

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

Hope that helps!
Let me know if you have any questions!

 

[carlo_gra]

Hi,

I'm having issues in installing the plugin on Ubuntu 20.04 with XFCE. I tried with the binary but it's not showed in the Tools menu...
I tried to install it manually but with any difference from the previous attempt.
I also tried with flatpak but in this case I lose VLC as a source.

Any Idea on how to have it working?

 

[Warmuptill]

Hi,

I'm having issues in installing the plugin on Ubuntu 20.04 with XFCE. I tried with the binary but it's not showed in the Tools menu...
I tried to install it manually but with any difference from the previous attempt.
I also tried with flatpak but in this case I lose VLC as a source.

Any Idea on how to have it working?

I think believe Ubuntu 20.04 is still using Qt5.
The prebuilt images of the plugin are built for Qt6 however.

This could be confirmed by having a look at an OBS log. (Feel free to share one and I will have a look)

If it should turn out that this is indeed the issue then you cannot use the official releases on GitHub.
Instead you will either have to rely a version available via a package manager (flatpak, snap, ...) or build the plugin yourself.

Let me know if you have any questions!

 

[carlo_gra]

I just found that there are a couple of issues with U20.04 and OBS and also your plugin.
Everything disappear with U22: also the plugin can be installed in a while using the deb package.

That's a pity because the new release is a little bit more resource consuming but ok... :)

Anyway, thanks for your answer!

C.

I think believe Ubuntu 20.04 is still using Qt5.
The prebuilt images of the plugin are built for Qt6 however.

This could be confirmed by having a look at an OBS log. (Feel free to share one and I will have a look)

If it should turn out that this is indeed the issue then you cannot use the official releases on GitHub.
Instead you will either have to rely a version available via a package manager (flatpak, snap, ...) or build the plugin yourself.

Let me know if you have any questions!

 

[videored]

Any way to tell this to mute absolutely everything in one particular scene without having to add each source from that scene individually to the macro?

 

[AaronD]

Everything disappear with U22

You mean you upgraded across the v27/v28 boundary, and all your plugins went away? Or do you mean something else?

That specific upgrade is known to do that, as a consequence of the Qt5/6 boundary that corresponds to those versions of OBS. Plugins made for OBS v27 and before, and thus Qt5, are not compatible with Qt6, and thus OBS v28 and later. So they'll fail to load. Because they fail to load, and because OBS overwrites all the settings when it closes, it wipes out the settings that they used to have, even if you downgrade back to what it was.

I really wish OBS itself would have put up a big warning about crossing that boundary, and offered a way to preserve the plugin settings if not the plugins themselves. But it didn't. So people don't think anything special until they see that they've lost all of that, by which time it's too late to recover.

If you know, then you can back up everything explicitly (screenshot if necessary), update the plugins too, and put it all back afterwards. But you have to know, and OBS itself completely failed what I consider to be a responsibility to tell you.

(Still remember that it's free, and both made and supported by volunteers. Nothing is guaranteed like a commercial product is.)