Advanced Scene Switcher

Advanced Scene Switcher 1.31.0

cdante100

New Member
The second recording seemed fine and was successfully paused and unpaused, as far as I can tell from the log:
Code:
### first recording starts here ###
14:01:42.069: ==== Recording Start ===============================================
### (un)pausing and macros also seem to work as far as I can tell ###
14:41:01.120: [adv-ss] spent 515 ms in video condition check of macro 'T Unpause recording'!
### recording stops ###
17:10:07.624: ==== Recording Stop ================================================
...
### second recording starts here ###
18:07:22.003: ==== Recording Start ===============================================
18:07:22.003: [ffmpeg muxer: 'adv_file_output'] Writing file 'C:/Users/Utente/Videos/OBS/2025-09-16 18-07-21.mkv'...
18:07:26.981: output adv_file_output paused
18:07:26.994: output adv_file_output unpaused
...
### shutdown issue ###
18:07:56.473: ==== Shutting down ==================================================
...
18:08:01.636: [adv-ss] started
...
The only issue I could find in the log was the shutdown issue.

So, I am unfortunately not sure what the problem could be.
Maybe the pause and unpause in the second recording happen too quickly one after another and "confuse" OBS?
when it does that problem it immediately removes the pause (less than 1 second later) and from then on it is no longer possible to pause it, stop the recording, or even close obs, maybe that's the problem, now I'll try to add a little wait and in case the problem arises again I'll write again here
 
Is there a solution to get AdvSS to save the position of the docks? If a different scene from "scene collections" is selected, I have to reselect the docks and manually reposition them within the OBS GUI manually.

View attachment 115657

Look into jrDockie.
It allows you to save a dock setup preset to a file, and reload it when needed.

There is even a method to force-load a preset by name, via scripting.
 

reflogwa9898

New Member
After updating OBS to the latest version 32.0 tonight, when I open OBS I get a message saying that it could not load the advanced scene switcher plugin. Apparently OBS has a new plug-in manager as of version 32.0. Is there a version of the plug-in I can update to to resolve this issue?

Thanks.
 

Warmuptill

Active Member
After updating OBS to the latest version 32.0 tonight, when I open OBS I get a message saying that it could not load the advanced scene switcher plugin. Apparently OBS has a new plug-in manager as of version 32.0. Is there a version of the plug-in I can update to to resolve this issue?

Thanks.
I am very sorry about that!
I will try to look into it as soon as I can (which probably will only be tomorrow, unfortunately).

Which version of the advanced scene switcher are you using?
Which OS are you using?

I thought I had tested the latest advanced scene switcher release with the OBS 32 beta releases and it was working fine.
I will make sure to verify that again tomorrow.
If you haven't done so already it might be worth a shot simply installing the most recent release once again.

Pinging @Daniel-House-1242 since he reported the same problem.
 
Last edited:

Daniel-House-1242

New Member
I am very sorry about that!
I will try to look into it as soon as I can (which probably will only be tomorrow, unfortunately).

Which version of the advanced scene switcher are you using?
Which OS are you using?

I thought I had tested the latest advanced scene switcher release with the OBS 32 beta releases and it was working fine.
I will make sure to verify that again tomorrow.

Pinging @Daniel-House-1242 since he reported the same problem.
Hello, I'm really sorry to have alarmed you for nothing. I had an older version in another computer and i was not aware of that. I always test new versions of OBS on another older coputer BEFORE to go live, so i forgot to update the advanced scene switcher (it was V1.20) . I just installed v1.31 right now and it's perfectly working! Thanks and sorry again. If you can, please delete my review and i will be happy to write it again. I can't edit since you commented. Thanks!
 

reflogwa9898

New Member
I am very sorry about that!
I will try to look into it as soon as I can (which probably will only be tomorrow, unfortunately).

Which version of the advanced scene switcher are you using?
Which OS are you using?

I thought I had tested the latest advanced scene switcher release with the OBS 32 beta releases and it was working fine.
I will make sure to verify that again tomorrow.
If you haven't done so already it might be worth a shot simply installing the most recent release once again.

Pinging @Daniel-House-1242 since he reported the same problem.

I am very sorry about that!
I will try to look into it as soon as I can (which probably will only be tomorrow, unfortunately).

Which version of the advanced scene switcher are you using?
Which OS are you using?

I thought I had tested the latest advanced scene switcher release with the OBS 32 beta releases and it was working fine.
I will make sure to verify that again tomorrow.
If you haven't done so already it might be worth a shot simply installing the most recent release once again.

Pinging @Daniel-House-1242 since he reported the same problem.
Thanks for the response. I updated to v1.31 and everything works fine now. I had not updated advanced-scene-switcher since I originally installed it in 2023
 

zagorskey

New Member
Hi,

Since updating to OBS 32.0.0 and the new canvas system, Advanced Scene Switcher 1.31.0 doesn't list Aitum Vertical Plugin's vertical scenes/sources anymore. I do hope it's a known issue and a fix is coming as 99% of my macros rely on vertical scenes/sources.

Is there any temporary workaround that could be applied?
 

