- Thread starter Warmuptill
- Start date
Frankiemagic13
New Member
Thanks let me try that
I use that on everything as a form of insurance, even if the condition itself naturally only occurs once. Never had a problem.
@Warmuptill What do you think the wisdom would be to make it the default?
Frankiemagic13
New Member
That worked thanks so much
ph0sphor_burn_out
New Member
Hey I am running Advanced Scene Switcher 1.20.5 with OBS 29.02 on Windows 11. I had a nice bunch of duration macros created that were working great a couple days ago and suddenly today they are basically not working/only occassionally are working. Is this because I need to update to the current version? Will updating screw with the macros I have created?
Also i should add that things are running fine on my mac. It's just on windows. and also, i can confirm that scene switcher is "on"
Also i should add that things are running fine on my mac. It's just on windows. and also, i can confirm that scene switcher is "on"
Last edited:
I must be missing something. Using ASS 1.20.5.
Showing several scenes with the Switch Scene followed by Wait action. All is working well. At the end of the Macro, I would like to repeat.
How do I loop back to the start of the Macro? In other words, a continuous loop?
Thanks much.
Showing several scenes with the Switch Scene followed by Wait action. All is working well. At the end of the Macro, I would like to repeat.
How do I loop back to the start of the Macro? In other words, a continuous loop?
Thanks much.
I would do that differently. Instead of the entire sequence in one macro, have a separate macro for each scene:
- If Current Scene is A for 5 seconds
- Switch to Scene B
- If Current Scene is B for 8 seconds
- Switch to Scene C
- If Current Scene is C for 12 seconds
- Switch to Scene A
And it's easy to jump out of the loop and not have it insist on jumping back in, like a single macro with Wait actions would.
Warmuptill
Active Member
I don't think that updating to the newest version will make any difference.
Can you share more details regarding what you have set up?
Would it be possible to share an export of your settings + a log file of the problem happening with verbose logging enabled?
(Both options can be found on the General tab)
Yes that should be possible using a setup similar to this:
It works by extracting the "text" value of the source settings using a set of regular expressions.
The condition itself is just used to extract the settings value - you can of course adjust it to your needs depending on when you want to change the variable value.
This example or the steps by @AaronD should work:
Automatically cycle through a list of scenes
An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
Thanks for this, I do need a little clarification tho. It looks like you are setting the value with the base of ("text":"example text"}. I'm not seeing where in this example setup it is actually pulling the value from the source you used Text(GDI+). It might help if I give my details.
I have a macro that isn't supposed to run for a number of seconds but that number can change based on other things, and I want to set a Text source (I'm calling it "CONFIG-delay") to the number of seconds I want the macro to wait. Then I'm intending to use that variable in the timed macro.
Figured I'd share my setup to clear Replay Buffer between saves:
- In Tools > Advanced Scene Switcher, in the General tab, lower "Check conditions every" to whatever is fast enough with negligible cpu cost (I use 50ms).
- In the Macro tab, create macro SaveAndClearReplayBuffer
- Add condition, [If] [Hotkey] "Save And Clear Replay Buffer"
- Add action, Replay Buffer Save replay buffer
- Duplicate SaveAndClearReplayBuffer to SaveAndClearReplayBuffer 2
- Edit condition to [If] [Macro] SaveAndClearReplayBuffer [Within the last] [3.00] [seconds]
- Add condition [And] [Replay Buffer] [Replay buffer saved]
- Edit action to [Replay Buffer] [Stop replay buffer]
- Duplicate SaveAndClearReplayBuffer 2 to SaveAndClearReplayBuffer 3
- Edit condition to [If] [Macro] SaveAndClearReplayBuffer 2 [Within the last] [3.00] [seconds]
- Edit condition #2 to [And] [Replay Buffer] [Replay buffer stopped]
- Edit action to [Replay Buffer] [Start replay buffer]
- Open Settings > Hotkeys and set "Save And Clear Replay Buffer" to a hotkey of your choice.
Warmuptill
Active Member
Thanks for reporting the problem!
A build with a fix will be available here in a few minutes:
Fix crash when using OCR check of video condition · WarmUpTill/SceneSwitcher@34602c5
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
Redolent Thought
Member
Hi, sorry I was out of town for a week.... (touching grass in Yosemite)
Yeah - those numbers aren't updating when I click the "get transform" - I'll try and enter manually - your screen shot actually helps a lot!
obsuser2023
New Member
Great app. Can I report a small bug for version 1.21.0?
Macro - video - match pattern, defaults to "cross correlation" no matter what u choose.
So if you change it to "correlation coefficient", close OBS and open, it goes back to "cross correlation". Tested on 2 windows PCs and new macros.
Thank you again for this amazing plug in.
Macro - video - match pattern, defaults to "cross correlation" no matter what u choose.
So if you change it to "correlation coefficient", close OBS and open, it goes back to "cross correlation". Tested on 2 windows PCs and new macros.
Thank you again for this amazing plug in.
Warmuptill
Active Member
Warmuptill updated Advanced Scene Switcher with a new update entry:
Minor changes and bug fixes
Read the rest of this update entry...
Minor changes and bug fixes
Read the rest of this update entry...
I'm a little bit behind now - 1.20.1, compared to yesterday's 1.21.1 - so this might have been fixed already. Or it could be a problem in OBS and not the plugin. Anyway, I noticed that an audio source fade over 0.50 seconds has a pronounced "zipper" effect. I think I counted 5 distinct pops over that time. (Adv. SS is running every 50ms) Mute/unmute has a single pop that sounds about the same.
My use is probably more of a challenge than most, in that it's much harder to hide the "zipper" in the original content, because it's a pure sine wave that is filtered out later. It's digitally generated, so its own harmonic content (distortion) is practically zero, and the filter is digital with the same clock, both of which make it easy to pick back out of a mix like I'm doing. It's not meant to get to the speakers, but if it misbehaves, then the misbehavior does.
My reasons to do that are:
The problem is that the mute-pop - or series of pops from a fade-zipper - cover the entire audio spectrum regardless of the original content, and so they show up on the soundtrack side of the crossover and continue on down that chain, regardless of whether I use the top end or the bottom end of the spectrum. It's not harmonics of the original sine, which would be entirely above the original frequency (if it were, then a 20kHz sine would be a convenient way to fix it, but it doesn't). It's a completely new signal that has nothing to do with the original, I suspect because two consecutive samples have vastly different values.
I've also thought about treating this as an XY problem and sending control signals directly from OBS to the DAW. Open Sound Control (OSC), for one example, or WebSockets again. But having seen what the WebSockets did originally, I still like the out-of-band audio idea a lot better!
OBS 29.0.2
Adv. SS 1.20.2
Ardour 6.9.0~ds0-1build1
Ubuntu Studio 22.04 LTS
My use is probably more of a challenge than most, in that it's much harder to hide the "zipper" in the original content, because it's a pure sine wave that is filtered out later. It's digitally generated, so its own harmonic content (distortion) is practically zero, and the filter is digital with the same clock, both of which make it easy to pick back out of a mix like I'm doing. It's not meant to get to the speakers, but if it misbehaves, then the misbehavior does.
My reasons to do that are:
- The WebSockets weren't getting through reliably from one copy of OBS and Adv. SS to another, even on the same machine. Most of the time they would, but then it would miss one, and the incomplete transition would create an audio feedback loop. After several iterations that eventually ended up just spamming the connection constantly (which did work, but also made it hard to override the receiving end manually), I switched to an audio trigger instead of WebSockets.
- I'm using more audio channels now than OBS really supports. My end goal is stereo, but with different mixes going to different places, I need to keep things separate and not mix them too early. OBS does *not* do multichannel very well, despite having the option! Not when it's feeding a loopback to another app at least, instead of a direct stream or recording. So I moved the entire audio chain into the DAW, which means that I need to generate control signals from OBS to control the DAW.
The problem is that the mute-pop - or series of pops from a fade-zipper - cover the entire audio spectrum regardless of the original content, and so they show up on the soundtrack side of the crossover and continue on down that chain, regardless of whether I use the top end or the bottom end of the spectrum. It's not harmonics of the original sine, which would be entirely above the original frequency (if it were, then a 20kHz sine would be a convenient way to fix it, but it doesn't). It's a completely new signal that has nothing to do with the original, I suspect because two consecutive samples have vastly different values.
I've also thought about treating this as an XY problem and sending control signals directly from OBS to the DAW. Open Sound Control (OSC), for one example, or WebSockets again. But having seen what the WebSockets did originally, I still like the out-of-band audio idea a lot better!
OBS 29.0.2
Adv. SS 1.20.2
Ardour 6.9.0~ds0-1build1
Ubuntu Studio 22.04 LTS
I did some more testing, and it seems like an OBS problem, not the plugin. Manually muting and dragging the volume control does the same thing.
So I'm back to wondering now about the reliability of network comms in Adv. SS, given that WebSockets from one copy to another on the same machine is not reliable. If the sending part of Adv. SS is fine, and the transport is fine, and only the receiving part of Adv. SS needs work, then using Ardour for the receiving end might be okay? Not sure how to test that theory without a debugging environment.
Anyway, for controlling Ardour, other DAW's, physical consoles, and other audio tools, what would you think of adding support for OSC? Commands first, ignoring the response, then possibly eventually adding the response later as a condition.
I ended up writing a command-line utility to send OSC commands over UDP to a specific IP:port, all of which comes as arguments, so now I can control a Behringer X32 console from the Run action in Adv. SS, but it would be more convenient to have OSC built into Adv. SS.
@Warmuptill I can PM you the source for that utility if you'd like to use it for a starting point. It's pared down from a GUI app with wxWidgets that also controls that board, so it still has some remnants of that, but it should still be readable enough.
Warmuptill
Active Member
Just for completeness:
The fade does indeed perform a volume changes at a fixed interval of 100ms.
Maybe that could help in figuring out which message gets lost / ignored?
I intended to start work on supporting MIDI devices anyway so that fits right in.
The fade does indeed perform a volume changes at a fixed interval of 100ms.
If verbose logging is enabled the advanced scene switcher should log when it is sending out websocket messages and receiving them.
Maybe that could help in figuring out which message gets lost / ignored?
Sure that would be much appreciated! :)
I intended to start work on supporting MIDI devices anyway so that fits right in.