-
-
Notifications
You must be signed in to change notification settings - Fork 177
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
don't copy pixmap data to ram: avoid the round-trips and stay on the GPU if we can #365
Comments
Here's how I think this can work.
Obviously, we'll also need fallback code for dealing with non-nvenc encoders, and lots of other little details I can't foresee.. Links: |
Another API we could potentially use (maybe just on win32?) is Although DRC seems to think it's not worth it: |
For win32 we now have an API we can use #1317 "nvidia capture sdk support" |
See #1552 comment 1. |
Boom! Done for NVFBC (#1317) + NVENC v8 (#1552) in r16458! Still TODO:
|
Will follow up in #1597. Closing at last! |
Also done for Linux in r16492: needed new NVENC kernels as Linux uses a different pixel format (XRGB vs BGRX). |
Regression: #1763 |
EXT_texture_from_pixmap should allow us to use the pixels on the GPU for doing CSC and/or encoding without first needing to copy them to RAM (via
XShmGetImage
orXGetImage
as we do now)[[BR]]
XShmGetImage
is pretty fast but then we have to upload the data again to the graphics card (assuming we do csc on the GPU - which is the fastest option) and then download the results. Quite wasteful, especially at high res.The text was updated successfully, but these errors were encountered: