Advanced Scene Switcher 1.28.1

[TheMegaXandy]

I'm having a problem using the plugin's "Run" action. For example, I have a cmd command that I would like to run:

piper --model pt_BR-faber-medium.onnx --output_file TTS-generating.wav < text.txt && del TTS.wav && rename TTS-generating.wav TTS.wav

How do I adapt this to the plugin's "Run" action?
I also have another simpler cmd command, which I was not successful in:

del TTS.wav

Both commands take a specific folder to be executed.
Note that the commands work properly in a command prompt window. So there is nothing wrong with the command syntax, nor with the exe file being executed.

 

[Warmuptill]

OBS 30, yes, and the last adv-ss I tried was 1.23.1 which I updated to 1.24.0 and both worked fine before the OS update yes - to further clarify, it wasn't the major version upgrade. I had already done that and things were still working as of Silverblue 39.20231128.0 (2023-11-28T00:51:38Z).

Sorry to come back with yet another clarification question:
The exact same OBS and plugin version caused crash with the newer OS version, right?

I'm having a problem using the plugin's "Run" action. For example, I have a cmd command that I would like to run
How do I adapt this to the plugin's "Run" action?

I think you are misunderstanding what the "Run" action is doing.
The "Run" action is not launching the shell / command prompt of whichever OS you are using and then running the string you have passed to the "Run" action in that shell environment.
Instead is is simply trying to launching whichever executable file you pass to it with a given set of arguments.

This is why running shell specific built-in commands or keywords like echo, del , <, >, |, ... won't have any effect.

If you do want to run shell commands with the "Run" action you can either put those commands in a script and run that instead or start the shell / command prompt binary itself and pass the commands you want to run as an argument.

For example, if you would want to use the cmd.exe shell environment to run the echo hi > someTextFile.txt command you would have to start the cmd.exe binary and pass /c as the first argument and echo hi > someTextFile.txt as the second argument.
(See https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/cmd for a description of the arguments supported by cmd.exe)

Both commands take a specific folder to be executed.

You can set the folder in which the command should be executed using the "Working directory" field.
The default working directory will be the folder in which the OBS binary is located at.

Hope that helps!
Let me know if you need further examples!

 

[obsfan]

The exact same OBS and plugin version caused crash with the newer OS version, right?

Right. I just rolled back to the last working OS version, Silverblue 39.20231128.0 (2023-11-28T00:51:38Z), OBS is 30.0.2 and adv-ss is 1.24.2. Everything is working perfectly. Those are the same versions of OBS and adv-ss I had installed with the newest F39, 39.20231219.0 (2023-12-19T00:35:47Z), in which the plugin appears to make OBS silently fail but OBS will start and run fine in safe mode or with the plugin uninstalled.

 

[TheMegaXandy]

I think you are misunderstanding what the "Run" action is doing.
The "Run" action is not launching the shell / command prompt of whichever OS you are using and then running the string you have passed to the "Run" action in that shell environment.
Instead is is simply ...

Yes, that's what I wanted to say! I wanted to run shell commands, and your example helped me.

I was confused about how I should use the "Run" action to accomplish what I wanted to do. I didn't know if I should put everything in the Run text box, much less did I know that I had to divide the arguments this way. (In the command prompt we put everything on a single line).

But now with your example, I managed to make it work, and this will possibly help me solve some race condition problems I'm having.

Just one more quick yes or no question. When I run this action block as shown above, will the plugin wait for the process to close, so that it can continue with the next actions, or will the plugin not wait? (It will be great if the plugin waits, even better if I can choose).

 

[Warmuptill]

Just one more quick yes or no question. When I run this action block as shown above, will the plugin wait for the process to close, so that it can continue with the next actions, or will the plugin not wait? (It will be great if the plugin waits, even better if I can choose).

At the moment the plugin does not wait for the spawned process to exit.
But I can try to look into adding an option to toggle this behaviour.

 

[Warmuptill]

At the moment the plugin does not wait for the spawned process to exit.
But I can try to look into adding an option to toggle this behaviour.

A build with the option to wait for a process to terminate will be available here in a few minutes:

Process wait · WarmUpTill/SceneSwitcher@3937f81

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

(You will have to be logged into GitHub to be able to download it)

Let me know if you run into any issues!

 

[ReaulBShea]

I downloaded the dvanced Scene Switcher plugin however it doesn’t look like I think it should when I look at examples on Advanced Scene Switcher on YouTube. I am attaching a screenshot here. Does this look correct? I think there are supposed to be more tabs then just in general and macro. Please let me know ASAP. Thank you

 

[AaronD]

I downloaded the dvanced Scene Switcher plugin however it doesn’t look like I think it should when I look at examples on Advanced Scene Switcher on YouTube. I am attaching a screenshot here. Does this look correct? I think there are supposed to be more tabs then just in general and macro. Please let me know ASAP. Thank youView attachment 100290

YouTube and most other guides are out of date. That's often the trouble with those things. They look wonderful...except they don't actually work anymore.

The functionality in the other tabs can all be done with macros if you really understand what's going on.

The other tabs are still there...for now...if you uncheck the option that's barely clipped off in your screenshot. But they're not maintained anymore and they'll eventually go away entirely, if my understanding is correct. So try to avoid them for any new stuff, and try to migrate anything you do have there into the macros.

 

[sgt_quagmire]

