Advanced Scene Switcher 1.31.0

[Warmuptill]

https://obsproject.com/logs/tDF58noPFJGOJ7DU

New User, installed plugin per instructions, Mac Sequoia M1 Pro - Crash happens when opening OBS

Unfortunately there is no indication of the advanced scene switcher even being loaded in the log you shared.
Do you have a crash log as well?
On MacOS this should be contained in the dialog window popping up informing you that OBS crashed.

In case you did not use the installer and manually placed the files in the corresponding directories please ensure to "sign" the files afterwards as described here:

Installation

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

github.com

 

[cdante100]

I am at a bit off a loss.
The log does unfortunately not give any conclusive hints as to what the problem might be.

Can you please send me an export of your settings?
You can export them to a file on the General tab.
Please send them to me via DM and not here to make sure your Twitch token does not get leaked.

I apologise that it is such a chore to get it working for you for some reason.

Hi man, i've sended you some update about the bug

 

[FOXENHEiM]

Hi there,

After updating to 1.31.0 (from 1.27.0) some "if statements" are not working. Specifically the ones I use to control one of my sound sources. Everything else seem to work perfectly, but the macros controlling audio level does not work, even after creating new ones.

I used them in the following way:
I had 4 marcos with if statements running together to govern the "audio configured volume" of my sound source, by looking at the "audio output level". Each macro would do something like the following:

If [output volume] exceeds (x)
And [configured volume] is exactly (y)
Then adjust [configured volume] to (73%)(this value changes based depending on (y))

These macros don't do anything anymore. As a side note the version I used did not have any fractions available for volume percentages, and could only be configured as percentage. V 1.31.0 can now be configured in either percentage or db, and percentage now has fractions available. I did double, triple an quadtriple checked that the volume levels match to the fraction perfectly stil with no success, not sure if the fractions are somehow causing this.

When I remove the "And [configured volume] is exactly (y)" part of the trigger works, but if Advanced scene Switcher does not know the current configured volume, it will not know which one of the 4 macros to fire.

Is there any known workaround for this? Or should I downgrade?

Also thank you so very much for this amazing plugin, such a lifesaver. Thank you for all the hard work <3

 

[Warmuptill]

Hi there,

After updating to 1.31.0 (from 1.27.0) some "if statements" are not working. Specifically the ones I use to control one of my sound sources. Everything else seem to work perfectly, but the macros controlling audio level does not work, even after creating new ones.

I used them in the following way:
I had 4 marcos with if statements running together to govern the "audio configured volume" of my sound source, by looking at the "audio output level". Each macro would do something like the following:

If [output volume] exceeds (x)
And [configured volume] is exactly (y)
Then adjust [configured volume] to (73%)(this value changes based depending on (y))

These macros don't do anything anymore. As a side note the version I used did not have any fractions available for volume percentages, and could only be configured as percentage. V 1.31.0 can now be configured in either percentage or db, and percentage now has fractions available. I did double, triple an quadtriple checked that the volume levels match to the fraction perfectly stil with no success, not sure if the fractions are somehow causing this.

When I remove the "And [configured volume] is exactly (y)" part of the trigger works, but if Advanced scene Switcher does not know the current configured volume, it will not know which one of the 4 macros to fire.

Is there any known workaround for this? Or should I downgrade?

Also thank you so very much for this amazing plugin, such a lifesaver. Thank you for all the hard work <3

I am not aware of any issues with the audio condition type.
But that of course doesn’t mean that there isn’t a potential issue. ;)
I will try to look into it later today.

In case you did not do so already you can enable visual indicators to help identify when a condition evaluate to true or false.

Troubleshooting

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

github.com

 

[FOXENHEiM]

I am not aware of any issues with the audio condition type.
But that of course doesn’t mean that there isn’t a potential issue. ;)
I will try to look into it later today.

In case you did not do so already you can enable visual indicators to help identify when a condition evaluate to true or false.

Troubleshooting

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

github.com

Thank you very much for getting back to me. I will use the visual indicators to do some more trouble shooting abd let you know what I find. Thanks again

 

[FOXENHEiM]

I am not aware of any issues with the audio condition type.
But that of course doesn’t mean that there isn’t a potential issue. ;)
I will try to look into it later today.

In case you did not do so already you can enable visual indicators to help identify when a condition evaluate to true or false.

Troubleshooting

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

github.com

I think I have an idea of what's happening: I don't think the problem has anything to do with ASS...or not really.

I updated OBS and with it all of my plugins. And that is when the volume macros stopped triggering. I used the visual indicaters like you sugested and I was able to determine that it is the [configured volume is EXACTLY] that does not trigger. This change in behaviour of my macros happens even if I dont update ASS after updating to OBS to 31.2.1

It's the OBS update that introduces the fractions(with volume percentage), even if I don't update ASS.

I used the MOVE plugin in conjunction with ASS to change the volume to certain db values. But it seems that when the MOVE plugin change the volume, it is not exact enoigh for the new OBS fractions or something like that, because the "match exactly" trigger doesn't work.

When I changed the macros to use the ASS internal AUDIO volume adjustments, it now triggers. Leading me to believe that the ASS volume change is exactly accurate. That, or maybe the ASS reads the volume differently from OBS.

Anyway, I found a way to get it to work again, but thought I should give the info.
Thanks again