Advanced Scene Switcher

Advanced Scene Switcher 1.36.1

Go to download
Overview Updates (115) Reviews (100) History Discussion
Grampa Wild Willy said:
Since I am using portable OBS, I assume I would need to use portable Advanced Scene Switcher. I'm looking at the documentation for OBS 33 on the subject of the plugin directory structure. I have also downloaded Advanced Scene Switcher 1.36.1 portable for Windows. The OBS 33 doc says there's going to be 2 directories. In my case, they will be named:

C:\OBS-studio\plugins\Advanced Scene Switcher
C:\OBS-studio\plugins\Advanced Scene Switcher\data

I am trying to fit the directories in the portable plugin zip archive for 1.36.1 into the OBS explanation. In your zip archive at the highest level of the tree, you have 2 directories: obs-plugins, data. I am assuming that I will drill down in your zip archive to directory obs-plugins\64bit, a tree structure that will be flattened out of existence in OBS33. From within that directory, I will copy the 2 dll files & the 2 pdb files into my C:\OBS-studio\plugins\Advanced Scene Switcher directory. I will copy the subdirectory named advanced-scene-switcher-plugins from your zip archive into that same directory.

For the data, I will drill down in you zip archive through another directory structure that will also be flattened out of existence, this time it's data\obs-plugins\advanced-scene-switcher. There's 3 subdirectories at that level of your zip archive: licenses, locale, res. I am assuming I will copy those 3 directories into C:\OBS-studio\plugins\Advanced Scene Switcher\data.

This is my attempt to reconcile the old directory structure that appears in your zip archive with the OBS documentation at https://obsproject.com/kb/legacy-plugin-locations in the section with the heading Windows (Portable). Do I have this right? Will I be able to use the advanced-scene-switcher-1.36.1-windows-x64-portable.zip with OBS 33 when it lands? Or will you have to recode anything & issue a new zip file with an updated directory structure? Just to be clear. I'm using portable OBS so I assume I need to use the portable zip file of Advanced Scene Switcher. Is this correct?
Click to expand...
I just had a brief look at the details on how the paths have changed with OBS 33:

Legacy Plugin Locations | OBS

OBS (Open Broadcaster Software) is free and open source software for video recording and live streaming. Stream to Twitch, YouTube and many other providers or record your own videos with high quality H264 / AAC encoding.
obsproject.com obsproject.com

They new differ even to the old ProgramData paths.
So, none of the existing build artefacts will be in accordance with the new layout. (But as mentioned the old format is still supported until OBS 34)
So, it cannot work the way you have tried it just now.
Sorry about that!

I will have to make adjustments and let you know once something is available for you to try. (Probably tomorrow)
 
