You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Camera API grabs software frames, but it's possible to get 0-copy textures instead. Which is faster if you only want to render the frames.
So that return value is a 0-copy texture for the SDL_Renderer.
( some example to use 0-copy textures with cameras: #8565
testffmpeg.c also shows 0-copy textures creations and update. )
The text was updated successfully, but these errors were encountered:
I would probably return properties that can be used to create a texture or interop with some other display mechanism, rather than tie it directly to an SDL renderer.
Currently the Camera API grabs software frames, but it's possible to get 0-copy textures instead. Which is faster if you only want to render the frames.
suggestion is to add:
So that return value is a 0-copy texture for the SDL_Renderer.
( some example to use 0-copy textures with cameras: #8565
testffmpeg.c also shows 0-copy textures creations and update. )
The text was updated successfully, but these errors were encountered: