-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feature request] toggle a scene filter #46
Comments
Oh this is exactly what I'm looking for. I made a post, which I'll delete right now. |
It seems as though this is already possible. the syntax is as follows obs-cmd filter This can be done for a source or scene. |
Hi. Sorry, but according to the code is not possible at the moment. According to current code:
it can be done currently over a source ( Or I'm missing something. If you, for real, can toggle the filter over a main scene (not an scene inside another either) instead of toggling a filter over a source inside a scene (different things, already possible), even when the current code I'm looking at seems to say otherwise, I would be grateful to know how with complete syntax and probably code and README of the project should be updated to properly reflect that possibility. Thanks. |
Hi. First of all, thanks for this piece of software 💚.
I have tried it and it works so well for me when I try to toggle a scene item with
obs-cmd scene-item toggle <scene> <item>
.But it doesn't have any option (as far as I know) to toggle a scene filter.
Is there any possibility to add a command to toggle that? Something like:
obs-cmd scene-filter toggle <scene> <filter-item>
.That would be pretty useful, specially to allow to automate usage of some specific plugins, like obs-move-transition. I want to do that using the streamdeck, but I could only achieve that if I'm able of doing such thing via commands and there is no simple/practical way of achieve that.
I know that this is supposed to have a minimal API, with I think this feature could be useful enough to be considered.
The text was updated successfully, but these errors were encountered: