-
Notifications
You must be signed in to change notification settings - Fork 5
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
Bump gstly and verify hw-accelerated video decoding #170
Comments
The Snap currently isn't expected to work with VA-API or NVCODEC unfortunately, but I wouldn't let that block this task. We just need to make sure bumping Gstly doesn't break anything for the Snap. |
The pyinstaller bash script for linux should def have the environment variable added though. Or maybe instead of putting it in the bash script, the client could set these variables itself? I'm not sure the best way to handle that. In Windows, the executable is launched directly. |
Potentially. I'm not sure if Python will be able to set these environment variables in such a way that GStreamer will see them. If not, we can always provide a way in Gstly to set these values programmatically as well.
True, although in the short term this may not matter because we don't support hardware acceleration on Windows yet. |
The new version of gstly supports hardware accelerated video decoding. Let's bump gstly and test adding the following environment variables to our snap/pyinstaller builds:
Let's also see what happens on the windows build. Does msys's gstreamer include nvcodec?
The text was updated successfully, but these errors were encountered: