Github messages for voidlinux
 help / color / mirror / Atom feed
From: ja-cop <ja-cop@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Intel packages
Date: Thu, 27 Apr 2023 19:45:41 +0200	[thread overview]
Message-ID: <20230427174541.M9c8cesHVOZi2ybsIItrLN_bszp_ByMHCjzZM54Fbjk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41132@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1792 bytes --]

New comment by ja-cop on void-packages repository

https://github.com/void-linux/void-packages/pull/41132#issuecomment-1526091256

Comment:
I tested these packages with an Intel Arc A770 with Linux 6.1.25_1, and I think I managed to get hardware accelerated video decoding working like so:
```bash
ffmpeg -hwaccel qsv -hwaccel_device /dev/dri/renderD128 -i Sprite\ Fright.mp4 \
-vcodec rawvideo -acodec copy -f matroska - | ffplay -i -
```
This works for H264, H265 and AV1 input videos. Nice! I'm not 100% sure it's not quietly falling back to software decoding, though - not sure how to reliably check. Verbose output doesn't indicate that it does.

If I replace `qsv` with `vaapi`, I get error spam:
```
Error while decoding stream #0:0: Input/output error
[h264 @ 0x562d81ba0880] Failed to end picture decode issue: 23 (internal decoding error).
[h264 @ 0x562d81ba0880] hardware accelerator failed to decode picture
```
Same errors for decoding h265 video. When passed an AV1 video, it "works", but it looks like it's falling back to the `libdav1d` software decoder without explaining why.

I haven't been able to get hardware decoding in mpv working - it looks like it doesn't support QSV, only VAAPI, at least on Linux? With `mpv --hwdec=vaapi`, it gives the same error as ffmpeg above.

---

As for encoding, I think I got h264 encoding working with `-hwaccel qsv`, wasn't able to find the right parameters for h265 encode, and the AV1 encoder doesn't even show up in `ffmpeg -encoders`. I'm looking to try out [this PR for OBS](https://github.com/obsproject/obs-studio/pull/8327) to see if I can get AV1 encoding working directly from OBS without going through ffmpeg.

---

Thanks for packaging these, looking forward to getting the most out of the A770 soon!

  parent reply	other threads:[~2023-04-27 17:45 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16 14:40 [PR PATCH] [WIP] " zlice
2022-12-16 14:43 ` [PR PATCH] [Updated] " zlice
2022-12-16 14:45 ` zlice
2022-12-16 16:33 ` zlice
2022-12-16 17:27 ` zlice
2022-12-16 17:33 ` zlice
2022-12-16 18:11 ` zlice
2022-12-16 19:03 ` zlice
2022-12-16 21:37 ` zlice
2022-12-16 22:28 ` zlice
2022-12-18  5:29 ` [PR PATCH] [Updated] " zlice
2022-12-18  6:19 ` zlice
2022-12-18  6:25 ` zlice
2022-12-18  6:49 ` [PR PATCH] [Updated] " zlice
2022-12-18 11:31 ` classabbyamp
2022-12-18 15:41 ` [PR PATCH] [Updated] " zlice
2022-12-18 19:47 ` zlice
2022-12-19  3:02 ` zlice
2022-12-19  3:02 ` zlice
2022-12-20 15:10 ` zlice
2023-01-14  4:09 ` [PR PATCH] [Updated] " zlice
2023-01-14  4:15 ` zlice
2023-01-20 14:10 ` [PR PATCH] [Updated] " zlice
2023-01-20 15:48 ` icp1994
2023-01-20 16:00 ` zlice
2023-01-20 16:02 ` icp1994
2023-01-20 16:04 ` zlice
2023-01-25 11:29 ` Anachron
2023-01-25 12:50 ` icp1994
2023-01-26 11:05 ` Anachron
2023-02-08  9:08 ` Anachron
2023-02-08  9:10 ` Anachron
2023-02-08  9:11 ` Anachron
2023-02-08 12:25 ` zlice
2023-02-08 14:15 ` [PR PATCH] [Updated] " zlice
2023-02-08 14:21 ` zlice
2023-02-08 15:34 ` zlice
2023-02-08 15:54 ` zlice
2023-02-08 15:55 ` [PR PATCH] [Updated] " zlice
2023-02-08 15:57 ` zlice
2023-02-10  7:18 ` icp1994
2023-02-10  7:20 ` icp1994
2023-03-23 13:32 ` [PR PATCH] [Updated] " zlice
2023-03-23 13:33 ` zlice
2023-04-27 17:45 ` ja-cop [this message]
2023-04-27 18:01 ` zlice
2023-04-27 18:02 ` zlice
2023-04-27 22:10 ` ja-cop
2023-04-27 23:43 ` zlice
2023-04-27 23:54 ` ja-cop
2023-04-28 13:38 ` zlice
2023-04-28 15:56 ` ja-cop
2023-05-05 12:52 ` [PR PATCH] [Updated] " zlice
2023-05-05 12:53 ` zlice
2023-05-22 15:56 ` [PR PATCH] [Updated] " zlice
2023-05-22 15:58 ` zlice
2023-06-19 20:21 ` [PR PATCH] [Updated] " zlice
2023-06-20  6:52 ` Anachron
2023-06-20 10:43 ` zlice
2023-06-22 12:23 ` zlice
2023-06-22 12:23 ` [PR PATCH] [Updated] " zlice
2023-07-04 15:23 ` zlice
2023-07-04 15:24 ` zlice
2023-07-04 17:17 ` Anachron
2023-08-02 14:01 ` [PR PATCH] [Updated] " zlice
2023-11-01  1:46 ` github-actions
2023-11-15  1:46 ` [PR PATCH] [Closed]: " github-actions
2023-11-20 12:54 ` zlice
2024-01-10 22:49 ` mdkcore0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230427174541.M9c8cesHVOZi2ybsIItrLN_bszp_ByMHCjzZM54Fbjk@z \
    --to=ja-cop@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).