aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authordec05eba <dec05eba@protonmail.com>2024-01-21 21:29:34 +0100
committerdec05eba <dec05eba@protonmail.com>2024-01-21 21:29:34 +0100
commitbbf509caf2dbf355ebc3d68ecc1b84e7669f195f (patch)
treed14cb30bf1fb939506f3e35a4bac6ef9316548d8 /README.md
parent496e00e947bd37c5eed6e9d96950bd06722278f7 (diff)
Readme black bars
Diffstat (limited to 'README.md')
-rw-r--r--README.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/README.md b/README.md
index 1f47948..4f117b2 100644
--- a/README.md
+++ b/README.md
@@ -143,6 +143,9 @@ It seems like ffmpeg earlier than version 6.1 has some type of bug. Install ffmp
Browsers and discord don't support hevc video codec at the moment. Choose h264 video codec instead with the -k h264 option.
Note that websites such as youtube support hevc so there is no need to choose h264 video codec if you intend to upload the video to youtube or if you want to play the video locally or if you intend to
edit the video with a video editor. Hevc allows for better video quality (especially at lower file sizes) so hevc (or av1) is recommended for source videos.
+## I get a black bar on the right/bottom in the video
+This is mostly an issue on AMD and it's a hardware issue/ffmpeg issue. If you use HEVC video codec then it's an issue in ffmpeg and if you use AV1 then it's an issue in the video encoding unit on certain AMD gpus, see: https://gitlab.freedesktop.org/mesa/mesa/-/issues/9185.
+If you get black bars then the workaround is to record with h264 video codec instead (using the -k h264 option).
# Donations
If you want to donate you can donate via bitcoin or monero.