I'm attempting to do a macro that detects a scene switch and adjusts audio of a source upon change. I noticed under the Audio tab it has set source volume but only allows a percentage. Is there a way to change it to a specific dB?

 

[AaronD]

I'm attempting to do a macro that detects a scene switch and adjusts audio of a source upon change. I noticed under the Audio tab it has set source volume but only allows a percentage. Is there a way to change it to a specific dB?

No, but there's a direct correlation. Once you play with it a bit, you can pick the percentage that gives you the dB you want.
That also means it shouldn't be too hard for @Warmuptill to add a choice of units, right? (until someone wants to use a variable with both units in different places)

That said though, I've only ever used 0% and 100%, which makes this point mostly moot. My actual mix is done with the compressors' makeup gains, since they're already there anyway. I use a DAW for all that, but it works in OBS too.

 

[TheMegaXandy]

A build with the option to wait for a process to terminate will be available here in...

Sorry for the delay in responding, but it worked flawlessly! Thanks!

 

[Gunthrek]

Just wanted to say I appreciate the update that made it so we can track current recording time! It's nice to see a developer quickly resolve an issue brought up by a user. When I'm not broke AF, I'll try to remember to come back and drop some support. Thanks!

 

[Studiobug]

#New Feature Request
When you minimize the "Wait" feature it should tell tell you how many seconds you asked the system to wait for. Right now every other feature seems easily recognizable when minimized by a label except the Wait feature. Please consider changing.

 

[sgt_quagmire]

No, but there's a direct correlation. Once you play with it a bit, you can pick the percentage that gives you the dB you want.
That also means it shouldn't be too hard for @Warmuptill to add a choice of units, right? (until someone wants to use a variable with both units in different places)

That said though, I've only ever used 0% and 100%, which makes this point mostly moot. My actual mix is done with the compressors' makeup gains, since they're already there anyway. I use a DAW for all that, but it works in OBS too.

It becomes real hard to play the guessing game with % as it takes the percentage of the current dB which makes it inconsistent when switching from different scenes but @Warmuptill helped me out and came in clutch with a new build that has a dB value

 

[GnomeAssociate]

I downloaded the dvanced Scene Switcher plugin however it doesn’t look like I think it should when I look at examples on Advanced Scene Switcher on YouTube. I am attaching a screenshot here. Does this look correct? I think there are supposed to be more tabs then just in general and macro. Please let me know ASAP. Thank youView attachment 100290

On the general tabl locate the following and uncheck the box indicated below.

 

[Warmuptill]

#New Feature Request
When you minimize the "Wait" feature it should tell tell you how many seconds you asked the system to wait for. Right now every other feature seems easily recognizable when minimized by a label except the Wait feature. Please consider changing.
View attachment 100534

Sure, a build with this change will be available here in a few minutes:

Cleanup · WarmUpTill/SceneSwitcher@e5b0148

An automation tool for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.

github.com

Just wanted to say I appreciate the update that made it so we can track current recording time! It's nice to see a developer quickly resolve an issue brought up by a user. When I'm not broke AF, I'll try to remember to come back and drop some support. Thanks!

Glad to hear that the plugin is of use to you! :)
(There is no need / no way to support the plugin financially - but I appreciate the offer!)

 

[BallLicker42069]

I am having an issue with the "check conditions every X seconds" part. Every time it checks conditions, my mouse shows the blue loading circle to the top right of the mouse for like 0.25sec. This is driving me absolutely crazy and I've looked everywhere for a fix, but it seems either no one else has this issue or I'm the only one who is being driven crazy by it.

Is there any way to stop it from changing my mouse to the loading symbol every single time it checks conditions? I would love to keep using this (while keeping the loading symbol enabled for other things) as it is exactly what I was looking for, but it is driving me NUTS.

Thanks for the plugin.

 

[Warmuptill]

I am having an issue with the "check conditions every X seconds" part. Every time it checks conditions, my mouse shows the blue loading circle to the top right of the mouse for like 0.25sec. This is driving me absolutely crazy and I've looked everywhere for a fix, but it seems either no one else has this issue or I'm the only one who is being driven crazy by it.

Is there any way to stop it from changing my mouse to the loading symbol every single time it checks conditions? I would love to keep using this (while keeping the loading symbol enabled for other things) as it is exactly what I was looking for, but it is driving me NUTS.

Thanks for the plugin.

Unfortunately, this is the first time I am hearing about such behaviour and I have never seen this before myself.
Can you describe what you have configured / export your settings to a file and share it?
This might give hints as to what might be causing the problem.

 

[BallLicker42069]

Unfortunately, this is the first time I am hearing about such behaviour and I have never seen this before myself.
Can you describe what you have configured / export your settings to a file and share it?
This might give hints as to what might be causing the problem.

Thanks for the quick reply. I attached my settings export and here's a video of what happens too if it helps at all. I also tried re-installing using the windows non-installer version (original install was with the installer) just in case but still ended up with the same thing.

 

[Warmuptill]

Thanks for the quick reply. I attached my settings export and here's a video of what happens too if it helps at all. I also tried re-installing using the windows non-installer version (original install was with the installer) just in case but still ended up with the same thing.

I can't reproduce the behaviour on my end when using your settings.
But one thing seemed a bit strange to me and might be related to the cursor issue.

What do you intend to achieve with this condition?

It will result in "valheim.exe" being started every 250 milliseconds which is probably not what you are trying to do.
This probably causes a lot of system load and could result in this cursor behavior.