cesch1n

New Member
Can somebody help me. I want my audience be able to sawp scenes when they enter a specific keyword on my twitch chat
 

Warmuptill

Active Member
Hi,

Since updating to OBS 32.0.0 and the new canvas system, Advanced Scene Switcher 1.31.0 doesn't list Aitum Vertical Plugin's vertical scenes/sources anymore. I do hope it's a known issue and a fix is coming as 99% of my macros rely on vertical scenes/sources.

Is there any temporary workaround that could be applied?
I will try to look into it.

What do your macros look like?
Maybe I can think of a workaround.

Can somebody help me. I want my audience be able to sawp scenes when they enter a specific keyword on my twitch chat
That should be doable using a macro like this:
1759497294295.png

You will of course have to adapt the channel name, the "!MyChatTrigger", and scene accordingly.
 

Indefa

New Member
I have just updated my plugin from 1.27.2 to 1.31 and before doing so I exported out my settings. Now when I import the settings back in my Macros appear but all of them show "unknown action" or "unknown condition". Did I mess up by not backing them up correctly? Was I suppose to individually export the macros in order to save them?
 

Attachments

  • 08_19-58-26 (mstsc).png
    08_19-58-26 (mstsc).png
    53 KB · Views: 7
  • adv-ss-SSB64Australia 2024-2025.10.07.20.37.36.txt
    12.5 KB · Views: 7

Indefa

New Member
I have just updated my plugin from 1.27.2 to 1.31 and before doing so I exported out my settings. Now when I import the settings back in my Macros appear but all of them show "unknown action" or "unknown condition". Did I mess up by not backing them up correctly? Was I suppose to individually export the macros in order to save them?
I just took a closer look at my export and noticed a lot of "id":"unknown" within the macros. So I'm guessing the export just didn't work correctly and everything lost it's name somehow :(
 

Warmuptill

Active Member
I have just updated my plugin from 1.27.2 to 1.31 and before doing so I exported out my settings. Now when I import the settings back in my Macros appear but all of them show "unknown action" or "unknown condition". Did I mess up by not backing them up correctly? Was I suppose to individually export the macros in order to save them?
I just took a closer look at my export and noticed a lot of "id":"unknown" within the macros. So I'm guessing the export just didn't work correctly and everything lost it's name somehow :(
That seems very strange.
I don't recall there being a problem with the settings export in that version, but maybe I just forgot about it.

There might be an automatic backup file in the plugin_config directory.
If you are using Windows you can usually find it at:
C:\Users\<your username here>\AppData\Roaming\obs-studio\plugin_config\advanced-scene-switcher
It will be named after the scene collection it belongs to.
 

surgestone23

New Member
Unfortunately there is no indication of the advanced scene switcher even being loaded in the log you shared.
Do you have a crash log as well?
On MacOS this should be contained in the dialog window popping up informing you that OBS crashed.

In case you did not use the installer and manually placed the files in the corresponding directories please ensure to "sign" the files afterwards as described here:
 

Indefa

New Member
That seems very strange.
I don't recall there being a problem with the settings export in that version, but maybe I just forgot about it.

There might be an automatic backup file in the plugin_config directory.
If you are using Windows you can usually find it at:
C:\Users\<your username here>\AppData\Roaming\obs-studio\plugin_config\advanced-scene-switcher
It will be named after the scene collection it belongs to.
I found two .json files in there from the day I did the update but they are both almost the same as the other exports I did manually did. I'm not sure how much stuff should be in there but it does appear all the actual settings etc. are in the files, it's just the ID of each source/scene has been lost somehow. I'm guessing I'm out of luck.
 

Attachments

  • settings-backup-SSB64Australia 2024-1.27.2.txt
    12.6 KB · Views: 4
  • settings-backup-SSB64Australia 2024-1.31.0.txt
    14.8 KB · Views: 4

Garryk

New Member
Hello) First, thank you for this cool plugin, it's really save a lot of time for me!

But i have a problem: for some reason, the point reward event often doesn't work.
"Points reward redeemed" usually works for a few minutes after the stream starts, and then the event stops tracking. I'm attaching the log. Please help. Thank you!

Full log is too large for uploading here, so: https://dropmefiles.com/WxFTT
 

Warmuptill

Active Member
OSB seems to crash in the asio lib after calling WSServer::WSServer().
To me this seems very similar to the following problem:

Which version of the advanced scene switcher plugin did you install?
The WSServer::WSServer() related code was removed from the plugin quite a while ago with the removal of the "Network" tab.
I am not sure if that old version is still compatible with the OBS version you are using.
Can you try installing the most recent release or is something preventing you to do so?

I found two .json files in there from the day I did the update but they are both almost the same as the other exports I did manually did. I'm not sure how much stuff should be in there but it does appear all the actual settings etc. are in the files, it's just the ID of each source/scene has been lost somehow. I'm guessing I'm out of luck.
Sadly I can't think of a reason why this happened and how to resolve it :(

Hello) First, thank you for this cool plugin, it's really save a lot of time for me!

But i have a problem: for some reason, the point reward event often doesn't work.
"Points reward redeemed" usually works for a few minutes after the stream starts, and then the event stops tracking. I'm attaching the log. Please help. Thank you!

Full log is too large for uploading here, so: https://dropmefiles.com/WxFTT
I am sorry to hear that!

I have a suspicion what the problem might be. (Improper handling of the session_reconnect event)

Can you please check if the problem is resolved in the following test build:
Unfortunately, you will have to be logged into GitHub to be able to download it at the bottom of the page.
If that should be problem let me know and I will try to share with you via other means.
 
Last edited:

Garryk

New Member
OSB seams to crash in the asio lib after calling WSServer::WSServer().
To me this seems very similar to the following problem:

Which version of the advanced scene switcher plugin did you install?
The WSServer::WSServer() related code was removed from the plugin quite a while ago with the removal of the "Network" tab.
I am not sure if that old version is still compatible with the OBS version you are using.
Can you try installing the most recent release or is something preventing you to do so?


Sadly I can't think of a reason why this happened and how to resolve it :(


I am sorry to hear that!

I have a suspicion what the problem might be. (Improper handling of the session_reconnect event)

Can you please check if the problem is resolved in the following test build:
Unfortunately, you will have to be logged into GitHub to be able to download it at the bottom of the page.
If that should be problem let me know and I will try to share with you via other means.
I tested the reward events during a 5-hour stream, and it's worked perfectly! I'll continue testing, and if anything goes wrong, I'll get back to you with the logs)

Thank you so much ❤️
 

Lycanthrope -R-

New Member
Hi. Thanks for the plugin and for your help as always. I'm working off of 1.31 with OBS 32.0.1

1. I don't know when it started exactly, likely with an OBS Update. But the default behavior of OBS is if there is sound playing on a scene, switching to a different scene without that source will fade out the sound.

However, in using Advance Scene Switcher, a macro switching the scene may or may not fade out the sound. It will just abruptly cut off. It seems to happen if you don't set the duration for the transition in the macro. (i assume it then defaults to something?) It seems to fix itself if you do set the duration.
Screenshot 2025-10-15 004627.png


Steps to reproduce:
  • Record
  • Have a scene with a sound source source playing.
  • Switch to a scene without the sound source.
  • Sound fades out normally.
    • Record
    • Have a scene with a sound source source playing.
    • Trigger a macro to switch the scene to one without the sound source, but don't set the transition duration.
    • Sound cuts off abruptly.

2. Triggering a scene transition via a macro using "Current Transition" will ignore the Transition Override set on the scene itself.
Screenshot 2025-10-15 003320.png
Screenshot 2025-10-15 004059.png

Screenshot 2025-10-15 003359.png


So, in this scenario, the macro will ignore the Fade Transition Override and still use the Luma Wipe. Now, I can just set the macro transition to Fade rather than Current Transition. But doing will change the standard Scene Transition to Fade, and I'd have to manually switch it back to Luma Wipe if that's what I'd normally be using. That, and I'm not sure if ignoring the Transition Override is desired behavior. I'm fairly sure it didn't used to do that.

Could these be looked into? Thanks again for any help that can be provided.
 

Warmuptill

Active Member
Hi. Thanks for the plugin and for your help as always. I'm working off of 1.31 with OBS 32.0.1

1. I don't know when it started exactly, likely with an OBS Update. But the default behavior of OBS is if there is sound playing on a scene, switching to a different scene without that source will fade out the sound.

However, in using Advance Scene Switcher, a macro switching the scene may or may not fade out the sound. It will just abruptly cut off. It seems to happen if you don't set the duration for the transition in the macro. (i assume it then defaults to something?) It seems to fix itself if you do set the duration.
View attachment 116104

Steps to reproduce:
  • Record
  • Have a scene with a sound source source playing.
  • Switch to a scene without the sound source.
  • Sound fades out normally.
    • Record
    • Have a scene with a sound source source playing.
    • Trigger a macro to switch the scene to one without the sound source, but don't set the transition duration.
    • Sound cuts off abruptly.

2. Triggering a scene transition via a macro using "Current Transition" will ignore the Transition Override set on the scene itself.
View attachment 116101View attachment 116103
View attachment 116102

So, in this scenario, the macro will ignore the Fade Transition Override and still use the Luma Wipe. Now, I can just set the macro transition to Fade rather than Current Transition. But doing will change the standard Scene Transition to Fade, and I'd have to manually switch it back to Luma Wipe if that's what I'd normally be using. That, and I'm not sure if ignoring the Transition Override is desired behavior. I'm fairly sure it didn't used to do that.

Could these be looked into? Thanks again for any help that can be provided.
1. At least I am not aware of having changed anything in regard to the transition / audio areas of the plugin, which would explain such behavior.
I will look into it.

2. You can configure how the plugin will behave in regard to transition overrides on the General tab.
 

ottawafro

Member
Any plans in the future to have search / filter implement to search for macros containing a certain source , search by macros name ... something along those lines.
I find it takes me a long time to find macros i need to edit cause i have so many and don't always recall what the macros name is or where it is located in my very long list of macros .
 
Top