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?
I use that on everything as a form of insurance, even if the condition itself naturally only occurs once. Never had a problem.
That worked thanks so muchThanks let me try that
I would do that differently. Instead of the entire sequence in one macro, have a separate macro for each scene: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.
I don't think that updating to the newest version will make any difference.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"
Yes that should be possible using a setup similar to this:Question about variables. Is there any way to set a variable to the value of a text source?
This example or the steps by @AaronD should work: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.
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.Yes that should be possible using a setup similar to this:
View attachment 92859
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.
Yes that should be possible using a setup similar to this:
View attachment 92859
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.
Thanks for reporting the problem!Hi. I found a bug on 1.21.0. on intel Mac OBS 28.1.2.
Even I choose different algorithms for the video condition's pattern matching option from cross correlation (e.g. correlation coefficient), it goes back to cross correlation when I relaunch my OBS.
Hi, sorry I was out of town for a week.... (touching grass in Yosemite)Sorry if I am stating the obvious or misunderstanding something, but the text area containing the transform data has a scroll bar.
The positional data should be part of the "pos" block towards the middle of the text field.
Does this value not change for you after moving the source and clicking the "Get transform" button again?
Or are you referring to something different with "location of the source"?
Sorry for coming back with so many questions instead of answers - I just want to be sure we are talking about the same thing :)
View attachment 92758
Changes:
- A confirmation prompt will now appear even when deleting only a single macro.
- Removed backwards compatibility for old versions of the "Studio mode" action.
This should prevent the log messages did not insert duplicate action entry with name "Studio mode" from appearing.- A warning message will now be displayed if a plugin of the advanced scene switcher (e.g. the video condition) fails to load.
Fixes:
- Resolved...
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.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.
If verbose logging is enabled the advanced scene switcher should log when it is sending out websocket messages and receiving them.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.
Sure that would be much appreciated! :)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.
Yep, that lines up with my observation.Just for completeness:
The fade does indeed perform a volume changes at a fixed interval of 100ms.
I'll see if I can make it misbehave on record. It's intermittent, which makes it harder, but not particularly rare.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?
Ooo! Nice!Sure that would be much appreciated! :)
I intended to start work on supporting MIDI devices anyway so that fits right in.