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

Flowblade won't utilise the full GPU for rendering #1177

Open
Disaster2life opened this issue Jan 20, 2025 · 1 comment
Open

Flowblade won't utilise the full GPU for rendering #1177

Disaster2life opened this issue Jan 20, 2025 · 1 comment

Comments

@Disaster2life
Copy link
Contributor

Finally got some time to work on something, and GPU acceleration seems to be "minimal", I know the Position Scale (and somewhat less so but still) Position Scale Rotate filter rely heavily on the CPU, and my timeline mostly consisted of the Position Scale Rotate and Crop filters, so I thought to mention how little the GPU is utilised for rendering that, heres a screenshot I took from intel_gpu_top

Image

@jliljebl
Copy link
Owner

Position Scale Rotate filter rely heavily on the CPU, and my timeline mostly consisted of the Position Scale Rotate and Crop filters, so I thought to mention how little the GPU is utilised for rendering that, heres a screenshot I took from intel_gpu_top

The current GPU filters offered by MLT are based on QT, and QT filters start QT main loop and haven't ever worked with Flowblade.

We will start working on this this year, probably first sessions coming next month. The current state of application is such that the biggest benefits for user will come from addressing this exact point, transferring as much as possible of work to GPU.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants