I installed it with the .exe, perhaps the directory I pointed it to was incorrect? This is the newest version.
Plugin Directory:
Last edited:
- Thread starter Warmuptill
- Start date
Plugin Directory:
Nevermind. I got it to work. Did a complete deletion of all plugin files and a clean install. It works now. Thank you!
xX_Van_Helsing_Xx
New Member
is there a way to supress the warning the plugin throws after obs crashes - No I don't want to stop the Plugin after a crash
OBS did not shut down cleanly (for example, due to a crash or freeze).The Advanced Scene Switcher plugin would normally start automatically.Would you like to keep it stopped for now?
NO - I found that I can click No with Alt+N after the message gets focus - but I need it to always say No
OBS did not shut down cleanly (for example, due to a crash or freeze).The Advanced Scene Switcher plugin would normally start automatically.Would you like to keep it stopped for now?
NO - I found that I can click No with Alt+N after the message gets focus - but I need it to always say No
OsirisRA
New Member
Thanks for sharing the example macro!
Unfortunately, I am not able to observe any issues on my side when using such a macro.
View attachment 118995
Can you please enable verbose logging on the General tab of the plugin and share an OBS log with a reproduction of the issue:
Troubleshooting
An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.github.com
Please also note down the time at which the problem occurred since verbose logs can become rather large very quickly.
I manged to change things around for the macros that was having problems with and changed this around a bit manly used exact timings instead of using for at least which seems to have fixed the issues. Thanks for your time.
Warmuptill
Active Member
Sorry about that!
I will make sure to include an option to suppress this warning permanently.
xX_Van_Helsing_Xx
New Member
Thank you very much ..
I think I found it - Since -disable-startup-Check was removed I delete .sentinel .. and for the Plugin it schould be .running ..
Thank you for your awesome work !
Warmuptill
Active Member
Unfortunately, I wasn't able to replicate this transition issue on my side.
This is what I have tried:
Do you have any additional hints how to reproduce it on my side?
Sorry if I simply misunderstood what the problem is!
KattPhloxworthy
Member
I'll have to do some other testing to make sure it really is Advanced Scene Switcher causing it, though some are happening to scenes whose transitions are being handled by Transition Table.
To be frank, though, my current setup is way beyond a need of a total refresh, both in bulk (with granularity going as fine as backing up the entire %APPDATA%\obs-studio tree to as coarse as the entire partition or even the drive everything resides on) as well as from within OBS Studio and the various plugins' interfaces, e.g. Advanced Scene Switcher's own.
More soon. In any event, I'm likely gonna be stuck on 32.0.4 for a while to come. I just don't want support for vertical canvases to be the thing that kills my setup, especially I don't have a use for them and don't want to deal with them anyway.
--Katt.
KattPhloxworthy
Member
UPDATE: I can manually create new rulesets within Advanced Scene Switcher, both in OBS Studio 32.1.0 and 32.0.4 using the Scene Switcher 1.32.9 and they'll work fine. My older stuff that has been around since long before a secondary (nearly always vertical) canvas was a thing.
I tried creating a new version of one of the events that uses a fade but it does a cut instead, like the old one.
Create from completely new rule list (e.g. via a new scene set) and they work fine.
Unless I can figure out the differences between the new and old ones, I may have to do this all over again from scratch, by hand.
Not fun.
Of course, unless you have some other ideas I can try?
--Katt. =^.^=
HOW DO I INSTALL THIS IN OBS STEAM? I need step-by-step instructions. I'm a newbie. I've been struggling with the installation for half an hour. WHY HAS NO ONE MADE A GUIDE? I moved the files to the root folder, I moved the files to plugins, but where do I open this script in the program?
Warmuptill
Active Member
Unfortunately, I don't have any other ideas at the moment.
HERE YOU GO:
Download the advanced-scene-switcher-*-windows-x64.zip archive.
Next, right click on OBS in steam.
Select "Manage", then "Browse local files".
Extract the contents of the advanced-scene-switcher-*-windows-x64.zip archive into this directory, so that the contents of the
data folder will be merged into OBS' data folder and the contents of the obs-plugins folder will be merged into OBS' obs-plugins folder.Next up launch or restart OBS and the plugin should be accessible via "Tools" -> "Advanced Scene Switcher" within OBS.
HOPE THIS HELPS! :D
If it does not can you please share an OBS log and a screenshot of what the
obs-plugins/64bit folder of OBS looks like.To be honest I didn't even know installing OBS via Steam was an option.
I will add instructions to the wiki page.
Last edited:
Hi,
I'm experiencing a consistent crash with Advanced Scene Switcher (latest version) on OBS 32.1.0 (64-bit) under Windows 10.
**Crash happens exactly when:**
- Switching to a different Scene Collection
- Closing OBS
The plugin works perfectly during normal use. The crash only occurs during the stop/unload phase.
**Crash details:**
- Exception: `c0000005` (access violation)
- Fault address: `w32-pthreads.dll!pthread_mutex_unlock+0x27`
- Stack trace always points to:
```
advanced-scene-switcher-lib.dll!advss::SendWebsocketVendorEvent
→ advss::RunStopSteps
→ advss::SwitcherData::Stop
→ advss::SwitcherData::~SwitcherData
→ FreeSceneSwitcher
→ obs.dll!free_module + obs_shutdown
```
It looks like the plugin is trying to send a WebSocket vendor event while its internal `SwitcherData` object is being destroyed, causing the mutex to be unlocked in an invalid state.
I can reproduce it 100% of the time just by switching scene collections.
Would it be possible to add a safeguard (or make the WebSocket event on stop optional) so the plugin doesn't crash during collection switch / shutdown?
Thanks in advance!
I'm experiencing a consistent crash with Advanced Scene Switcher (latest version) on OBS 32.1.0 (64-bit) under Windows 10.
**Crash happens exactly when:**
- Switching to a different Scene Collection
- Closing OBS
The plugin works perfectly during normal use. The crash only occurs during the stop/unload phase.
**Crash details:**
- Exception: `c0000005` (access violation)
- Fault address: `w32-pthreads.dll!pthread_mutex_unlock+0x27`
- Stack trace always points to:
```
advanced-scene-switcher-lib.dll!advss::SendWebsocketVendorEvent
→ advss::RunStopSteps
→ advss::SwitcherData::Stop
→ advss::SwitcherData::~SwitcherData
→ FreeSceneSwitcher
→ obs.dll!free_module + obs_shutdown
```
It looks like the plugin is trying to send a WebSocket vendor event while its internal `SwitcherData` object is being destroyed, causing the mutex to be unlocked in an invalid state.
I can reproduce it 100% of the time just by switching scene collections.
Would it be possible to add a safeguard (or make the WebSocket event on stop optional) so the plugin doesn't crash during collection switch / shutdown?
Thanks in advance!
Warmuptill
Active Member
I assume the full crash log looks something like this:
Code:
0000005AD56FB160 00007FFF62145277 0000025429323D80 0000025429323D80 0000005AD56FB240 00007FFEEC70C5E0 w32-pthreads.dll!pthread_mutex_unlock+0x27
0000005AD56FB1A0 00007FFF2A8A7DC0 00000253926B0AD0 0000000000000000 0000025429340C00 00007FFEEC6709CF obs.dll!proc_handler_call+0x80
0000005AD56FB220 00007FFEEC65825C 00000253DC275060 00000253DC274FE0 0000025429340C00 00007FFEEC39E576 advanced-scene-switcher-lib.dll!advss::SendWebsocketVendorEvent+0xdc
0000005AD56FB270 00007FFEEC657DBA 0000000000000001 000002538FE4C000 0000000000000000 00007FFEEC89E0D0 advanced-scene-switcher-lib.dll!std::_Func_impl_no_alloc<`advss::setup'::`2'::<lambda_2>,void>::_Do_call+0x7a
0000005AD56FB2E0 00007FFEEC639D3F 00007FFEEC89E0D0 000002538FE4C000 0000000000000288 00000254278026C0 advanced-scene-switcher-lib.dll!advss::RunStopSteps+0x5f
0000005AD56FB320 00007FFEEC36E88C 00007FFEEC89E0D0 0000025421C55540 00000253BD625DE0 00007FFF2FFB285B advanced-scene-switcher-lib.dll!advss::SwitcherData::Stop+0xbc
0000005AD56FB3A0 00007FFEEC36A32B 0000025421C55540 0000000000000000 0000000000000288 00000253BD625DE0 advanced-scene-switcher-lib.dll!advss::SwitcherData::~SwitcherData+0x2b
0000005AD56FB3F0 00007FFEEC38A264 0000025427991040 000002542772EB00 00000253B9914C40 00000253B9812C88 advanced-scene-switcher-lib.dll!FreeSceneSwitcher+0x24
0000005AD56FB420 00007FFF2A83DBCE 0000000000000288 00000253BD625DE0 0000005AD56FB650 0000000000000288 obs.dll!free_module+0x3e
0000005AD56FB450 00007FFF2A8845C0 0000000000000000 0000005AD56FF4F0 0000005AD56FB599 0000025429459510 obs.dll!obs_shutdown+0x370While the call stack does contain advss functions that particular type of crash is not caused by the advss plugin necessarily.
As you already pointed out the advss is just trying to emit a websocket event when changing scene collections.
The crash happens within the proc_handler_call call of the obs_websocket_vendor_emit_event function of the OBS websocket API.
The mutex in question is an OBS internal one and not used by the advss directly.
This can happen when there are source leaks anywhere in OBS (most likely a plugin).
I previously spent quite a bit of time trying to track down a potential issue within advss somehow corrupting OBS, but it ultimately turned out that a different plugin was just leaking resources.
Once I fixed the leak in the other plugin the issue was gone immediately.
I assume even if you completely disable the advanced scene switcher via plugin manager you will instead run into an the "Source Cleanup Error" being reported:
If that is the case I would suggest disabling all plugins and turning them back on one by one to narrow down which one is the culprit.
But just in case can you please share the full crash log?
Then I will have another look.
Warmuptill
Active Member
The plugin can only "do stuff" when OBS is already running.
So, unfortunately you can't use it to launch OBS.
Sorry, if I misunderstood you question!
Danny Teunissen
New Member
Hey @Warmuptill here is the log from the discussion on the other page.
The marco runs ok if i press run macro.
best regards Danny
The marco runs ok if i press run macro.
best regards Danny
Last edited:
Warmuptill
Active Member
Thanks for sharing the problematic macro!
I think you might have accidentally changed an "Or" to an "And" in your macro:
While the individual date conditions can become true both of them cannot be true at the same time.
Let me know, if changing it back to an "Or" fixes your issue!
Danny Teunissen
New Member
Jup saw that :-) I attached a image what happens. The pc time is now 21:03 nothing seems changed or start running .
Attachments
Danny Teunissen
New Member
I also see a object button under a object button ? See image or did i see this wrong .
The field is big enough.
Attachments
Warmuptill
Active Member
As far as I can tell the macro seems to do what it is supposed to:
You have quite a few "wait" actions in there.
By default macro will not be executed again while it is currently still running.
So, the action execution might just have been skipped because the macro actions are still being executed.
You can change that behavior in the settings of the macro:
I did however notice one visual bug:
The "repeat every ..." option does not update the settings unless you close the advanced scene switcher settings window completely.
In the past it did update when switching away from the macro and back again.
(The "Next match at: ..." field did however update correctly)
I will make sure to fix that in the next release, so that the date / time field updates again when switching between macros.
That is just how the time selection widget from Qt looks.
I don't think there is anything missing here.
One of the "buttons" on the right side of the widgets increments the time and the other decrements it.
(I do agree that it looks a bit strange though :D)
Sorry if I misunderstood what you meant here.