-
-
Notifications
You must be signed in to change notification settings - Fork 526
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
Support AV1 encoding using AMF on Windows #1967
Conversation
I think this PR should be split between AMF headers upgrade and the rest, because the changes are hard to navigate. |
IMO it's not hard to navigate. Why would you split PR if it all related? Unless the headers upgrade is not required for the rest. |
If anything else, i'd like to split the PR because of the "single concern" principle. |
^ it would be much easier to figure out what the issue is if an upgrade of the headers happens to cause issues however unlikely |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed my mind though I would like a warning when a user enables pre-analysis because it incurs a latency penalty... something you generally don't want in a realtime vr driver.
I think the PR can be rebased @barnabwhy |
0155769
to
ae18cf2
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Does AV1 also work on Windows with Nvidia cards? 🤔 |
@MommasLittleHelper Noone contributed that yet |
It seems to be working nicely from my testing with a Quest 3 and RX 7700XT.
There's a couple of changes to settings, namely:
With this I also updated AMF to v1.4.33, which may bring some improvements elsewhere. (It may be worth looking into the "New AVC / HEVC encoder rate control methods" added in v1.4.28)