Advanced Scene Switcher

Advanced Scene Switcher 1.37.2

Go to download
Overview Updates (117) Reviews (101) History Discussion
ArdSagart said:
Yep. We had a short conversation about 6 months ago. I encontered a similar issue, you said it was a timestamp. I downloaded some very special version of the plugin and the problem disappeared. Everything was ok after updating to 1.31.0
This is the log when I expected a chat message in 1.32.2
Click to expand...
I see.

I don't think anything changed in 1.32 regards to the timestamp verification of Twitch events / chat messages.
But I will try to have another look and reproduce the issue.

The log snippet itself seems fine - as in, there are no errors reported regarding the connection to the Twitch servers.

ArdSagart said:
By some reason OBS is not creating a crash report, but the new log starts from
Click to expand...
That can happen if there is a "deadlock".
If it is not a problem for you, can you share the complete log from where OBS was frozen on shutdown?
That might help me track down what caused that to happen.
 
Deliverator said:
Hi! First of all, FANTASTIC piece of plugin. I can't overstate how much it has made my life easier!

I am getting into the variables system. I do use a variables system through Touch Portal ( ElGato StreamDesk's alternative on your Android device) and I can't find a way to inter-connect the variables of them both so as to have a better control over OBS.

There are things that I need to run through Touch Portal as I have a quide in-depth system already running over there, but I also need the controll given by variables within Scene Switcher.

Any idea on how could i made them talk? I don't mind if I need some janky solution, as far as it works!
Click to expand...
Unfortunately, I don't have any experience with Touch Portal.
If it can send out OBS websocket vendor requests that might be a way to do it.
Then you could use the "Websocket" condition and action to exchange messages.
github.com

Websockets

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com github.com
 
Warmuptill said:
Unfortunately, I don't have any experience with Touch Portal.
If it can send out OBS websocket vendor requests that might be a way to do it.
Then you could use the "Websocket" condition and action to exchange messages.
github.com

Websockets

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com github.com
Click to expand...
Thank you! Yes, it does work with Websockets. Will investigate!
 
Frozen Bok said:
Hello. How to avoid a millisecond of black screen while transition between static (images, background color) and non-static (video, playlist) sources using "Cut"?
Here is example of this problem: https://drive.google.com/file/d/1be7HK2e4PJBoVVzX5dfUWJ4BDS-IBMFt/view?usp=sharing (sorry but loaded file does not support 50 fps as I recorded, so pay attention on the second part)
Click to expand...
I am not sure that this can solved in any way on the Advanced Scene Switcher side.
What type of sources are you using on the relevant scenes?
Is a source maybe configured to only load when visible?
If so, then that brief flicker might be caused by the source loading whatever file / resource it is playing back.

Maybe you could use a fade with a very short duration to mask the issue?
 
Warmuptill said:
Can you share a crash log and OBS log?
Which version of the plug-in are you using?

Backups should automatically created if the version you are using is not too old:
github.com

Saving and loading settings

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

This wiki page also describes where your settings are stored.
Click to expand...
FYI I looked up the log and put it into ChatGPT and it pointed out I still had an old websocket legacy compat plugin for the OBS 28->29 transition and it was crashing the plugin. Renaming it to obs-websocket-compat.disabled rather than obs-websocket-compat.plugin allowed it to load without crashing.
 
Warmuptill said:
I am not sure that this can solved in any way on the Advanced Scene Switcher side.
What type of sources are you using on the relevant scenes?
Is a source maybe configured to only load when visible?
If so, then that brief flicker might be caused by the source loading whatever file / resource it is playing back.

Maybe you could use a fade with a very short duration to mask the issue?
Click to expand...
It's OBS related problem in general. I want ideal transition with no black miliseconds
 
I have generally ok luck with the Advanced Scene Switcher, it really does a great job of following my train of thought around my process based on scene change using percent change of selected picture regions. Switches to 10 + 5 different scenes on 2 computers with OBS connecting and compiling across the 2 computers over the NDI network OBS plugin.

Are there any ideas with such a setup as to whether there is a good way to keep minimal duration switches (flashing scenes quickly switching to another scene and one scene on one computer switching a small amount of time after a scene on the other computer switches) off the final video? I can't follow any normal algorithm for success because as both computers are running the switcher, there would need to be some cross talk for it to agree when to change the scene smoothly from both computers. I am frankly not even sure if it is working with all good intervals on either computer by themselves. I see quite a few short snippets of scenes or quick jumps.

It doesn't bother me but I suppose it looks glitch + wrong to outsiders? Anyone ever successfully got the scene switching to sync up? Is there any network syncing mechanism that I don't know about for 2 computer Adv.S.S. setup? Something that could grab a tempo and just use it. A nice slow tempo.
 
Last edited:
Tallicia said:
Love the updates! Absolutely fantastic!

One/Two quick questions/requests. Can the variables be dockable, able to be opened in a separate window so that the macros can be seen side by side with the variables? - And for icing on the cake, could a search/filter top entry field be added to filter the variables displayed?

Thank you, as always!
Click to expand...
A build with the option to filter and dock the variables tab is available here:
github.com

master push run · WarmUpTill/SceneSwitcher@555f7c1

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

You will have to be logged into Github to be able to download it at the bottom of the page.
If that should be a problem let me know and I will try to upload it somewhere else.

Is this roughly what you had in mind?

1762800087415.png


1762800115246.png


MrGhost said:
I have generally ok luck with the Advanced Scene Switcher, it really does a great job of following my train of thought around my process based on scene change using percent change of selected picture regions. Switches to 10 + 5 different scenes on 2 computers with OBS connecting and compiling across the 2 computers over the NDI network OBS plugin.

Are there any ideas with such a setup as to whether there is a good way to keep minimal duration switches (flashing scenes quickly switching to another scene and one scene on one computer switching a small amount of time after a scene on the other computer switches) off the final video? I can't follow any normal algorithm for success because as both computers are running the switcher, there would need to be some cross talk for it to agree when to change the scene smoothly from both computers. I am frankly not even sure if it is working with all good intervals on either computer by themselves. I see quite a few short snippets of scenes or quick jumps.

It doesn't bother me but I suppose it looks glitch + wrong to outsiders? Anyone ever successfully got the scene switching to sync up? Is there any network syncing mechanism that I don't know about for 2 computer Adv.S.S. setup? Something that could grab a tempo and just use it. A nice slow tempo.
Click to expand...
Would you mind sharing a minimal example macro setup to replicate issue?
I think I roughly get what the problem is, but I am not sure I fully understand what is triggering the problem on your side and the example might help with that.

Without knowing much about the setup:
Wouldn't it help to simply add a "Wait X seconds" action after each scene switch to ensure scenes are not switched too quickly?
1762800562214.png

Alternatively the conditions section of the relevant macros could be adapted to limit how frequently the actions are triggered.
1762800623630.png
 
Hello!

I'm trying to use the Date function to start a recording, but it doesn't seem to work as expected.
1762800949348.png

Whenever this macro runs the recording starts immediately regardless of the date and time I set. Is there something obvious I'm missing here? I've also tried setting it from Any day at to Any day after or before, but it still starts as soon as I press run macro.
 
spacewizard said:
Hello!

I'm trying to use the Date function to start a recording, but it doesn't seem to work as expected.
View attachment 116536
Whenever this macro runs the recording starts immediately regardless of the date and time I set. Is there something obvious I'm missing here? I've also tried setting it from Any day at to Any day after or before, but it still starts as soon as I press run macro.
Click to expand...
Hello!
Can you please enable verbose logging, then reproduce the problem, and share the corresponding log file?
github.com

Troubleshooting

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com github.com
 
Warmuptill said:
Thanks for sharing the log!

Just for my understanding:
How did you reproduce the issue?
Did you press the "Run macro" button at the top?
Click to expand...
Yes, I pressed Run macro at the top. And it seems it gets a little weirder. It runs as soon as Run macro is pressed, then it runs again once the time I've set is detected.

I've attached logs of this happening. Hopefully that helps.
 

Attachments

spacewizard said:
Yes, I pressed Run macro at the top. And it seems it gets a little weirder. It runs as soon as Run macro is pressed, then it runs again once the time I've set is detected.

I've attached logs of this happening. Hopefully that helps.
Click to expand...
There seems to be a slight misunderstanding what the "Run macro" button does:

The "Run macro" button will run the actions of the macro regardless of what the current condition state is.
You will not have to press it to "activate" a macro.
A macro is active, if the checkbox next to the name of the macro is checked.

1762883469700.png


So, it sounds like the macro is behaving as it should and starting the recording at the given time.
Let me know if that cleared things up! :)
 
Warmuptill said:
There seems to be a slight misunderstanding what the "Run macro" button does:

The "Run macro" button will run the actions of the macro regardless of what the current condition state is.
You will not have to press it to "activate" a macro.
A macro is active, if the checkbox next to the name of the macro is checked.

View attachment 116560

So, it sounds like the macro is behaving as it should and starting the recording at the given time.
Let me know if that cleared things up! :)
Click to expand...
Ah, that makes much more sense! Thank you very much.
 
@Warmuptill Yes, that filter is great, especially on the value as well as the column/variable name. And the Dock is great! So much easier to debug as well as see state of things. BIG Thank you!

FWIW, the only tiniest thing I could note is that if there was a "Clear" the filter button on the left or right side of the "search ..." text input box, that would be icing on the cake.
 
Last edited:
Warmuptill said:
Would you mind sharing a minimal example macro setup to replicate issue?
I think I roughly get what the problem is, but I am not sure I fully understand what is triggering the problem on your side and the example might help with that.

Without knowing much about the setup:
Wouldn't it help to simply add a "Wait X seconds" action after each scene switch to ensure scenes are not switched too quickly?
View attachment 116534
Alternatively the conditions section of the relevant macros could be adapted to limit how frequently the actions are triggered.
View attachment 116535
Click to expand...


The problem is no matter how many seconds you tell #4 computer to wait, the #3 computer is likely to switch at a completely different time unless both were governed by some network sync or tempo sync driven externally such as MIDI carried DAW tempo sync out of Studio One.
 
Last edited:
You must log in or register to reply here.
Back
Top