I tried out the motion-filter on a scene, and was initially confused why it wasn't working even though I followed the short and simple instructions in the readme. I eventually realised it was because I was in studio mode, and the filter only applies to preview not program.
If this is an intentional design decision or a limitation of OBS's structure, then it would be great to add a note to the readme to indicate that motion-filter is not compatible with studio mode. I didn't see any docs apart the readme and couldn't find any relevant mention of studio mode in issues/codebase/etc.
If it's something that can probably be fixed, and if you don't have time/motivation, I might have time in the next few weeks to take a look - if you can point me in the right direction - but no promises
Problem description:
When in studio mode, the motion filter on a scene only applies the filter to the preview feed. With the same scene visible in both preview and program, you can use hotkey triggers for the filter and see that only the preview feed is changed. With scene change trigger, the motion filter effect is only visible if you transition to and from the same scene.
Steps to reproduce:
Make a scene with a source in it
Apply the motion filter to the scene
In the filter properties, set the source to the source. Set trigger to scene switch (hotkey also demonstrates this). Set some random start/destination X/Y values
Close filter properties
Enable Studio Mode
Transition to your scene multiple times in a row (transition from and to the same scene). Notice that the effect is only applied in the preview window
Transition away from the scene (to a second scene) and back to it. Notice that no effect is visible at all (since after transitioning to the scene, the second scene is in preview)
Workaround:
For one of my use cases, I am using the hotkey trigger, and I was able to work around this by adding a new second scene, adding the original scene to the second scene using the scene source type. This layer of scene-indirection-abstraction appears to make OBS always show the live version of changes to the scene to program. This doesn't work for the scene change - only for hotkey
Hello!
OBS Version: 27.0.1 motion-effect version: 1.2.1
Love the plugin!
I tried out the motion-filter on a scene, and was initially confused why it wasn't working even though I followed the short and simple instructions in the readme. I eventually realised it was because I was in studio mode, and the filter only applies to preview not program.
If this is an intentional design decision or a limitation of OBS's structure, then it would be great to add a note to the readme to indicate that motion-filter is not compatible with studio mode. I didn't see any docs apart the readme and couldn't find any relevant mention of studio mode in issues/codebase/etc.
If it's something that can probably be fixed, and if you don't have time/motivation, I might have time in the next few weeks to take a look - if you can point me in the right direction - but no promises
Problem description:
When in studio mode, the motion filter on a scene only applies the filter to the preview feed. With the same scene visible in both preview and program, you can use hotkey triggers for the filter and see that only the preview feed is changed. With scene change trigger, the motion filter effect is only visible if you transition to and from the same scene.
Steps to reproduce:
Workaround:
For one of my use cases, I am using the hotkey trigger, and I was able to work around this by adding a new second scene, adding the original scene to the second scene using the scene source type. This layer of scene-indirection-abstraction appears to make OBS always show the live version of changes to the scene to program. This doesn't work for the scene change - only for hotkey