I would move that from the General tab to its own Midi tab, or a combined Resources tab that handles *everything* that the macros use, but are not macros themselves. Kinda like what I was saying earlier. Variables, Websockets, Midi, etc. And keep it always available, to be able to add the first one that way too.
- Thread starter Warmuptill
- Start date
Good idea
flyingdoodah
New Member
Hey everyone! Any help would be appreciated! I'm a music teacher using OBS to run a digital backdrop for my school play. I did this successfully last year using an older version of OBS and Advanced Scene Switcher. I've since updated OBS, and now the duration modifier doesn't seem to be working consistently. I'm struggling and the play is next week! Here's how I have things set up, which worked last year:
The play has its own Scene Collection. The collection consists of video loops, which have no audio, and music videos for song and dance numbers. The video loops are active when there is dialogue. The music videos are active when there is singing and dancing.
Each music video has a loop before and after it in the scene collection. I have a duration modifier set to the exact length of the song. When the song is over, it should automatically switch to loop after it in the collection. I have all of the cues set up in order in the collection. I start at the top of the collection, follow along in the script, press the down arrow when there is a cue for a song, sound effect, or scene change, OBS advances to the next scene. When a song is finished playing, it automatically advances to the loop that comes after it in the collection.
I'm not sure what's going on. Sometimes it works and sometimes it doesn't. I don't know if there is a box that should be checked or unchecked. I'm not sure of any other factors that would be messing me up. Here is a screen shot of my macros and a shot of the scenes/OBS window
The play has its own Scene Collection. The collection consists of video loops, which have no audio, and music videos for song and dance numbers. The video loops are active when there is dialogue. The music videos are active when there is singing and dancing.
Each music video has a loop before and after it in the scene collection. I have a duration modifier set to the exact length of the song. When the song is over, it should automatically switch to loop after it in the collection. I have all of the cues set up in order in the collection. I start at the top of the collection, follow along in the script, press the down arrow when there is a cue for a song, sound effect, or scene change, OBS advances to the next scene. When a song is finished playing, it automatically advances to the loop that comes after it in the collection.
I'm not sure what's going on. Sometimes it works and sometimes it doesn't. I don't know if there is a box that should be checked or unchecked. I'm not sure of any other factors that would be messing me up. Here is a screen shot of my macros and a shot of the scenes/OBS window
Does the "at least" modifier work any better? I wonder if the "exact" one is getting skipped over.
It happens a lot in general software, for a naive programmer to look for "x == 5", for example, and then wonder why it never happens. The bug is exposed when a readout of "x" shows, "0, 1, 3, 4, 6, 7, ..."
flyingdoodah
New Member
Just tried "at least" and it still doesn't work.
If the file itself is that length, then you might use that for timing instead of a separate timer. Don't know why the timer doesn't work, so the same thing might kill both, but something I've done a lot is:
So regardless of how long the video is, the last 1/2-second of it (or whatever you set it for) is used to transition to the next scene.
It helps with that too, to have a scan interval that is much less than the time that you set here. I have mine all the way down, at 50ms.
.
Warmuptill
Active Member
I will try to think of something to resolve this.
Maybe some automated "re-connection" attempt if the device could not be found initially, so that if the device is connected later on it will just work.
Regarding the warning if a device is not connected.
Maybe I will simply add a new condition check for the MIDI condition which allows you to check which MIDI devices are currently connected.
Then you could do something "if not device X is connected -> display warning".
I can't give you an ETA yet unfortunately.
Currently it is not possible to access the clipboard contents, but I will add it to the todo list and let you know once that is possible.
Can you please enable verbose logging on the General tab.
Once you have done that please try to reproduce the issue and note down the time when the problem happened.
Afterwards please share the corresponding log file and if possible please export your settings to a file.
This will likely help in tracking down the problem.
If you want we can also set up a short call on the weekend and look at the issue together.
If so, send me a direct message.
Warmuptill
Active Member
Is anyone else experiencing issues starting with the 1.25.* releases with the thresholds of the "Audio" condition not working as they used to?
Meaning the same threshold values are resulting in different behavior in 1.25.* compared to earlier releases.
I believe this was reported on GitHub in https://github.com/WarmUpTill/SceneSwitcher/issues/1051, although the description was not quite clear enough.
If so, I would very much appreciate it, if someone, who did experience those types of issues and returned to an earlier version of the plugin because of it, can test if the following build does resolve the problem:
github.com
Any feedback regarding this topic would be very welcome (positive or negative)!
Please just make sure to back up your settings beforehand just in case!
Thank you!
Meaning the same threshold values are resulting in different behavior in 1.25.* compared to earlier releases.
I believe this was reported on GitHub in https://github.com/WarmUpTill/SceneSwitcher/issues/1051, although the description was not quite clear enough.
If so, I would very much appreciate it, if someone, who did experience those types of issues and returned to an earlier version of the plugin because of it, can test if the following build does resolve the problem:
Audio condition pull request run · WarmUpTill/SceneSwitcher@30b7887
An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
github.com
Any feedback regarding this topic would be very welcome (positive or negative)!
Please just make sure to back up your settings beforehand just in case!
Thank you!
Lawrence_SoCal
Active Member
I'm wondering if the basic logic is the issue, and Aaron's suggestion (what I was thinking) maybe more appropriate.
that is - Is there a measure of time for a Scene? yes, for a video playing, but how long a scene has been Active?
If the issue is how long the video is playing, then the Video is the trigger, not the Scene. And as Aaron mentioned, computers get busy and can miss 'exact' moment sometimes, so 'greater than', or 'equal or greater than' much more reliable triggers... 'cuz would you care all that much if trigger was 100 ms later?
Oh, and I use https://obsproject.com/forum/resources/media-controls.1032/ so I can monitor time remaining in a Video
flyingdoodah
New Member
Thank you. I will try both of those suggestions.
thegamingstig
Member
How can I set my NDI source as a trigger when my phone's NDI camera app is on/off?
I don't think *any* source on/off is available. To my knowledge, OBS just doesn't provide that information.
But you might use the Video condition to see if the picture is changing. OBS hangs on the last frame that it received, so a strict, pedantic "no change at all" might be fairly foolproof because the camera will always have some noise, which is still a (small) change. That won't work for PowerPoint slides or other things that are made entirely from still images, but it should for a video camera.
l1i1l
Member
Hi!
In versions 1.25.0, 1.25.1, 1.25.2 “Scene element visibility” by audio level trigger stops working.
@Warmuptill
In versions 1.25.0, 1.25.1, 1.25.2 “Scene element visibility” by audio level trigger stops working.
@Warmuptill
Warmuptill
Active Member
Can you please try this build mentioned here and report back if that resolves your issue.
You will have to reimport your 1.24.* settings for the automatic conversion of the audio threshold to function.
Thank you!
Is anyone else experiencing issues starting with the 1.25.* releases with the thresholds of the "Audio" condition not working as they used to?
Meaning the same threshold values are resulting in different behavior in 1.25.* compared to earlier releases.
I believe this was reported on GitHub in https://github.com/WarmUpTill/SceneSwitcher/issues/1051, although the description was not quite clear enough.
If so, I would very much appreciate it, if someone, who did experience those types of issues and returned to an earlier version of the plugin because of it, can test if the following build does resolve the problem:
Audio condition pull request run · WarmUpTill/SceneSwitcher@30b7887
An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.
Any feedback regarding this topic would be very welcome (positive or negative)!
Please just make sure to back up your settings beforehand just in case!
Thank you!
Last edited:
l1i1l
Member
The latest version in which everything worked for me was 1.24.2. When switching to any versions, starting from 1.25, the macros stops working, it simply does not respond to the trigger.
l1i1l
Member
I can confirm that when migrating from 1.24.2 to the 1.25.2-5 you suggested, there are no problems, the macros works as expected!
(tested on Windows 10)
Warmuptill
Active Member
Thanks a lot for the test / confirmation!
I will release an update with the fix later today! :)
l1i1l
Member
Thank you for efficiency!
Great job and great plugin!
Warmuptill
Active Member
Warmuptill updated Advanced Scene Switcher with a new update entry:
Advanced Scene Switcher 1.25.3
Read the rest of this update entry...
Advanced Scene Switcher 1.25.3
Read the rest of this update entry...