Advanced Scene Switcher

Advanced Scene Switcher 1.28.1

Kaisercelt

New Member
The plugin will check all conditions and perform actions (if applicable) at a set interval. (Every 300 ms per default - This interval can be configured on the General tab)
Using the "Automated scene change was triggered in this interval" condition type will allow you to limit the amount of scene switches to one per interval.
It is not related to any time restrictions for any macro conditions you might have in place.

Ah... perfect. Thanks.

I can set that slightly higher than 300ms also.
 
Hi, I have suffered crashes just today after activating advanced scene switcher for the first time and setting a few triggers.
I've been using only audio and random.
I don't know where to find a crash report


Does any one know what I'm supposed to do?
 

Warmuptill

Active Member
Sorry, to hear that you are having issues.
Please do share the crash reports - you can find them here:
CrashReport.png
 
Hi and thanks for answering. Here is the latest crash report but something is wrong. The time of the crash report is incorrect, the latest crash happened just now at 3:30ish french time. Another weird thing I just noticed is that there doesn't seem to be any crash reports for any of the crashes I've been experiencing. The times for all crash reports from the whole folder, I do not recognize as times when I actually had the crashes. And there seem to be too few of them.

I'll describe the crash:

Latest one, I wasn't even streaming, just testing out settings. I wasn't really looking because I was doing something else and when I got back to OBS, it was frozen.
Note that only the preview was frozen, I could actually interact with the software briefly, and then it completely froze and I had to manually shut it down. And this seems to happen every time it crashes, except that once I noticed the frame which was frozen was right in the middle of an automated scene switch from advanced scene switcher.

At first, I was using audio and random tabs, but when I saw they were discontinued I switched everything to Macros.
 

Attachments

  • Crash 2022-03-29 00-43-00.txt
    212.8 KB · Views: 17

Warmuptill

Active Member
Hi and thanks for answering. Here is the latest crash report but something is wrong. The time of the crash report is incorrect, the latest crash happened just now at 3:30ish french time. Another weird thing I just noticed is that there doesn't seem to be any crash reports for any of the crashes I've been experiencing. The times for all crash reports from the whole folder, I do not recognize as times when I actually had the crashes. And there seem to be too few of them.

I'll describe the crash:

Latest one, I wasn't even streaming, just testing out settings. I wasn't really looking because I was doing something else and when I got back to OBS, it was frozen.
Note that only the preview was frozen, I could actually interact with the software briefly, and then it completely froze and I had to manually shut it down. And this seems to happen every time it crashes, except that once I noticed the frame which was frozen was right in the middle of an automated scene switch from advanced scene switcher.

At first, I was using audio and random tabs, but when I saw they were discontinued I switched everything to Macros.
Unfortunately I don't see any obvious indication that the scene switcher would be involved in the crash in the provided log.
Can you share which settings you are using exactly? (By exporting the settings to a file on the General tab)
Is the scene switchers settings menu opened when you are encountering these freezes / crashes?
 
Last edited:
Unfortunately I don't see any obvious indication that the scene switcher would be involved in the crash in the provided log.
Can you share which settings you are using exactly? (By exporting the settings to a file on the General tab)
Is the scene switchers settings menu opened when you are encountering these freezes / crashes?
Hi these are settings + latest crash report which I still am not sure has the correct date and time stamp
 

Attachments

  • Crash 2022-03-29 16-47-33.txt
    190.2 KB · Views: 25
  • adv-ss-FFVIIR-2022.03.30.00.44.24.txt
    15.7 KB · Views: 21

Warmuptill

Active Member
Hi these are settings + latest crash report which I still am not sure has the correct date and time stamp
The time stamp of the crash is printed at the top of the log.
In this example: Date/Time: 2022-03-29, 16:47:32
So it seems reasonable.

