Skip to content
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

Virtual Greenscreen filter does not initialize if Source is 0x0 #760

Open
adjstreams opened this issue Jan 1, 2022 · 10 comments
Open

Virtual Greenscreen filter does not initialize if Source is 0x0 #760

adjstreams opened this issue Jan 1, 2022 · 10 comments
Assignees
Labels
bug Bugs such as crashing, freezing, broken functionality, etc.

Comments

@adjstreams
Copy link

adjstreams commented Jan 1, 2022

Operating System

Windows 10 1903 and higher

OBS Studio Version?

27.1

StreamFX Version

0.11.0a1

OBS Studio Log

https://obsproject.com/logs/ze6AL_A8Cb-sJz64

OBS Studio Crash Log

No response

Current Behavior

After an OBS restart, a source mirror (of a camera) with virtual greenscreen filter applied is still present in the filter list and enabled with "quality" selected, but doesn't actually apply the greenscreen effect at all, until you go into the filter and toggle the dropdown value to performance, then it becomes re-enabled. It appears to forget, or perhaps has a failure to enable the virtual greenscreen filter properly after the restart.

Expected Behavior

At the point of restarting OBS, the source mirror should retain the virtual greenscreen effect that was previously applied, without the need to open the filter and toggle the quality/performance mode.

Steps to Reproduce the Bug

  1. Add video capture device
  2. Add a Source Mirror source
  3. Add the virtual green screen effect to that source mirror, set it to "quality" mode. Behaviour as expected.
  4. Close OBS and reopen it.
  5. The source mirror greenscreen filter is present in the filter list and enabled but doesn't actually apply the greenscreen effect until you go into the filter and toggle the dropdown value to performance, then it becomes re-enabled.

Any additional Information we need to know?

No response

@adjstreams adjstreams added status:help-wanted bug Bugs such as crashing, freezing, broken functionality, etc. labels Jan 1, 2022
@adjstreams adjstreams changed the title OBS Source Mirropr + Green Screen filter doesn't remember setting Source Mirror + Green Screen filter doesn't remember setting Jan 1, 2022
@austins

This comment was marked as off-topic.

@Xaymar
Copy link
Owner

Xaymar commented Jan 4, 2022

Confirmed

Problem is not tied to Source Mirror, but any source that can have 0x0 as resolution when it is created.

@Xaymar Xaymar changed the title Source Mirror + Green Screen filter doesn't remember setting Virtual Greenscreen filter does not initialize if Source is 0x0 Jan 4, 2022
@coelhoricardo
Copy link

Hi, is there any known workaround ?

@spectangulation
Copy link

Hi, is there any known workaround ?

set it to performance and then back to quality.

confirming i have this issue too.

@inconsx

This comment was marked as off-topic.

@skeletonbow

This comment was marked as off-topic.

@OsiMood

This comment was marked as off-topic.

@HunterAP23

This comment was marked as off-topic.

@Xaymar
Copy link
Owner

Xaymar commented Feb 20, 2022

Please do not flood the message thread with "I have this issue too". If you have the same issue, just react with a 👍.

@Xaymar Xaymar self-assigned this Feb 20, 2022
@Xaymar Xaymar added this to the 1.0 milestone Feb 20, 2022
@EliottGaboreau
Copy link

In case this helps, when running obs from a shell I get this error message :

Caught exception: cudaErrorInvalidPitchValue: cudaMemcpy2DFromArrayAsync(...)

@Xaymar Xaymar removed this from the 1.0 milestone Jul 31, 2022
@Xaymar Xaymar added this to the v0.13 milestone May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bugs such as crashing, freezing, broken functionality, etc.
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

10 participants