- Thread starter Warmuptill
- Start date
lindenkron
Member
Afraid not, OBS hotkeys still need to work, just only when in-game :)
Think that might work with the check for "is focused". Will test tomorrow. Thanks :)
lindenkron
Member
Checked the 'process focus' and it appears to work. Thanks!
Have another small issue I wonder if you know how to optimize. On a 200ms check, this code takes 2 seconds to get checked (before it kicks in) which seems a little weird.
Any ideas? :)
Have another small issue I wonder if you know how to optimize. On a 200ms check, this code takes 2 seconds to get checked (before it kicks in) which seems a little weird.
Any ideas? :)
Warmuptill
Active Member
Good to hear that the process condition is working as intended! :)
Hm, strange - can you explain in more detail what you want this condition to achieve?
I doubt that it is a CPU resource issue, but can you double check if you see the following pattern in your OBS log for the affected macro just in case?
"spent X ms in Y condition check of macro 'Z'!"(Just want to be sure I didn't mess something up in the implementation)
lindenkron
Member
I switch between two feeds, on a specific scene (Game Play) and I wasnt it to fade the audio for my game out/in depending on which source (feed) is visible.
15:56:26.695: [adv-ss] detected busy loop - refusing to sleep less than 1ms
All I see.
15:56:26.695: [adv-ss] detected busy loop - refusing to sleep less than 1ms
All I see.
lindenkron
Member
We just finished. I started having strange behaviour where sometimes it would act as if it pressed 'r' twice, or ran both macros one after another.
But I'm having issues consistently reproducing it. It unfortunately resulted in quite a few instances of it switching back to my Observer feed while it wasn't supposed to, when I didn't catch it to switch it again.
Am thinking perhaps some lag issues with 1 or 0 not being set properly and it firing both? Unknown.
Other than that, things went good with adv-ss!
But I'm having issues consistently reproducing it. It unfortunately resulted in quite a few instances of it switching back to my Observer feed while it wasn't supposed to, when I didn't catch it to switch it again.
Am thinking perhaps some lag issues with 1 or 0 not being set properly and it firing both? Unknown.
Other than that, things went good with adv-ss!
lcalder
Member
Thanks for reporting the issue - i will look into it as soon as I can.
Update: I might have identified the reason for the crash on OBS exit.
A build with a fix should be available here in a few minutes:
(You need to be logged into GitHub to be able to download it - let me know if that should be an issue)
Fix crash on exit caused by status dock · WarmUpTill/SceneSwitcher@aac9429
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.github.com
Thanks for the info regarding the dock issue!
I will try to look into it soon, but I will have to prioritize the crashes on the OBS beta for now.
Unfortunately, I can't think of a good solution to the macro toggle issue, besides using this new "Sequence" action from the build above.
View attachment 79380
I tried the updated advanced scene switcher from Github and it still crashes. I've included the log, crashfile and the advanced-scene-switcher settings files as you requested. Let me know it you need anything else, and thanks so much for your help on this wonderful plugin.Thanks for reporting the issue - i will look into it as soon as I can.
Update: I might have identified the reason for the crash on OBS exit.
A build with a fix should be available here in a few minutes:
(You need to be logged into GitHub to be able to download it - let me know if that should be an issue)Fix crash on exit caused by status dock · WarmUpTill/SceneSwitcher@aac9429
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
Thanks for the info regarding the dock issue!
I will try to look into it soon, but I will have to prioritize the crashes on the OBS beta for now.
Unfortunately, I can't think of a good solution to the macro toggle issue, besides using this new "Sequence" action from the build above.
View attachment 79380
Warmuptill
Active Member
Thank you very much for the test, but I think you might have accidentally downloaded the wrong version judging by the version string printed in the log file.
Can you give downloading it another try?
(Sorry, in case I posted the wrong / too many links)
I submitted some other unrelated fixes to the master branch in the mean time so I would suggest to use this build:
Add sequence action (#395) · WarmUpTill/SceneSwitcher@abd6fd6
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
19:29:46.166: [adv-ss] version: abd6fd6
19:29:46.166: [adv-ss] version: abd6fd6b7e1f839f1b82bca34e7d8ee69a3aa55c
Update: The newest OBS beta also has the following change, which might make a difference:
- Fixed a crash that could happen on shutdown with certain third-party plugins
Last edited:
Warmuptill
Active Member
I see, thanks for the explanation. (The "Or" is intended, right? Or was an "And" intended here?)
Setting up a similar condition on my side does not result in any delay and as you also don't see the "spent X ms in ..." messages I also assume that the duration spent in the condition check is not the issue.
That would leave two possible causes:
- An action running in your macro, which is happening before the audio fade, is taking about two second to complete.
- Other macros are running before this one and are taking up the time.
- A combination of the previous two points
To test the second theory try to move the respective macro to the top of the macro list so it is being executed first or just pause all other macros.
Hope that helps to get to the root cause of the delay.
Glad to hear that things went well :)
Regarding the macro when pressing "R".
I would instead suggest to set up the following:
Two macros - one for switching to scene A, a second one for switching to scene B:
Finally a third macro which will do the toggling:
The "Run macro in parallel to other macros" is important if you want to avoid the issue of the hotkey presses queueing up and resulting in multiple consecutive scene switches.
Hope that helps!
lindenkron
Member
Hey @Warmuptill
That sequence did wonders, so much simpler now. And it doesn't bug at the start like the other one did. Thanks!
I already tried the moving the macro up to the top. And there's nothing else in the actions than "mute", so nothing to clear out.
This is the full macro, and below it an example of timing (you can see the bottom fading and when the button mutes/unmutes).
^video of the transitioning.
^example with fade
I'd like it to be a fade mute over 1 second as to follow the fade. The mute is just a test. Issue was that it would *start* fading at the time you see the mute happening in the clip. So those 2 seconds, + 1 second fade means the fading of the video is pretty offset.
Best regards,
-Lind
That sequence did wonders, so much simpler now. And it doesn't bug at the start like the other one did. Thanks!
I already tried the moving the macro up to the top. And there's nothing else in the actions than "mute", so nothing to clear out.
This is the full macro, and below it an example of timing (you can see the bottom fading and when the button mutes/unmutes).
I'd like it to be a fade mute over 1 second as to follow the fade. The mute is just a test. Issue was that it would *start* fading at the time you see the mute happening in the clip. So those 2 seconds, + 1 second fade means the fading of the video is pretty offset.
Best regards,
-Lind
Last edited:
Warmuptill
Active Member
Ah good to hear that the sequence action is working as expected! :)Hey @Warmuptill
That sequence did wonders, so much simpler now. And it doesn't bug at the start like the other one did. Thanks!
I already tried the moving the macro up to the top. And there's nothing else in the actions than "mute", so nothing to clear out.
This is the full macro, and below it an example of timing (you can see the bottom fading and when the button mutes/unmutes).
View attachment 79488
^video of the transitioning.
^example with fade
I'd like it to be a fade mute over 1 second as to follow the fade. The mute is just a test. Issue was that it would *start* fading at the time you see the mute happening in the clip. So those 2 seconds, + 1 second fade means the fading of the video is pretty offset.
Best regards,
-Lind
Regarding the delay issue I am out of ideas to be honest.
Can you maybe set up a minimal reproduction example in a new scene collection and export the settings you are using to a file? (General tab)
Are you using some special transition type? (You mentioned fade, but asking just in case)
lindenkron
Member
It's in the detection somewhere. Adding the audio to the macro that does the switching itself works, but the detection one for audio doesn't trigger instantly.
Unfortunately I'd prefer to have all my audio for a specific feed in one place if I can so I don't have to go looking for it in 20-30 macros :3
Hey guys, just a quick question, cause I am unsure if I can do this with the ASS Plugin.
I would like to setup a 24/7 stream. What I want to do is I want to have two inputs. One is a 24/7 automated playlist (Stream 1) the other is a real live stream (Stream 2). What I want to happen is when Stream 2 goes online, I want to switch to this scene, and as soon as that stream goes offline, I want to switch back to Stream 1.
Can I do the monitoring and switching with the Advanced Scene Switcher?
Kind Regards
Zero
I would like to setup a 24/7 stream. What I want to do is I want to have two inputs. One is a 24/7 automated playlist (Stream 1) the other is a real live stream (Stream 2). What I want to happen is when Stream 2 goes online, I want to switch to this scene, and as soon as that stream goes offline, I want to switch back to Stream 1.
Can I do the monitoring and switching with the Advanced Scene Switcher?
Kind Regards
Zero
Warmuptill
Active Member
You can set up automated scene switches depending on whether or not you are currently streaming, but I am not sure if it would be useful in your case.
Are both Stream 1 and Stream 2 originating from the same OBS instance? (Is that possible?)
Or are these streams just special sources on different scenes inside OBS?
To further elaborate it....
Stream 1 would be a scene in OBS with a VLC playlist automated by a third party tool.
Stream 2 would be a media source pointing to the RTMP server.
Biggest challenges so far are to constantly ping the RTMP server to see if the stream is up and to then switch to that scene and again, to go back to the other VLC scene when the RTMP goes down....
Stream 1 would be a scene in OBS with a VLC playlist automated by a third party tool.
Stream 2 would be a media source pointing to the RTMP server.
Biggest challenges so far are to constantly ping the RTMP server to see if the stream is up and to then switch to that scene and again, to go back to the other VLC scene when the RTMP goes down....
Warmuptill
Active Member
You could set up a macro to monitor if the "Stream 2" source has changed it's video output recently and if so switch scenes accordingly.
Maybe this example could help:
Creating a macro
An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
I could imagine there are probably better tools for this job, but I am not familiar with this topic to know them.
Hope this helped anyway! :)
So basically, the plugin is then checking the connection state every xx seconds/milliseconds and keeps remediating that automatically to check if the condition is true or false? That would help big Time!!!
Hi, I am a newbee on OBS and have tried to use this plugin on two instances of OBS on Windows10.
But unfortunately only the plugin works on the OBS instance which is first launched after installing the plugin. On the other instance of OBS I can setup the plugin, start it but no task is performed
How can I get the plugin working on each instance of OBS ?
But unfortunately only the plugin works on the OBS instance which is first launched after installing the plugin. On the other instance of OBS I can setup the plugin, start it but no task is performed
How can I get the plugin working on each instance of OBS ?
Warmuptill
Active Member
Hm strange.
In theory there should be nothing preventing the plugin from being run multiple times each across separate OBS instances.
Can you provide an OBS log file of the second instance, which is not performing its tasks?
Please make sure to enable verobse logging. (The option can be found on the General tab)