Grampa Wild Willy said:
Excellent! Thank you! I look forward to your instructions.
Click to expand...
You can find a first build which supports the new layout for OBS 33 here:
(GitHub actions link in case it is preferred: https://github.com/WarmUpTill/SceneSwitcher/actions/runs/38058126799)

You can use the advanced-scene-switcher-1.36.0-27-g3b69f7f5-windows-x64.zip archive if you want to install it by hand.
You should also be able to point the advanced-scene-switcher-1.36.0-27-g3b69f7f5-windows-x64-Installer.exe installer to your OBS portable directory and it will figure out where to place the files.

Let me know if everything works as expected or if you run into any issues!
 
I got the zip archive for the manual installation. It contains 4 zip archives. Two of them are destined for the future OBS 33 that is not yet available. Yes, I know, they're up to RC 1. I'm waiting for the general availability.

In the meantime, the other 2 of the 4 zip archives you have supplied are for the current OBS 32. One is labelled portable & the other is not. Even a dummy like me can figure out that the one with portable as part of its file name is the one for me. And I read the README. Yeah. I know. What a concept. So I just unzipped your portable zip into my existing OBS directory (portable, it's not in %APPDATA% or %ProramFiles%) & opened OBS. It recognized the new version of Advanced Scene Switcher. I think I've got it installed twice in different parts of the OBS directory tree, but I don't really care. I am intending to wipe my current portable OBS directory once OBS 33 lands & start over completely from scratch. I opened the Advanced Scene Switcher window within OBS 32 & it looks like everything is there the way it's supposed to be. I haven't actually done anything to exercise it but it seems to be there, waiting for me to do something to exercise it. So thank you for this . . . and I'll thank you again once OBS 33 lands.
 
Hi,

I'm trying to unpause an ASS macro via a hotkey but I don't see the macro names in the OBS Settings Hotkey window so I don't know which one I would be unpausing.

1792053646733.png


I am on the latest ASS 1.36.1 and OBS and OBS 32.2.2

regards,

David
 
David_G said:
Hi,

I'm trying to unpause an ASS macro via a hotkey but I don't see the macro names in the OBS Settings Hotkey window so I don't know which one I would be unpausing.

View attachment 121603

I am on the latest ASS 1.36.1 and OBS and OBS 32.2.2

regards,

David
Click to expand...
Thanks for letting me know!
This was a regression introduced with 1.36.1.

A build with a fix will be available here in a few minutes:
github.com

Fix macro pause hotkeys not displaying macro name in OBS settings pull request run · WarmUpTill/SceneSwitcher@745dbf7

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

Alternatively, you can use this link, if you don't have a GitHub account:

If you don't want to use a test build, you could temporarily set up a helper macro like this to achieve the same effect:
1792084394039.png


Sorry about the issue!

GeeMack said:
I installed the new manual install zip on OBS 33.0.0rc1 on Windows 11. I don't have a complicated setup or complex macros, but it does seem that everything is working. Thanks.
Click to expand...
Thanks for the feedback!
 
Toofyplayz said:
Hi,
Is there a version that will work with the current OBS Studio?
I've tried everything and cant get it to work :(
any help would be most appreciated.
Click to expand...
Unfortunately, I am not sure which version is being referred to by "current" here.
A build which is compatible with both OBS 33 and OBS 32 can be found here:
github.com

Release Advanced Scene Switcher 1.37.0-beta · WarmUpTill/SceneSwitcher

⬇️ Jump to downloads Important notes: The minimum supported OBS version is OBS 31.1.1. Please make sure to back up your settings! If you run into any issues, please either post in the OBS forums o...
github.com github.com
Let me know, if you need further help!
 
Hi,

I've been using your plugin for some time now with many many macros being used and many iterations of them changing as more functionality comes along or I see a better way of solving a need or the need has evolved.

In this process I've found there are a few things that would make maintaining these macros easier.

1. I'd love the ability to see where a given variable has been used or a least a count of how many times it has been referenced in a macro. This would help to be able to cleanup up obsolete variables or to fix when I've imported a new variable with the same name but different case as an existing variable (such as already having a variable called varTrue then importing one called VarTrue).

2. Only exporting variables referenced by the macros being exported. So when I have 40 variables but the macros being exported are only referring 5 of those macros I still get the full 40 being sucked up in my import and I don't have an easy way of determining which I don't really need (See above).

3. Finding macros which have fields not filled in like "If Scene Current Scene is {select scene}" or a macro like "variable Set to value {select variable}", which happens when I deleted the "VarTrue" variable instead of the "varTrue" variable.

I love the plugin but sometimes these little issues add a lot of work.

cheers,

David


Across
 
Warmuptill said:
Thanks for letting me know!
This was a regression introduced with 1.36.1.

A build with a fix will be available here in a few minutes:
github.com

Fix macro pause hotkeys not displaying macro name in OBS settings pull request run · WarmUpTill/SceneSwitcher@745dbf7

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

Alternatively, you can use this link, if you don't have a GitHub account:

If you don't want to use a test build, you could temporarily set up a helper macro like this to achieve the same effect:
View attachment 121613

Sorry about the issue!


Thanks for the feedback!
Click to expand...
Thanks for the fix. I'm going with the new build and I'll also be looking at 1.37.0 beta
 
The flexibility of Advanced Scene Switcher is incredible. Being able to create macros based on audio levels and timers takes a massive cognitive load off solo operators during a live broadcast. Truly one of the most powerful tools in the OBS ecosystem.
 
David_G said:
Hi,

I've been using your plugin for some time now with many many macros being used and many iterations of them changing as more functionality comes along or I see a better way of solving a need or the need has evolved.

In this process I've found there are a few things that would make maintaining these macros easier.

1. I'd love the ability to see where a given variable has been used or a least a count of how many times it has been referenced in a macro. This would help to be able to cleanup up obsolete variables or to fix when I've imported a new variable with the same name but different case as an existing variable (such as already having a variable called varTrue then importing one called VarTrue).

2. Only exporting variables referenced by the macros being exported. So when I have 40 variables but the macros being exported are only referring 5 of those macros I still get the full 40 being sucked up in my import and I don't have an easy way of determining which I don't really need (See above).

3. Finding macros which have fields not filled in like "If Scene Current Scene is {select scene}" or a macro like "variable Set to value {select variable}", which happens when I deleted the "VarTrue" variable instead of the "varTrue" variable.

I love the plugin but sometimes these little issues add a lot of work.

cheers,

David


Across
Click to expand...
Thanks for the feedback and suggestions!

A new build is available here:
Or here on GitHub if you have an account:
github.com

Var track pull request run · WarmUpTill/SceneSwitcher@f470169

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

It adds the possibility to see how often a variable is used and where, by providing this information on the "Variables" tab.
1792516334887.png

It also introduces the possibility to search / filter variables by variable:

Example.gif


The export option now only selects the relevant variables by default:
export.gif


I don't really have a good solution for the third point you brought up, unfortunately.
I fear supporting such functionality might require a major rework.

Regardless, let me know, if you face any issues with the test build!
 
Warmuptill said:
Thanks for the feedback and suggestions!

A new build is available here:
Or here on GitHub if you have an account:
github.com

Var track pull request run · WarmUpTill/SceneSwitcher@f470169

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

It adds the possibility to see how often a variable is used and where, by providing this information on the "Variables" tab.
View attachment 121669
It also introduces the possibility to search / filter variables by variable:

View attachment 121670

The export option now only selects the relevant variables by default:
View attachment 121671

I don't really have a good solution for the third point you brought up, unfortunately.
I fear supporting such functionality might require a major rework.

Regardless, let me know, if you face any issues with the test build!
Click to expand...
That's brilliant. It's made things much easier.

Fair enough about point 3. I'm just very appreciative that you've done what you have and so quickly.

I have not found any issues with it
 
You must log in or register to reply here.
Back
Top