-
Notifications
You must be signed in to change notification settings - Fork 283
feat: use gpu texture in screen consumer #1651
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
base: master
Are you sure you want to change the base?
feat: use gpu texture in screen consumer #1651
Conversation
Doesn't work on Linux as is, because on linux we use different opengl "wrappers" in the accelerator and screen consumer. @Julusian, why do we have a separate context (using EGL) on Linux? I'm guessing there is a reason... |
That was a recent change to support environments where X11 is not available #1624 But maybe that can be reshuffled to choose at runtime based on whether it is found to be available rather than being hardcoded this way. |
Yea, I just had a look in the commit history and realized I should have looked there before asking :) A runtime check sounds like the correct fix. I'll have a go at that... |
39af23c
to
89c130b
Compare
I think this works now. I'm on vacation and haven't got access to my linux workstation. It runs fine(ish) in WSL, and selects context implementation based on the presens of a DISPLAY env var. The screen consumer actually works in WSL now, with the sfml context. ...when using the EGL context it crashes in WSL, but that is not specific to this PR. |
There seems to be some issues with this still. Marking as “draft” until I’ve sorted it out |
89c130b
to
a63ac5f
Compare
@niklaspandersson what issues were you having? |
My client had issues with glitching when he used this together with ndi- and decklink producers. I haven't been able to reproduce, but I've seen a video. I just noticed that I was missing a fence to protect the gpu textures while rendering. I'll have him try it again now... |
Uh oh!
There was an error while loading. Please reload this page.