I can see the desire to make it "pretty", as in "pleasant to look at" or "easy to use in complete isolation". But when there's a connection to something else, and that something else is the controlling one and yours is just a reflection of it, then I think it's better to just copy it verbatim and leave it at that. Even if it's ugly. That would make @lindenkron 's screenshot the standard to match.
- Thread starter Warmuptill
- Start date
I can see the desire to make it "pretty", as in "pleasant to look at" or "easy to use in complete isolation". But when there's a connection to something else, and that something else is the controlling one and yours is just a reflection of it, then I think it's better to just copy it verbatim and leave it at that. Even if it's ugly. That would make @lindenkron 's screenshot the standard to match.
Warmuptill
Active Member
Thanks for the suggestion!
First of all I apologize if my previous statement came across as rude / dismissive of the way it was handled by stream deck.
Unfortunately I am not sure that this approach would be the best way to go for this plugin however.
Using the current approach makes it easier to add the "any" / "all" selection and is (probably?) easier to use if there are a lot of scene items on a particular scene.
But that is just my opinion and it probably comes to down to personal preference.
(And I don't want to invest too much time in such a minor area of the plugin :D)
You can still add things outside of the "verbatim block" - All, Any, etc. - to create your block, but the set that you copy from remains unchanged.
Don't know if the data structure lends itself to this or not, but some pseudocode might look like this:
and not much else.
lindenkron
Member
@Warmuptill
It appears to be working as intended! Thanks.
Regarding the back and forth above; I agree with AaronD on things from a UX perspective. It's easier when both lists show the same thing - to simply scroll to where the source is in your OBS - it makes working between OBS and Streamdeck for selecting sources very intuitive and easy.
Things listed in alphabetical order might seem from a logical standpoint as the go-to move, but it makes it harder (at least personally) to find things when you know it's at the bottom of your scene, but you forgot what you named it.
A comparison:
But I'm not out here trying to make your life harder than it need be. I appreciate a quick and functional solution! It's definitely going to get it's fair uses with the amount of repurposed sources I use :)
It all seems to work, I've had no issues with it. So if you wish to merge it to masters; I see no reason why not.
Thanks again, and happy new year!
It appears to be working as intended! Thanks.
Regarding the back and forth above; I agree with AaronD on things from a UX perspective. It's easier when both lists show the same thing - to simply scroll to where the source is in your OBS - it makes working between OBS and Streamdeck for selecting sources very intuitive and easy.
Things listed in alphabetical order might seem from a logical standpoint as the go-to move, but it makes it harder (at least personally) to find things when you know it's at the bottom of your scene, but you forgot what you named it.
A comparison:
But I'm not out here trying to make your life harder than it need be. I appreciate a quick and functional solution! It's definitely going to get it's fair uses with the amount of repurposed sources I use :)
It all seems to work, I've had no issues with it. So if you wish to merge it to masters; I see no reason why not.
Thanks again, and happy new year!
VesNL
New Member
I'm having an issue with the settings. Despite having set to not start when opening OBS it keeps activating.
Cleared my plugins folder, reinstalled OBS and cleared everything and it still happens. Tried it with default settings and the only plugin installed but it remained.
On OBS 27.1.3 and plug version 1.16.5 on Windows 10.
Cleared my plugins folder, reinstalled OBS and cleared everything and it still happens. Tried it with default settings and the only plugin installed but it remained.
On OBS 27.1.3 and plug version 1.16.5 on Windows 10.
Warmuptill
Active Member
Sorry about that - that is a bug that was introduced with 1.16.5.
You can find a build with a fix here:
Remove unnecessary uses of UNUSED_PARAMETER macro · WarmUpTill/SceneSwitcher@ce57304
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
(I plan on making a new release soon which contains a few other fixes and changes as well)
Last edited:
Hey yall! I'm having an issue and I'd love some help as I can't find a tutorial for this.
I'm trying to get all of my scenes in OBS to have different audio inputs enabled. I think I put the conditions in correctly, but when I switch scenes in OBS, I still have to fix my audio as things that should be muted are active and things that should be active are muted. I'm not sure if I'm using the wrong tab in the scene switcher or if I'm potentally just doing this all wrong. Any help yall could provide would be greatly appreciated!
I'm trying to get all of my scenes in OBS to have different audio inputs enabled. I think I put the conditions in correctly, but when I switch scenes in OBS, I still have to fix my audio as things that should be muted are active and things that should be active are muted. I'm not sure if I'm using the wrong tab in the scene switcher or if I'm potentally just doing this all wrong. Any help yall could provide would be greatly appreciated!
Warmuptill
Active Member
What exactly have you configured?
If you don't mind you can export your current settings to a file on the General tab and attach it here.
VesNL
New Member
Sorry about that - that is a bug that was introduced with 1.16.5.
You can find a build with a fix here:
You need to be logged into GitHub to be able to download it - let me know if that is an issue for you!
Remove unnecessary uses of UNUSED_PARAMETER macro · WarmUpTill/SceneSwitcher@ce57304
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
(I plan on making a new release soon which contains a few other fixes and changes as well)
Thanks, I thought I was going crazy.
lindenkron
Member
The only thing crazy here is the speed at which Warmuptill supplies fixes, improvements & updates.
That's comforting. Whenever you make one of these builds - I always worry that previous fixes from other builds might not be included >.< (Not sure how it works).
lindenkron
Member
Does anyone have any suggestions for how to improve this?
Trigger only if coming from 'Intro' going to 'Casters'. I just spent 10 mins going back in old projects trying to figure out what this was meant to do because how it looks is so utterly confusing. I was expecting the first condition having to be 'Previous scene'.
I'm sorry to be a nagging nanny but I feel like there has to be a better way to convey "If scene you're coming from = Intro" instead of saying "current scene is" on both of them, which completely threw me for a loop.
I can't immediately figure out what an ideal fix would be. I'm not even exactly sure what 'Previous scene' currently does, only that Warm helped me figure this out last time :D
Trigger only if coming from 'Intro' going to 'Casters'. I just spent 10 mins going back in old projects trying to figure out what this was meant to do because how it looks is so utterly confusing. I was expecting the first condition having to be 'Previous scene'.
I'm sorry to be a nagging nanny but I feel like there has to be a better way to convey "If scene you're coming from = Intro" instead of saying "current scene is" on both of them, which completely threw me for a loop.
I can't immediately figure out what an ideal fix would be. I'm not even exactly sure what 'Previous scene' currently does, only that Warm helped me figure this out last time :D
Warmuptill
Active Member
I would do something like this:
You can also make it work with the current / previous scene check if you prefer that:
But note that the latter solution will continuously be true while the caster scene is active while the former will only be true during the transition.
If you want the conditions to just be true in the exact moment the transition from Intro to Caster completes you can use something like this.
So the best approach depends on what exactly you need.
Assuming you switch scenes from A -> B.
Then A is the "previous scene" and B the "current scene".
If you should then switch to scene C, B will take over the "previous scene" spot and C will be the "current scene".
Last edited:
lindenkron
Member
I was going to add https://obsproject.com/forum/threads/advanced-scene-switcher.48264/post-550057 as a reference since I've had the issues with not being able to get 'Previous Scene' to work how I wanted it to.
Wondering if your second example would work if adding a time restraint to the 'current scene is' of 0.20 (assuming 200ms check) so that it can only trigger once.
Might give it a try in the morning. I didn't see the "Transition > Transitioning From > Scene" till now, might also be handy! I wasn't expecting the 'transition' category to have 'scene' elements - so that might end up being the solution.
Thanks again!
Warmuptill
Active Member
Warmuptill updated Advanced Scene Switcher with a new update entry:
Dock, OpenVR, and more
Read the rest of this update entry...
Dock, OpenVR, and more
Additions:
- Added the option create a dock widget to check and control whether or not the Advanced Scene Switcher is currently running.
You can access it via View -> Docks -> Advanced Scene Switcher.
It can be used just like...
Read the rest of this update entry...
lindenkron
Member
@Warmuptill Just installed 1.17, tried changing one of my If statements from "Scene" to "Transition" and my audio went nuts and OBS shut itself down haha.
Not exactly sure what happened; no crash reports (just killed the app) and nothing in the logs.
I went back to the last build you made me; and that works without crash.
Not exactly sure what happened; no crash reports (just killed the app) and nothing in the logs.
I went back to the last build you made me; and that works without crash.
Warmuptill
Active Member
Hm, that seems very strange - I am not sure how changing a transition type would affect audio.
Is the issue reproducible?
If so can you share the settings that are causing the problem?
lindenkron
Member
The audio was probably because there was music playing and CPU hit 100% (then audio distorts). I'm guessing something infinite looped or something, it seemed really strange at least.
I re-installed 1.17, but I changed the thing that crashed it since (with your old version) and I don't seem to be able to get it to do it again. It does have me a little worried now though lol.
I'll try and continue using 1.17 and let you know if it does it again.
lindenkron
Member
@Warmuptill Found what I suspect to be a glitch:
Edit:
Shows check field:
"waitForTransition": false
Hides check field:
"waitForTransition": true
Edit:
Shows check field:
"waitForTransition": false
Hides check field:
"waitForTransition": true
Last edited:
Warmuptill
Active Member
Thanks for pointing that out, but that is actually intended behavior!@Warmuptill Found what I suspect to be a glitch:
Edit:
Shows check field:
"waitForTransition": false
Hides check field:
"waitForTransition": true
The option to set "waitForTransition" was removed already in the last version as it did not really fit into this condition type. (Unticking this checkbox is basically equivalent to a "Transitioning to ..." check)
Existing conditions were not affected for compatibility reasons, but if you choose to set the "waitForTransition" field the option will be hidden.
Add the option to check for the source and the target scene of an ongoing transition.
At the same time the option "wait for transition to complete" was removed from the "current scene is" check as it did not really fit into that category and its description was not really formulated clearly to begin with.
Note that the behaviour has not change for any already existing macros.
But thanks again for having a look out for potential issues! :)
lindenkron
Member
Okay, little confusing. Sorry for bringing it up, it just came across as a feature unintentionally disappearing.
So am I to understand it correctly that from now on you should never use 'scene' for anything that's supposed to happen once when going to a scene? That from now on If Transition Transitioning to SCENE should be used?
Personally feels a little unintuive to me from how I've used adv-ss previously, but hopefully it'll feel more natural in the future.
What's your intentional usage of the "If scene" functionality now then?