-
Notifications
You must be signed in to change notification settings - Fork 147
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
Video Encode API: Unable to set Two Pass Encoding #2
Comments
I have been stepping through the amfrt32 and amfrt64 library for a bit now and only discovered strings related to HEVC, not Two Pass or SinglePass encoding. I will continue looking until there is an official update. |
An update on this would be nice. I assume the 2-pass is also for H264, not just H265? |
Two Pass encoding is really needed to provide better quality than what you currently get in dark scenes. I don't know why but AMF uses a bitrate way too low for dark areas - similar to x264 superfast behaviour. |
Any word on this? HEVC and 2-pass support were big reasons I went with a polaris GPU instead of going Nvidia. It's disappointing that these advertised features are still not supported. Developers out there are sat twiddling their thumbs waiting for SDK support to implement it in their apps :( |
16.10.3 seems to be the first driver that has new parameters available, including one that referse to a Preanalysis. Is it really going to happen, Pre-Pass/"Two"-Pass encoding before christmas? |
@Xaymar Maybe they will add it in the ''annual'' driver this year...a.k.a Omega / Crimson / Whats next? |
...Should I be saving for a Geforce 1050? The advertised features are supported before the card was even released. :/ |
It will most likely be in the next non-hotfix driver. Also you can already use it, my plugin already offers a way to enable the flag for it. |
There currently seems to be no way to tell AMF/VCE which encoding type should be used. It is either missing from the include files or not properly documented. I may have missed it though.
The text was updated successfully, but these errors were encountered: