-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
AMD VCE encoders add green/black bars and/or work with wrong aspect ratio #5952
Comments
AMD AV1 encoder has a severe limitation, it can only works with widths and heights divisible by 64 (or 32?) if I remember correctly. However it should happen with AMD H.264 or AMD H.265. |
Interesting, but then I'd expect to see those bars when using amd codec acceleration in other apps, such as screen recording through ShareX (with random region size every time!), or adrenalin screen recording? |
It affects all apps being a hardware limitation. Most screen resolutions won't be affected as they are usually divisible by 64 so not that surprising. Looking at your encode, you might want to drop the cropping down to 0. I do wonder if that's a false positive crop detection. That would bring the resolution up. |
As I said, settings do not matter. Also, I did say that recordings were with random region sizes, so the chances to hit n*64/32 every time is zero. |
If this is the issue your seeing, then your sod outa luck. AMD confirmed it was a problem on their end so in all likelihood we'll see it sorted with RNDA 5 However, are you able to share with us a sample file, I can run it here just in-case there is something more going on |
The live preview inside HandBrake doesn't seem to align the video properly sometimes, but I can't reproduce the issue when playing the encoded file in a separate app. I can't test AV1. |
on Windows? That's just an instance of the Windows media player. (Not entirely sure if it's using the legacy or modern API for it but it should then be reproducible in the native app) The Media Player app, or WMP can be tried separately to confirm There is an option to use external media player for when compatibility issues occur as I can't do anything about it if they misbehave since it's just an overlay control they provide us. |
Just checking in if there is a sample you can share. if not, I don't think there is any further action we can take here. |
Problem Description
I've spent past 2 hours trying to simply convert old .wmv files to av1, and always ended up having a green bar on the right side of video. Sometimes it was black, depending on Dimensions tab.
I've noticed that no matter the settings, the bar was there, and video is squished to the left.
It happened on amd x264, amd x265 and amd AV1.
However, simply switching to non-AMD version of a codec - simply x264, x265 or AV1 SVT - problem is gone. Video transcodes with identical size as the input, with no extra bars created anywhere.
Settings are not changed anywhere except for the codec. Here are those anyway:
No matter how set up. Automatic, none, disabled, custom...
Video preview without anything (Yes, it's blurred, for SFW reasons).
Preview with AMD AV1 ecoding. Same result with AMD x264 and AMD HEVC. Notice green bar on right. Video itself is squished to the left, and also notice bars on top and bottom - those seem to be from the 'original' preview - like video has been cropped/squished vertically also. Possibly auto-crop, but nonetheless it does not happen in non-AMD encoder.
Preview with non-AMD encoder - AV1 SVT. It will also be like this (proper, without bars and resizes) with x264 and hevc.
Also please note that I've noticed this happening months ago as well, but thought it's caused by Topaz Video AI, because it was happening on other videos as well.
Activity Log, Crash Log or any other details
AMD AV1 activity log
AV1 SVT activity log
What Operating System are you running?
Windows 11 23H2 22631.3296 (was also like this on W10)
What version of HandBrake are you running?
1.7.3 (2024021000)
Where did you download HandBrake from?
winget, github
The text was updated successfully, but these errors were encountered: