oh, okay, that clears up things now, thank you!Yes, the scene switcher would check the timing after the condition became true.
It can only be ever as accurate as the interval.
oh, okay, that clears up things now, thank you!Yes, the scene switcher would check the timing after the condition became true.
It can only be ever as accurate as the interval.
not sure about the dock panel, but you can set a hotkey to start/stop the plugin in OBS Settings > Hotkeys.How hard would it be to create a dock panel to at least allow simple start / stop of the plugin without having to open it up?
Thanks for pointing that out.View attachment 78222
seems like adv-ss spams this kind of log message with my infinite loop running in parallel
this is my macro
View attachment 78223
View attachment 78224
tested it without running it in parallel, and it doesn't spam the log.
Thanks, looks good to me.Thanks for pointing that out.
A build where this spam is disabled can be found here in a few minutes:
![]()
Fix crash when reordering macros · WarmUpTill/SceneSwitcher@3be4b3f
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.github.com
Good idea - i will look into it!Here's another suggestion I keep forgetting to say here. How about you add a checkbox on "Switch scene" macro actions to "wait until transition is finished"? Currently, we would have to add a wait action after for the timing of the next action, but if we end up changing the transition duration, we would have to adjust the values again. Also, such checkbox could also lead to less macro actions.
Hm, strange - let me know if you find any way to reproduce it.Oh, dear, I got another case of the "wrong macro action index". I'm clicking the add button on one of my macro actions, but the copy goes to a different position instead of right next to it. I can't give reproduction steps atm as it would take a while to test around haha. Got it on 1.16.5.
uhhh, so basically "for exactly X seconds" will almost never be true?Yes, the scene switcher would check the timing after the condition became true.
It can only be ever as accurate as the interval.
Well it will only ever be as accurate as the interval configured on the general tab.uhhh, so basically "for exactly X seconds" will almost never be true?
I now implemented a first version of this functionality.Here's another suggestion I keep forgetting to say here. How about you add a checkbox on "Switch scene" macro actions to "wait until transition is finished"? Currently, we would have to add a wait action after for the timing of the next action, but if we end up changing the transition duration, we would have to adjust the values again. Also, such checkbox could also lead to less macro actions.
Well it will only ever be as accurate as the interval configured on the general tab.
The main difference between "for exactly ..." and "for at least" / "for at most" is that it will only match at the moment the time was reached and not after / before it.
I chose to use the wording "for exactly" to differentiate it from the "at least" / "at most" cases but it might not be the most clear.
If you have a suggestion for a better name I am all ears :)
Thanks!
I think I found the problem.
A build with a fix should be available here in a few minutes:
It would be great if you could quickly confirm whether or not the problem is resolved on your end as well.![]()
Fix crash when reordering macros · WarmUpTill/SceneSwitcher@d18d596
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.github.com
I also added the option to check whether or not studio mode is currently active to this build.
View attachment 78121
Just to clarify - are you referring the media condition type in the Macro tab or the separate tab labeled "Media"?
In case of the latter this would actually be "expected behaviour" as the the way the priority system works is that checks are only performed until one functionality fulfils its conditions and a match is found.
So if the macro tab functionality is running in a continuous loop and thus a match is always found the other functionality like the media tab will not get a chance to run.
The easiest way to solve this would be to just transition your entries from the Media tab to the Macro tab so you can rely on the "run in parallel option".
But you are not the only user who stumbled upon this issue, so maybe I should adjust things.
The reason it was implemented in this way is that if a user configured automated scene switches via the macro tab and also the "old" tabs two scene switches could clash with one another and result rapidly flickering scene changes.
But maybe I can find a way to work around this.
Hey @Warmuptill
Is there anything you can do about duplication sources not showing up in the dropdown menu for stuff such as Scene Item Visibility? I've had this issues other places as well. Not sure if it's possible in the environment you're working in, but I know Stream Deck managed to implement the capabilities of selecting specific duplicated sources.
View attachment 78433
Example above. Only one is visible in the dropdown; but there's 4 sources.
Thanks!
-Lind
It is actually a very common use case to duplicate sources and keep their names the same. Sources with the same name mean that they are references to only one source. If they are separate sources, then it will take more OBS resources. This is especially true when you use window captures, and you're using the same source in a scene with different layouts. If you use two separate window captures, then OBS will likely use 2x the computing power for capturing the same window (not that I know internals, but this is a rough estimation of the difference).You can rename them, independently of what they are. Is that too much trouble? (if you're adding and removing constantly, then the answer could very well be yes)
If they do need to have the same name, then how do you tell the difference in the dropdown? Looks like they're in alphabetical order, not the user's order from the Sources list, which would destroy any confidence that I might have had in choosing the correct identical name.
Hey @WarmuptillThanks for the suggestion regarding duplicate source names.
I will look into whether or not this is feasible.
@lindenkron you mentioned that other tools faced the same issue.
How did they solve the issue of displaying the same entry multiple times on the UI side?
I can of course just add the same name X amount of times but that would probably be a bit confusing.
Hey @Warmuptill
The representation was very simple. Same identical name; but they're placed in the same order as you see it in your scene items. So 1 in the list, is 1 in the 'scene.item' list.
Now how they did it technically, I can't say. Here's the Stream Deck repo: https://github.com/elgatosf/streamdeck-obs-plugin
View attachment 78499
Here's a visual representation of it.