Warmuptill
Active Member
Maybe something similar to this will work for you?Можете ли вы показать мне, как его настроить?
Maybe something similar to this will work for you?Можете ли вы показать мне, как его настроить?
I tried manually installing it and still get the same problem. No error message but still not showing up under Tools.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?
Большое спасибо! Очень помог!Может быть, что-то подобное вам подойдет?
View attachment 87955
Can you share a log after attempting to manually install it?I tried manually installing it and still get the same problem. No error message but still not showing up under Tools.
It's installed here D:\obs-studioCan you share a log after attempting to manually install it?
Where is your obs installed?
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.
- Copy advanced-scene-switcher.plugin into ~/Library/Application Support/obs-studio/plugins/ (Should be done by the installer)
- Open ~/Library/Application Support/obs-studio/plugins/ in Terminal
- Run command: xattr -r -d com.apple.quarantine advanced-scene-switcher.plugin
Unfortunately, there is still no indication of the plugin being even attempted to be loaded.It's installed here D:\obs-studio
I attached the log.
D:\obs-studio\obs-plugins\64bit\advanced-scene-switcher.dll
actually exists?Yes, thank you.
Yes it's in there.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 fileD:\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.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 fileD:\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.
I found the problem on my end. Turns out I had a separate older vision I was working with. Anyway, it works fine and thanks for the help!Yes it's in there.
View attachment 87957
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.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.
Good point.@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?
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.Also, side note, maybe you can also add "Between" to simple settings?
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.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:
Add special handling for the "between" case when ignoring the date · WarmUpTill/SceneSwitcher@ad973d3
An automated scene switcher for OBS Studio. Contribute to WarmUpTill/SceneSwitcher development by creating an account on GitHub.github.com
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.
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!
Yes, you can, see example screenshot below.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.
Ah you are right.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.