Advanced Scene Switcher

Advanced Scene Switcher 1.28.1

Warmuptill

Active Member
Можете ли вы показать мне, как его настроить?
Maybe something similar to this will work for you?
Hotkey.PNG
 

ExtraBulla

New Member
Sorry if that is an obvious question, but Is the plugin running?
You can check if it is active on the General tab / the status dock.
(See first red arrow)

If it is indeed active can you please enable verbose logging (second red arrow), reproduce the problem, and finally share the corresponding OBS log file?

View attachment 87951


Can you please try to manually install the plugin by placing the files from this archive advanced-scene-switcher-windows-x64.zip into your OBS installation directory? (E.g. C:\Program Files\obs-studio)


That seems really strange.
The "Run macro" button is only intended to be used to be able to test macro actions.
It does not affect whether or not a macro is "active" or not.

The only way to deactivate a macro is to use the checkboxes to the left of the macro names, highlighted below:
View attachment 87953
Their status will also update if a macro is paused e.g. via a hotkey / some other macro.

Are you able to reproduce the problem?
If so can you please share an OBS log with verbose logging enabled?
(See screenshot above on how to enable verbose logging)

So I don't think the solution to your problem would be adding some sort of indicator widget but to understand in what situation the plugin is after the crash.

Could it be that maybe the "WorkProfile" or "BlankProfile" macros were triggered and thus a different set of macros were loaded as the scene collection was changed?
I tried manually installing it and still get the same problem. No error message but still not showing up under Tools.
 

Si5584

New Member
Can you please share an OBS log file?

Can you please also share an OBS log file?
It seems that MacOS is quarantining the plugin for some reason, so you might have to undo that using the terminal.

  1. Copy advanced-scene-switcher.plugin into ~/Library/Application Support/obs-studio/plugins/ (Should be done by the installer)
  2. Open ~/Library/Application Support/obs-studio/plugins/ in Terminal
  3. Run command: xattr -r -d com.apple.quarantine advanced-scene-switcher.plugin

Is this what you require?

 

Warmuptill

Active Member
It's installed here D:\obs-studio
I attached the log.
Unfortunately, there is still no indication of the plugin being even attempted to be loaded.
So OBS cannot even see the plugin files.

Can you check if the file D:\obs-studio\obs-plugins\64bit\advanced-scene-switcher.dll actually exists?

Yes, thank you.

You have installed the "arm64" variant but seem to be running the x86_64 version of OBS.
Please either use advanced-scene-switcher-macos-universal.pkg or advanced-scene-switcher-macos-x86_64.pkg instead.
 

ExtraBulla

New Member
Unfortunately, there is still no indication of the plugin being even attempted to be loaded.
So OBS cannot even see the plugin files.

Can you check if the file D:\obs-studio\obs-plugins\64bit\advanced-scene-switcher.dll actually exists?


Yes, thank you.

You have installed the "arm64" variant but seem to be running the x86_64 version of OBS.
Please either use advanced-scene-switcher-macos-universal.pkg or advanced-scene-switcher-macos-x86_64.pkg instead.
Yes it's in there.
1666636063186.png
 

Si5584

New Member
Unfortunately, there is still no indication of the plugin being even attempted to be loaded.
So OBS cannot even see the plugin files.

Can you check if the file D:\obs-studio\obs-plugins\64bit\advanced-scene-switcher.dll actually exists?


Yes, thank you.

You have installed the "arm64" variant but seem to be running the x86_64 version of OBS.
Please either use advanced-scene-switcher-macos-universal.pkg or advanced-scene-switcher-macos-x86_64.pkg instead.
Thanks, all sorted. I had tried the other versions previously but I have done that again with x86 and all working now. I think I had to run the terminal commands.

Thanks again,

Si.
 
I had previously experiment "pause/unpause/run/stop" macros action. Pause/unpause appears check/uncheck the checkbox. When I tried using stop on macros, It stopped the macro permanently and not work again (just like when I use pause) - but checkbox remains check.

I haven't been able to reproduce the problem. But I will enable the verbose logging from now on.

The workprofile or blankprofile weren't trigger. I would know visually since both those profiles do not have platform server logins like my streamingprofile, and the have different sources, scenes, and plugin profiles.
 

CodeYan

Member
I had previously experiment "pause/unpause/run/stop" macros action. Pause/unpause appears check/uncheck the checkbox. When I tried using stop on macros, It stopped the macro permanently and not work again (just like when I use pause) - but checkbox remains check.

I haven't been able to reproduce the problem. But I will enable the verbose logging from now on.

The workprofile or blankprofile weren't trigger. I would know visually since both those profiles do not have platform server logins like my streamingprofile, and the have different sources, scenes, and plugin profiles.
Stop macro is not supposed to uncheck the checkbox. It's meant to be used to stop or "cancel" a macro that is currently executing. Pause macro pauses the evaluation of conditions. Meaning, if a macro is already executing, and you pause it, the macro will continue to execute, but will no longer execute again because the conditions will not be evaluated until you unpause it.
 

CodeYan

Member
@Warmuptill I installed the latest commit build so I can test the date macro, and the time issue is indeed fixed. However, my last macro condition doesn't work because it's 23:49 to 00:00, and it seems like it encompasses the whole day, rather than just 11 minutes. I can't type 24:00 for the second field so I can't do this, other than make it 23:59:59, but this is still a limitation. Like, what if I wanted the range to be 23:50 to 00:10?

Also, side note, maybe you can also add "Between" to simple settings?

1666765340989.png

As always, thank you for your work!
 

Warmuptill

Active Member
@Warmuptill I installed the latest commit build so I can test the date macro, and the time issue is indeed fixed. However, my last macro condition doesn't work because it's 23:49 to 00:00, and it seems like it encompasses the whole day, rather than just 11 minutes. I can't type 24:00 for the second field so I can't do this, other than make it 23:59:59, but this is still a limitation. Like, what if I wanted the range to be 23:50 to 00:10?
Good point.
I have attempted to change behaviour when using the "between" option in combination with ignoring the date component.
A build will be available here in a few minutes:

Also, side note, maybe you can also add "Between" to simple settings?
This will face the same problem as above but worse (due to relying on week days instead of specific dates) so I would like to keep the simple settings as is.
 

CodeYan

Member
Good point.
I have attempted to change behaviour when using the "between" option in combination with ignoring the date component.
A build will be available here in a few minutes:


This will face the same problem as above but worse (due to relying on week days instead of specific dates) so I would like to keep the simple settings as is.
Tried it by changing my time zone, well, the range 23:49 to 00:10 works for 23:49 to 00:00, but it no longer returned true after that. It's probably because it already changed dates, and so it now checked for 23:49 of the next day. I guess such time range is not possible, other than to split it into 2 conditions? Now i'm not sure how this should be handled in the UI.

As for not including it in simple settings, that's fine, thanks.
 
Sorry if that is an obvious question, but Is the plugin running?
You can check if it is active on the General tab / the status dock.
(See first red arrow)

If it is indeed active can you please enable verbose logging (second red arrow), reproduce the problem, and finally share the corresponding OBS log file?

View attachment 87951


Can you please try to manually install the plugin by placing the files from this archive advanced-scene-switcher-windows-x64.zip into your OBS installation directory? (E.g. C:\Program Files\obs-studio)






So, for whatever reason (yes, it was on "Active" already :) After several resets and turning off/on the PC a few times for various other reasons, it just started working today. Dunno! But it's back, baby!
 

BenAndo

Member
Is it possible to have a trigger based on an audio's muted/unmuted state that then triggers an action? Currently you can change an audio source as an action but not as a trigger.
An example is I want to make that if a particular audio source is unmuted, it then triggers a source - set settings.
 

CodeYan

Member
Is it possible to have a trigger based on an audio's muted/unmuted state that then triggers an action? Currently you can change an audio source as an action but not as a trigger.
An example is I want to make that if a particular audio source is unmuted, it then triggers a source - set settings.
Yes, you can, see example screenshot below.
1666868916966.png

If you don't see these options, update the plugin.
 

Warmuptill

Active Member
Tried it by changing my time zone, well, the range 23:49 to 00:10 works for 23:49 to 00:00, but it no longer returned true after that. It's probably because it already changed dates, and so it now checked for 23:49 of the next day. I guess such time range is not possible, other than to split it into 2 conditions? Now i'm not sure how this should be handled in the UI.

As for not including it in simple settings, that's fine, thanks.
Ah you are right.
I will now also try to shift the date into the past by 24h and checking if that matches to handle this case.

Btw. thank you very much for adding the wiki entry! :)
 
Top