Advanced Scene Switcher

Advanced Scene Switcher 1.33.1

Go to download
Overview Updates (109) Reviews (97) History Discussion
Warmuptill said:
As far as I can tell the macro seems to do what it is supposed to:

View attachment 119051

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:

View attachment 119053

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.
Click to expand...
Thank you . I go test this. Sorry for all the wait in the Marco. It's a community station running 24/7 it's runs for 3 years now with the same Marco. Never had a problem. But the now the problems started. This weekend the macro started but not at the given time. Yesterday after I did the update it did not even start.

If you want to see what scene switcher did with our community channel follow the link :-) https://rtvideaal.nl/kijk-ideaaltv/
 
Danny Teunissen said:
Thank you . I go test this. Sorry for all the wait in the Marco. It's a community station running 24/7 it's runs for 3 years now with the same Marco. Never had a problem. But the now the problems started. This weekend the macro started but not at the given time. Yesterday after I did the update it did not even start.

If you want to see what scene switcher did with our community channel follow the link :-) https://rtvideaal.nl/kijk-ideaaltv/
Click to expand...
Its working again. Thx for your efforts. Happy Easter.
 
Warmuptill said:
I have adapted how machting patterns are counted in this build:
github.com

Rework pattern count temp var pull request run · WarmUpTill/SceneSwitcher@0537d73

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com github.com
Basically ignores overlapping matches.
Does this produce the expected result for your setup?
Click to expand...
Yes the matching variable value works now as i would expect it to. Thank you!!

Would it be a possibility for the system to provide some x/y values of matches? Would be interesting if I could use that info to make an app highlight on the screen for viewers. So if it found 3 matches on a screen, it could be stored as a system variable or something that could be used to identify the position.
Match 1 = 900,300
Match 2 = 1910 ,1050
 
export your macro and post it. We can trouble shoot it perhaps

1775421581222.png
 
Warmuptill said:
Unfortunately, I don't have any other ideas at the moment.
Click to expand...

I have been able to create an entirely new config and have it work. My existing configuration does not.

I am at my end of my rope and am willing to stay at 32.0.4 for forever if I want to keep Aitum Stream Suite but if I have to go to OBS Studio 32.1.1, I will have to ditch Aitum Stream Suite.

I am desperate to have this looked at. At this point, I would even be willing to let you have a look at my config files so you can look at my configs.

I would send you the entire scene file, not just the AdvSS config file. Rebuilding my entire scene files is likely to be an option but that's a lot of work to have to redo.

--Katt. =^.^=
 
Hey
@Warmuptill
,Thanks a lot for your answer!You're right, it's not an Advanced Scene Switcher issue. I've isolated the plugin and confirmed that the problem is actually related to StreamUP.
Warmuptill said:
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+0x370

While 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:
View attachment 119037

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.
Click to expand...
 

How to disable the window "The program terminated abnormally: continue in safe mode or normal mode"? After a power outage or other reason, the OBS displays a warning that the program has terminated abnormally and should continue in safe or normal mode. How can I permanently disable this notification? I'm constantly forgetting to press the button to launch the OBS, which leads me to believe it launched after restarting the computer and is running automatically, but that's not the case. I've already lost a valuable shot because of this warning, and this can't continue.​

 
You must log in or register to reply here.
Back
Top