GridMonkey
Member
Hey, i will give that a test shot soon, the options look good however. I appreciate it, will let you know once i've tried it out.
- Thread starter Warmuptill
- Start date
GridMonkey
Member
So, i gave it a very short rundown in the way i thought i would want it to work, and it did a great job with the recording control. I didnt stream for the test but i suspect that wouldnt matter in this case.
^ just a few scene versions ( i will test it deeper with the scene group tab as well )
After i checked the recording i went back to the tab to change some numbers and the left hand boxes ( scene names ) were all
[--select scene-- ]
I renamed them closed and reopened the options a few times and it seems to have stuck, unsure if real issue or not.
I also wonder if it would be possible to add a switch on the general behavior tab that makes Advanced Scene Switcher active while streaming? For my use case it would be so that if the streamer is modifying scenes they are not accidentally recording things :) The person i do all the backend stuff for doesn't really understand how much of the software works, just that it does, and often wants to look at the scenes if i have altered assets( i usually just remote change the file but it keeps the same name .)
Either way, this was made much faster than i thought it would be, so again thanks for your work.
Grid
^ just a few scene versions ( i will test it deeper with the scene group tab as well )
After i checked the recording i went back to the tab to change some numbers and the left hand boxes ( scene names ) were all
[--select scene-- ]
I renamed them closed and reopened the options a few times and it seems to have stuck, unsure if real issue or not.
I also wonder if it would be possible to add a switch on the general behavior tab that makes Advanced Scene Switcher active while streaming? For my use case it would be so that if the streamer is modifying scenes they are not accidentally recording things :) The person i do all the backend stuff for doesn't really understand how much of the software works, just that it does, and often wants to look at the scenes if i have altered assets( i usually just remote change the file but it keeps the same name .)
Either way, this was made much faster than i thought it would be, so again thanks for your work.
Grid
Warmuptill
Active Member
Thanks for the feedback!
Just out of curiosity, which combination of tools are you using?
(Just want to see if I maybe could extend this functionality with some stuff I haven't thought about yet)
Thank you, too, for your feedback! :)
I will investigate what could have led to the scene selection not to be persisted.
Do you happen to know if it was just an UI issue and the underlying triggers were still functional or if the settings were really lost?
(I doubt that you tested for that, but its worth asking)
Usually I would expect that to happen if the underlying scene was deleted, but I do not think that was the case here, was it?
Adding an option to automatically activate the scene switcher as soon as streaming starts should be doable.
I will see if I get around to adding a first draft of this today.
EDIT:
You can find a build with the option to automatically start the scene switcher on recording / streaming start here:
Add option to automatically start scene switcher on recording / streaming start · WarmUpTill/SceneSwitcher@bc17c78
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
Last edited:
GridMonkey
Member
The scenes did not get removed,
I set up the triggers you see, closed settings, stepped through them in the order i would have wanted, made about a 15 second video in total, opened the folder watched the video, yay it worked.
went right back into settings to alter a time on the triggers, names were missing, closed settings, reopened settings, names still missing, reinput the names, closed settings, did another recording using the triggers, tabbed to folder watched, tabbed back reopened settings and the names had stayed this time.
So, i didn't try to run the recording triggers with blank names, which im assuming would have told you if it was UI (name persistance?) or underling code. If it pops up again i will do that. I will be installing the latest version you did and give it an actual real stream/recording test this evening. ( probably a few "fake" tests before hand )
Thanks again.
Grid
I set up the triggers you see, closed settings, stepped through them in the order i would have wanted, made about a 15 second video in total, opened the folder watched the video, yay it worked.
went right back into settings to alter a time on the triggers, names were missing, closed settings, reopened settings, names still missing, reinput the names, closed settings, did another recording using the triggers, tabbed to folder watched, tabbed back reopened settings and the names had stayed this time.
So, i didn't try to run the recording triggers with blank names, which im assuming would have told you if it was UI (name persistance?) or underling code. If it pops up again i will do that. I will be installing the latest version you did and give it an actual real stream/recording test this evening. ( probably a few "fake" tests before hand )
Thanks again.
Grid
Warmuptill
Active Member
You might be looking for something like this:
Transition Table
Inspired by OBS Transition Matrix Donations You can donate to me via PayPal, GitHub or Patreon.
GridMonkey
Member
Thanks for the feedback!
Just out of curiosity, which combination of tools are you using?
(Just want to see if I maybe could extend this functionality with some stuff I haven't thought about yet)
Thank you, too, for your feedback! :)
I will investigate what could have led to the scene selection not to be persisted.
Do you happen to know if it was just an UI issue and the underlying triggers were still functional or if the settings were really lost?
(I doubt that you tested for that, but its worth asking)
Usually I would expect that to happen if the underlying scene was deleted, but I do not think that was the case here, was it?
Adding an option to automatically activate the scene switcher as soon as streaming starts should be doable.
I will see if I get around to adding a first draft of this today.
EDIT:
You can find a build with the option to automatically start the scene switcher on recording / streaming start here:
The setting can be found in the general tab.
Add option to automatically start scene switcher on recording / streaming start · WarmUpTill/SceneSwitcher@bc17c78
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
I tested on the actual live streaming computer before the stream tonight and had some issues then i tested on the same rig i tested your last release on. Unless noted the issues are the same on both machines
On the same rig as the previous release test, while the recording function still happens, the new option to automatically activate on stream does not seem to work. I selected
And used the same triggers from the last post, I was able to switch off the start screen and recording started instantly. paused/unpaused and ended the same. This happened while the scene switcher was inactive, as shown above.
When i reopened settings the "automatically star the scene switcher when:" was set to [Never]
Same when i set closed the settings closed obs and reopened, box still said [Never]
It feels like two problems?
1) the automatic start mode isn't responding/remembering it's setting ( on the computer that actually went live with a stream, the mode DID switch to active when OBS went live, however the 'Automatically start ... when:' box still said [never], this time it might just be the UI )
HOWEVER:
2) the scene switches cause the recording commands to function when the switcher is inactive. This was the purpose for the request of the new settings box. This in fact may be a carried over issue from your last release as i rolled back to the previous and found the same behavior. If Advanced Scene Switch is active or inactive the recording/pause/buffer/mute ( did not test streaming ) options in scene triggers still occur. Sorry i missed that in the last go around.
Please let me know what more information i can give you, i can always record all the steps i take if there are some information i'm leaving out. The laptop i've been doing the initial testing on has no other plugins installed, fresh install of 26.1.1 64bit. The real rig is also running streamFX and NDI plugin
Thanks again
Grid
Warmuptill
Active Member
Thanks for testing the build and reporting the issues!
1) I will check what could be causing that. (Probably just forgot to update the UI when loading the settings)
2) You are right. I will make sure that the scene triggers also respect the state of the plug-in.
EDIT:
A build with both of these changes will be available here in a couple of minutes:
Add option to automatically start scene switcher on recording / streaming start · WarmUpTill/SceneSwitcher@0e78a9f
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
Last edited:
ContentDeveloper
Member
This did not work.... still not seeing the Advanced Scene Switcher menu item show up in OBS on the other computer....
Warmuptill
Active Member
Then I am out of ideas unfortunately - I assume the message in the OBS log did not change from error 126, did it?
The redistributable is the only dependency I can think of.
Does the same issue also occur with builds that are not the special one-off build I shared with you?
Last edited:
ContentDeveloper
Member
I had installed your latest version.
The error did not appear in the log file.
Can you tell me which redistributable your installer tries to install?
Warmuptill
Active Member
These:
- x86: vc_redist.x86.exe
- x64: vc_redist.x64.exe
Or is there just a different error?
I'm having a bit of an issue getting the fullscreen detection to work when matching window titles with regex. I'm trying to have OBS switch to a scene with a game capture whenever ANY program is fullscreen. The regex used seems to work perfectly on RegExr, and if I uncheck "if fullscreen", it will lock OBS to the game capture scene, so I can only assume the regex is working fine in OBS too. If I select a fullscreen window out of the list of window titles, the fullscreen check will work just fine, but it would be a little annoying if every time I play something new I have to go in and manually add it into OBS. Maybe my regex is wrong, I don't know much regex myself so I had to resort to google which supplied me with both (.*) and [\s\S]+, neither of which will work. I've tried with multiple different games and none were detected when "if fullscreen" was checked.
Warmuptill
Active Member
Thanks for noticing this!
There was indeed an issue where the maximized and full-screen checks would only test for a direct match of the window title and not perform these check based on the regex pattern.
You can find a build with a fix here in a few minutes:
Fix regex matching for window tab · WarmUpTill/SceneSwitcher@aa031c5
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
If you see any issues with this new build please let me know.
Last edited:
GridMonkey
Member
Hey, 2 stream tests and everything works as expected. We're not currently using the other automatic features but the triggered recording and only active while streaming features seem to work perfectly. The UI shows the proper settings( compared to last build) and the record triggers work great.Thanks for testing the build and reporting the issues!
1) I will check what could be causing that. (Probably just forgot to update the UI when loading the settings)
2) You are right. I will make sure that the scene triggers also respect the state of the plug-in.I will also add an option to pause the triggers on certain scenes on the pause tab.
EDIT:
A build with both of these changes will be available here in a couple of minutes:
Add option to automatically start scene switcher on recording / streaming start · WarmUpTill/SceneSwitcher@0e78a9f
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
I appreciate your willingness to add the feature / quick communication and support. Alatus says thank you as well. Automation helps her focus more on her content than on how she put's it out there and that means a lot to her.
Grid
ContentDeveloper
Member
I noticed that when I ran your installer, it placed the dll file in the wrong location... I do not use the default location (running in "portable" mode), so had to put in a custom path.
Once I figured that out, and moved the dll, I did see the menu item show up. (NOTE: I had also found that same redist file -- 2015-2109) and installed that too.
Warmuptill
Active Member
Warmuptill updated Advanced Scene Switcher with a new update entry:
Add Scene Group and Scene Trigger tab
Read the rest of this update entry...
Add Scene Group and Scene Trigger tab
Read the rest of this update entry...
When running the latest version (1.9)
With the default transition is set to CUT.
Under Transition tab:
When scene "1" is active change default scene transition to "cut"
Under Sequence:
When "2" is active switch to "1" after "20" seconds using "Fade"
The transition begins from 2 to 1, but the image quickly jumps back to "2", apparently because of the settings under the transition tab.
I am just trying to keep the default transition as "cut", even after the sequence executes with "fade"
With the default transition is set to CUT.
Under Transition tab:
When scene "1" is active change default scene transition to "cut"
Under Sequence:
When "2" is active switch to "1" after "20" seconds using "Fade"
The transition begins from 2 to 1, but the image quickly jumps back to "2", apparently because of the settings under the transition tab.
I am just trying to keep the default transition as "cut", even after the sequence executes with "fade"