Advanced Scene Switcher

Advanced Scene Switcher 1.28.1

Warmuptill

Active Member
Hello Warumtill!

Did intensive tests today and it works fine! Thanks for the quick implementation! However double click automatically also switches the scene on my "Live Production" laptop so I have to be really careful :-)

Regarding the client / server role selection: It was initially not meant per scene - just in general for all scenes - so your checkbox solution is perfectly well but it should work and be named "Synchronize ONLY preview scene when running in Studio mode"

Hope this is just a few lines of code in your business logic, or is it more complicated?

Kind regards
Andreas
I now added the option to not send scene change messages.
NetworkNoSceneChange.PNG

A build will be available here in a few minutes:
 

ASchneider

Member
Sorry about this and thank you for the tests and investigation!
I had only tested without these scene groups. (I didn't even know this feature existed to be honest)

I have fixed this behaviour and also allowed groups to be selected as the target of the scene visibility action.
You can find a build here in a few minutes:

Thank you very much! I've tested and it works perfectly, amazing. Have a great day!
 

Warmuptill

Active Member
Hello @Warmuptill, I think I've another bug: every time I restart OBS, pause settings are restored to "--select macro--".

View attachment 71492
Thanks.
Thanks! :)
That is fixed already.
(Macros were not yet all loaded while the references to other macros were set)

A build with a fix and also the count feature I mentioned is available here:

Note that I also reworked the pause action slightly and combined it with the counter reset action.
(The action entry is now named "Macro" - old pause actions will not be loaded)
 

ASchneider

Member
Thanks! :)
That is fixed already.
(Macros were not yet all loaded while the references to other macros were set)

A build with a fix and also the count feature I mentioned is available here:

Note that I also reworked the pause action slightly and combined it with the counter reset action.
(The action entry is now named "Macro" - old pause actions will not be loaded)
Hello!

Amazing, I really liked how you have implemented the count feature, really nice. I see that it resets itself after OBS restarts, wouldn't it be nice to reset itself after Advanced Scene Switcher restarts too (stop and starts again)?

Also, it seems that the problem with selection groups has returned :)

1621887344058.png


Maybe you missed the built that you had it fixed before...

Thanks a lot!
 

Warmuptill

Active Member
Hello!

Amazing, I really liked how you have implemented the count feature, really nice. I see that it resets itself after OBS restarts, wouldn't it be nice to reset itself after Advanced Scene Switcher restarts too (stop and starts again)?

Also, it seems that the problem with selection groups has returned :)

View attachment 71499

Maybe you missed the built that you had it fixed before...

Thanks a lot!
>wouldn't it be nice to reset itself after Advanced Scene Switcher restarts too (stop and starts again)?
Good idea! I will add it to the todo list.

>Also, it seems that the problem with selection groups has returned
I am using different branches for development of the different features and fixes.
This particular branch was created when the source selection changes were not yet merged to the master branch.
So this is expected - I should have mentioned that, but I simply had not thought of it.
But thanks for noticing and pointing it out! :)

I started a build containing the count feature based on the latest state of the master branch in case you need it:
 

ASchneider

Member
>wouldn't it be nice to reset itself after Advanced Scene Switcher restarts too (stop and starts again)?
Good idea! I will add it to the todo list.

>Also, it seems that the problem with selection groups has returned
I am using different branches for development of the different features and fixes.
This particular branch was created when the source selection changes were not yet merged to the master branch.
So this is expected - I should have mentioned that, but I simply had not thought of it.
But thanks for noticing and pointing it out! :)

I started a build containing the count feature based on the latest state of the master branch in case you need it:
Thank you! I'll give it a try as soon as it is ready. I was wondering: would it be possible to have an action to stop the plugin entirely? I have a macro that is used on the last scene, when I finish my stream, to stop streaming/recording after 2 minutes of showing the last scene and it would be nice to stop Advanced Scene Switcher after that, so I could go trough the scenes that has triggers and change something if needed without having the plugin doing anything.
 

ASchneider

Member
Ok, so the latest beta is great, both groups and macros are now functioning as it should :)

I was thinking about the source and scene visibility actions: not sure how disabling a source would help, since you cannot control it using OBS UI, comparing to the current scene visibility. Don't you think it might confuse people and cause more problems than help?

