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

Apply video filters in shaders instead of the CPU #254

Open
lukexor opened this issue May 29, 2024 · 0 comments
Open

Apply video filters in shaders instead of the CPU #254

lukexor opened this issue May 29, 2024 · 0 comments
Labels
enhancement New feature or request tetanes

Comments

@lukexor
Copy link
Owner

lukexor commented May 29, 2024

Currently video filters are done in the CPU and consume a few percent of the overall CPU usage during runtime. Moving these to shaders would be faster and open up additional "off the shelf" filtering options

There is a caveat though that this would cause a split in implementation as tetanes-core does not concern itself with shader implementations.

tetanes would instead rely on the ControlDeck::frame_buffer_raw method instead of ControlDeck::frame_buffer in order to provide the shader with the data to process.

@lukexor lukexor added the enhancement New feature or request label May 29, 2024
@lukexor lukexor self-assigned this May 29, 2024
@lukexor lukexor added the tetanes-core Change related to tetanes-core label May 29, 2024
@lukexor lukexor removed their assignment May 29, 2024
@lukexor lukexor changed the title Apply video filters in shaders instead of on the CPU Apply video filters in shaders instead of othe CPU Jun 12, 2024
@lukexor lukexor changed the title Apply video filters in shaders instead of othe CPU Apply video filters in shaders instead of the CPU Jun 12, 2024
@lukexor lukexor removed the tetanes-core Change related to tetanes-core label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request tetanes
Projects
None yet
Development

No branches or pull requests

1 participant