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

[Feature Request] In the list of codecs, mark those that currently support hardware acceleration #1287

Open
Korb opened this issue Mar 12, 2024 · 0 comments
Assignees
Labels
🔷Enhancement Type • Improvements for the software. ⬜ Pending Status • This issue stills needs to be analyzed.

Comments

@Korb
Copy link

Korb commented Mar 12, 2024

At the moment, it is impossible to understand which of the codecs offered by the video saving application is supported by hardware on the current device and which is not supported. I have Nvidia GeForce RTX 3070 Ti, GeForce Game Ready Driver 551.76 WHQL (2024.3.5), Microsoft Windows 10.0.19045.4123 installed, and I assume that some of the codecs can be used with a significant performance increase compared to others.

Controls the usage of dedicated hardware (video graphics).
Off: Doesn't use dedicated hardware.
On: Uses dedicated hardware and lets you select special encoders.
Auto: Uses dedicated hardware and automatic selects the right encoder, when possible.

I set the "Hardware Acceleration" variable to "On", but no matter what I select in the "Codec" drop-down list, when saving to mkv, it does not cause a significant increase in speed. In the process manager, the CPU and GPU load is minimal.

I imagine that indicating hardware-supported codecs will save users many hours of time waiting for long recordings to be saved.

@Korb Korb added ⬜ Pending Status • This issue stills needs to be analyzed. 🔷Enhancement Type • Improvements for the software. labels Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔷Enhancement Type • Improvements for the software. ⬜ Pending Status • This issue stills needs to be analyzed.
Projects
None yet
Development

No branches or pull requests

2 participants