Also, not sure if scene visibility is the best name, since it only changes sources. Maybe just calling "source visibility" would be more clear to understand :)

Another small suggestion: as you can see on my latest screen grab, would it be possible to sort the sources the same way it is shown on the source list? That would help to find what source you need to set if you have many items and you had them organized it before.

1621892631565.png


Now it shows the list in reverse, as you can see in the image.

Thanks!
 
Thanj
I now added the option to not send scene change messages.
View attachment 71483
A build will be available here in a few minutes:
Thanks Warmuptill! This eases my graphics handling and monitoring tremendously. Looking forward to your next functional enhancements! Andreas
 

Warmuptill

Active Member
Ok, so the latest beta is great, both groups and macros are now functioning as it should :)

I was thinking about the source and scene visibility actions: not sure how disabling a source would help, since you cannot control it using OBS UI, comparing to the current scene visibility. Don't you think it might confuse people and cause more problems than help?

Also, not sure if scene visibility is the best name, since it only changes sources. Maybe just calling "source visibility" would be more clear to understand :)

Another small suggestion: as you can see on my latest screen grab, would it be possible to sort the sources the same way it is shown on the source list? That would help to find what source you need to set if you have many items and you had them organized it before.

View attachment 71501

Now it shows the list in reverse, as you can see in the image.

Thanks!

>I was thinking about the source and scene visibility actions: not sure how disabling a source would help, since you cannot control it using OBS UI, comparing to the current scene visibility. Don't you think it might confuse people and cause more problems than help?

I thought it might be useful if one would want to disable a source on every single scene, but I do agree that it might confuse people.
For now I added a warning clearly stating that disabling a source globally cannot be controlled via the regular OBS UI.

>Also, not sure if scene visibility is the best name, since it only changes sources. Maybe just calling "source visibility" would be more clear to understand :)

What about "scene item visibility"? (The name used in the API)

>Another small suggestion: as you can see on my latest screen grab, would it be possible to sort the sources the same way it is shown on the source list? That would help to find what source you need to set if you have many items and you had them organized it before.

Good point. This is stems from the way I am enumerating through the different sources.
I resorted to just sorting it alphabetically as even the using the order of sources might become confusing with a lot of sources.


I now implemented the source activity, visibility and settings conditions as well as the macro action to stop the plugin.
(Sorry that it took me so long to get around to it)

SourceConditionStopAction.png


A build will be available here in a few minutes:

Let me know if it works as expected and what you think, if you should get the chance to give it a try! :)
 

ASchneider

Member
>I was thinking about the source and scene visibility actions: not sure how disabling a source would help, since you cannot control it using OBS UI, comparing to the current scene visibility. Don't you think it might confuse people and cause more problems than help?

I thought it might be useful if one would want to disable a source on every single scene, but I do agree that it might confuse people.
For now I added a warning clearly stating that disabling a source globally cannot be controlled via the regular OBS UI.

>Also, not sure if scene visibility is the best name, since it only changes sources. Maybe just calling "source visibility" would be more clear to understand :)

What about "scene item visibility"? (The name used in the API)

>Another small suggestion: as you can see on my latest screen grab, would it be possible to sort the sources the same way it is shown on the source list? That would help to find what source you need to set if you have many items and you had them organized it before.

Good point. This is stems from the way I am enumerating through the different sources.
I resorted to just sorting it alphabetically as even the using the order of sources might become confusing with a lot of sources.


I now implemented the source activity, visibility and settings conditions as well as the macro action to stop the plugin.
(Sorry that it took me so long to get around to it)

View attachment 71572

A build will be available here in a few minutes:

Let me know if it works as expected and what you think, if you should get the chance to give it a try! :)
Hello again! Amazing stuff, thank you very much

>What about "scene item visibility"? (The name used in the API)

Great! I really like it :)

I'll take a look at the new source trigger, everything else looks excellent.

I was wondering: I've tried on of your latest built test from a couple of days ago and it seems that macro actions (pause/unpause) were again not saving... Have you merged all of those fixes that we had talked before in your latest beta built? https://github.com/WarmUpTill/SceneSwitcher/actions/runs/883337651

Thank you!
 

ASchneider

Member
Wow, now this is just amazing hahah

1622155770204.png

It would be great to have the source action to be able to write its JSON paramentes, just like the trigger could read it, I could change text, fonts or anything else in any source. If that's possible, now source actions makes sense for me haha

I can see that some drop-down lists are now showing in alphabetical order, it helped a lot to find the source I needed, but some other lists are not, just to let you know.

I think this build is now saving macro actions settings :)

Great job! The next final version will be a great upgrade from the last one, so many new features. My final suggestion would be to have trigger/action sorting/deleting and that's a wrap haha

Thank you!
 

ASchneider

Member
Ok... I was trying to create a macro that changes my webcam position based on the mouse cursor position (half screen left/right) and was not possible because the move filter was in the scene item haha

1622159108003.png


It would be great to see scene filters here.

Thanks.
 

rusty1

Member
I am using the Advanced Scene Switcher to do two main tasks...

1) I created a random switcher on a timer. Every twelve seconds it cuts to a different scene within the same scene group. This is like an auto-pilot editing mode. I assigned hotkeys for turning on and off the Advanced Scene Switcher, so that I can have manual control over scene switching when I want it.

2) I'm also using the Advanced Scene Switcher for its ability to switch back to the previous scene when media ends. So, I trigger a scene change that plays a video, and when that video finishes it automatically returns to the previous scene.

But there is one thing I can't figure out. I want to be able to turn on and off the random switcher, but I want to keep the media-state triggers always active. Right now, it's all or nothing. If I turn off the Advanced Scene Switcher to disable the random switcher, then I lose my media-triggers too.

Is there a boolean variable I can use as a conditional to toggle on and off some features, while keeping other features on at all times?
 

rusty1

Member
I am using the Advanced Scene Switcher to do two main tasks...

1) I created a random switcher on a timer. Every twelve seconds it cuts to a different scene within the same scene group. This is like an auto-pilot editing mode. I assigned hotkeys for turning on and off the Advanced Scene Switcher, so that I can have manual control over scene switching when I want it.

2) I'm also using the Advanced Scene Switcher for its ability to switch back to the previous scene when media ends. So, I trigger a scene change that plays a video, and when that video finishes it automatically returns to the previous scene.

But there is one thing I can't figure out. I want to be able to turn on and off the random switcher, but I want to keep the media-state triggers always active. Right now, it's all or nothing. If I turn off the Advanced Scene Switcher to disable the random switcher, then I lose my media-triggers too.

Is there a boolean variable I can use as a conditional to toggle on and off some features, while keeping other features on at all times?

I know I can turn the Advanced Scene Switcher on and off with scene triggers, but this feature would not know whether or not to turn it back off at the end of the scene. It wouldn't know if I had it on or off before. And it would mess up my two-state stream deck toggle button.
 

Warmuptill

Active Member
Hello again! Amazing stuff, thank you very much

>What about "scene item visibility"? (The name used in the API)

Great! I really like it :)

I'll take a look at the new source trigger, everything else looks excellent.

I was wondering: I've tried on of your latest built test from a couple of days ago and it seems that macro actions (pause/unpause) were again not saving... Have you merged all of those fixes that we had talked before in your latest beta built? https://github.com/WarmUpTill/SceneSwitcher/actions/runs/883337651

Thank you!
>I've tried on of your latest built test from a couple of days ago and it seems that macro actions (pause/unpause) were again not saving

The test build provided yesterday should have "everything", so if you do encounter issues please let me know!

>It would be great to have the source action to be able to write its JSON paramentes, just like the trigger could read it, I could change text, fonts or anything else in any source.

That is on the todo list already :)
I might get around to that later today.

>I can see that some drop-down lists are now showing in alphabetical order, it helped a lot to find the source I needed, but some other lists are not, just to let you know.

You are right - it probably makes sense to apply this to all selections.

>It would be great to see scene filters here.

Makes sense - didn't even occur to me that this is possible. :D
I will look into it!
I am using the Advanced Scene Switcher to do two main tasks...

1) I created a random switcher on a timer. Every twelve seconds it cuts to a different scene within the same scene group. This is like an auto-pilot editing mode. I assigned hotkeys for turning on and off the Advanced Scene Switcher, so that I can have manual control over scene switching when I want it.

2) I'm also using the Advanced Scene Switcher for its ability to switch back to the previous scene when media ends. So, I trigger a scene change that plays a video, and when that video finishes it automatically returns to the previous scene.

