-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Fix rate control for AMD cards using VAAPI #2821
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #2821 +/- ##
======================================
Coverage 8.98% 8.99%
======================================
Files 95 95
Lines 17304 17310 +6
Branches 8232 8234 +2
======================================
+ Hits 1555 1557 +2
- Misses 12884 12888 +4
Partials 2865 2865
Flags with carried forward coverage won't be shown. Click here to find out more.
|
e8f6f7c
to
e2c27c2
Compare
Great to see this merged so quickly! Looking forward to the next release. 😊 |
I was getting the "Number of fragments for reed solomon exceeds DATA_SHARDS_MAX" error previously but not with this fix. It has made a nice performance improvement, particularly when using HDR. |
Description
Intel needs RC buffer size unset for their H.264 encoder to avoid horrible encoding quality, however this causes issues for AMD cards overshooting the expected maximum frame size and causing packet loss. Resolve this by adding a new hook in
avcodec_encode_device_t
to allow the platform encoding code to set additional options on the codec context and using the vendor string to distinguish Intel cards.Screenshot
Issues Fixed or Closed
Fixes #2788
Type of Change
.github/...
)Checklist
Branch Updates
LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.