But, unfortunately, the new crash log also does not indicate any obvious involvement of the scene switcher plugin.
So I am not sure how I can help :(

Just like last time the crash happened in "libobs: graphics thread" - so OBS's main graphics thread, if I am not mistaken.
The scene switcher was just "sleeping" / performing a "Wait" action at the time of this particular crash, so it is rather unlikely that it was involved.

Do you maybe have any other plugins installed that might interfere with OBS's graphics system?

P.S.:Sorry about the delayed reply!
 
Why there is no function to switch sources instead scenes? I don't need that at all.
Hey what I did was create two identical scenes but with the one source switched. The only thing I can"t seem to do is make one source go with an animation while the rest of the sources stay put, sadly.
 

Warmuptill

Active Member
Why there is no function to switch sources instead scenes? I don't need that at all.
I assume you probably intend to toggle the visibility of sources, but it would be best if you describe what you want to achieve in more detail.

To toggle the visibility of sources you can for example create a macro similar to this one:
example.PNG

For a general overview on how to create macros have look at this wiki page:
 
The time stamp of the crash is printed at the top of the log.

In this example: Date/Time: 2022-03-29, 16:47:32

So it seems reasonable.



But, unfortunately, the new crash log also does not indicate any obvious involvement of the scene switcher plugin.

So I am not sure how I can help :(



Just like last time the crash happened in "libobs: graphics thread" - so OBS's main graphics thread, if I am not mistaken.

The scene switcher was just "sleeping" / performing a "Wait" action at the time of this particular crash, so it is rather unlikely that it was involved.



Do you maybe have any other plugins installed that might interfere with OBS's graphics system?



P.S.:Sorry about the delayed reply!


Thank you for the reply, anyway I was trying to figure out why it would crash, with or without the plugin active.

What I found out is : there is no crash report for the crashes I'm experiencing. For example, it crashed just now, but the last crash report dates back to yesterday.

I think whatever crashes OBS reports are when I reboot the machine and it is forced to stop by the system or something, don't really know what is happening here.

I also found out something else: I was able to let my computer on AND streaming to twitch WITH the plugin active for more than 9 hours while I was sleeping. I was very surprised to find it up and running without a single hiccup when I woke up, although it crashed a few moments after I started using it... I think this might indicate that the crashes are related to PC load or system stability. I haven't got any type of OC going on, I have a good cooler for my Ryzen 5 3600X and the GPU is a stock RTX 2070 Super.

I tried streaming this morning with minimalistic behavior, not many apps running on the PC, just a game and the stream and it crashed.

I also suspected Windows Search Indexer to be a cause of instability because it was somehow running in the background forever at 15-20% CPU load, without ever throttling even when I game, so I disabled the service entirely, and tried streaming this morning but it still failed.

I tried to reeproduce the exact same conditions from the previous crash from this morning, but without enabling advanced scene switcher, and it didn't crash.. what I noticed were lags in the game and sound issues at times, but it came back to normal quickly, and that scenario reproduced a few times during the stream. Then, I enabled the plugin and it suddenly crashed after a minute or so. This time something ele happened, though. Instead of force closing OBS as soon as it was frozen, I let it run frozen for a while, and I could see it was still using CPU and ram, and the PC was completely laggy, barely useable. I let this go for a while and then, when nothing happened, I force closed the OBS process. But as I did, the game crashed (FFVII Remake) and then two identical pop ups arreared saying the GPU had been reset and I should check my drivers. I don't know if both windows belonged to FFVII or if one of them, or both, actually belonged to OBS or plugins.

Again, no crash report, for either of the two crashes from this morning.
 
Hi!

I have been doing some testing and I have found useful information!

I do not know why OBS didn't report those freezes as crashes, but it doesn't matter because I found the crash in normal log files, NOT crash logs.


here is the log file, crash happened at 5:24, and I left OBS opened frozen for about two minutes before terminating the process.
 

Attachments

  • 2022-04-03 03-59-05.txt
    293.6 KB · Views: 21

Warmuptill

Active Member
Hi!

I have been doing some testing and I have found useful information!

I do not know why OBS didn't report those freezes as crashes, but it doesn't matter because I found the crash in normal log files, NOT crash logs.


here is the log file, crash happened at 5:24, and I left OBS opened frozen for about two minutes before terminating the process.
Unfortunately this log file does not really give any further insights as to what the issue might be.

I will run a longer automated scene switch test on my end as well, but I don't have high hopes for a reproduction.
The reason being that switching scenes is such a basic functionality of this plugin that I think such a severe issue of OBS freezing would be more wide spread.

As you mentioned noticing GPU driver reset messages during some of the freezes / crashes it might be worth investigating further in that area. But to be honest I don't really have an idea how, unless you happen to have a second, known working graphics card lying around for a reference test.

I am sorry, that I am not really of much help here :(
 
The plugin only checks the volume of an audio source and not the frequencies used - if that is your question.
hey guys just getting back to OBS and last time I posted was like page 30 something of this thread lol... i jumped ahead to page 76 but so much info that is not what I was looking for I find myself breezing thru to quick. So I figured I might as well ask to see if I can be pointed to what I may be looking for / need

I need to be able to switch via tone, and just checking if this has changed since that last post?
 

AaronD

Active Member
hey guys just getting back to OBS and last time I posted was like page 30 something of this thread lol... i jumped ahead to page 76 but so much info that is not what I was looking for I find myself breezing thru to quick. So I figured I might as well ask to see if I can be pointed to what I may be looking for / need

I need to be able to switch via tone, and just checking if this has changed since that last post?
Not that I know of, but there was a mention of using the volume post-filters. I haven't looked to see if that's been implemented, but if it has, then maybe you can put an aggressive EQ on a source that you leave muted or otherwise route away from the audience?

Also, you mentioned using DTMF tones for control. Those are quite specific, more so than I would expect from a filter that is designed to be heard. So you might need to have those filters outside of OBS, and then bring the results in already processed: one input per possible tone, none of which go to the audience, but Adv-SS can pick them up as volume-triggers.
 
and then bring the results in already processed: one input per possible tone, none of which go to the audience, but Adv-SS can pick them up as volume-triggers.
can you explain what you mean by this? i think im a bit confused. we have the tone saved. and it a quite the difference in volume. i actually created a ffmpeg/bat file to create tones

it may be possible with ffmpeg to listen for tone and do some sort of trigger to OBS, maybe trigger a hotkey from a .bat file? that hotkey will have a macro sequence
 
Top