But there is one thing I can't figure out. I want to be able to turn on and off the random switcher, but I want to keep the media-state triggers always active. Right now, it's all or nothing. If I turn off the Advanced Scene Switcher to disable the random switcher, then I lose my media-triggers too.

Is there a boolean variable I can use as a conditional to toggle on and off some features, while keeping other features on at all times?
I am not sure if there is a good way to achieve what you are looking for. (Controlling individual switching methods via Hotkeys)
You could maybe achieve something similar, if you instead of stopping the plugin completely via a hotkey instead switch to a scene contniously triggering a scene change to itself.

But that is a good suggestion I might introduce for the macro tab.
Registering a hotkey to pause each macro.
 

rusty1

Member
Thank you, I'll give the continuous triggering a scene change to itself a try. Hot keys for pausing each macro would be very cool. It's almost like I wish I could run two separate instances of the Advanced Scene Switcher, each with its own on-off control.
 

ASchneider

Member
>I've tried on of your latest built test from a couple of days ago and it seems that macro actions (pause/unpause) were again not saving

The test build provided yesterday should have "everything", so if you do encounter issues please let me know!

>It would be great to have the source action to be able to write its JSON paramentes, just like the trigger could read it, I could change text, fonts or anything else in any source.

That is on the todo list already :)
I might get around to that later today.

>I can see that some drop-down lists are now showing in alphabetical order, it helped a lot to find the source I needed, but some other lists are not, just to let you know.

You are right - it probably makes sense to apply this to all selections.

>It would be great to see scene filters here.

Makes sense - didn't even occur to me that this is possible. :D
I will look into it!

I am not sure if there is a good way to achieve what you are looking for. (Controlling individual switching methods via Hotkeys)
You could maybe achieve something similar, if you instead of stopping the plugin completely via a hotkey instead switch to a scene contniously triggering a scene change to itself.

But that is a good suggestion I might introduce for the macro tab.
Registering a hotkey to pause each macro.
Thanks again!

I was thinking of how to show and edit source attributes (JSON). What do you think of something like this?

1622226090976.png


Not sure if all fields are visible for all sorts of sources but maybe it could start as blank, when you click on "Get current settings" this GUI/boxes could show up with the current fields and its attributes. If nothing is set, just the field on the left and then a blank darker box on the right, so you could set what ever you need. Maybe another checkbox to "show empty" would show empty fields, to avoid clutter.

I'm thinking of a "regular" user trying to understand JSON code for the first time and not knowing what to do or messing something up with the code.

Anyways, just a simpler way to show a JSON code as an easy graphic interface :)

This could be used on both trigger and action, maybe.

Thanks!
 
Last edited:

Warmuptill

Active Member
Thanks again!

I was thinking of how to show and edit source attributes (JSON). What do you think of something like this?

View attachment 71605

Not sure if all fields are visible for all sorts of sources but maybe it could start as blank, when you click on "Get current settings" this GUI/boxes could show up with the current fields and its attributes. If nothing is set, just the field on the left and then a blank darker box on the right, so you could set what ever you need. Maybe another checkbox to "show empty" would show empty fields, to avoid clutter.

I'm thinking of a "regular" user trying to understand JSON code for the first time and not knowing what to do or messing something up with the code.

Anyways, just a simpler way to show a JSON code as an easy graphic interface :)

This could be used on both trigger and action, maybe.

Thanks!
Good suggestion, but might be a lot of work.
I will look into it. (Maybe I can reuse the OBS properties selection somehow)

For now I would just leave it as a textbox.

A build with your previous suggestions will be available here in a few minutes:
  • Added settings modification option to macro action "source"
  • Sort (most) selection fields alphabetically
  • Add scenes to "filter" action
  • Some bug fixes
 

ASchneider

Member
Good suggestion, but might be a lot of work.
I will look into it. (Maybe I can reuse the OBS properties selection somehow)

For now I would just leave it as a textbox.

A build with your previous suggestions will be available here in a few minutes:
  • Added settings modification option to macro action "source"
  • Sort (most) selection fields alphabetically
  • Add scenes to "filter" action
  • Some bug fixes
Hello!

I'm giving the latest beta a spin.

Not sure if that many "select filter" should be there :)

1622230417482.png


It seems that it is not saving its correct settings there as well.

Also, not sure if this trigger (Screen region) could had a "for x seconds"

1622231098607.png


Thanks!
 
Top