From: Kerberoge <Kerberoge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Intel Quick Sync Video broken on Void Linux; no implementations available in the repositories
Date: Tue, 04 Feb 2025 01:37:37 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54208@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1865 bytes --]
New issue by Kerberoge on void-packages repository
https://github.com/void-linux/void-packages/issues/54208
Description:
Intel Quick Sync Video is a marketing name for hardware acceleration features found on Intel integrated GPUs. On Linux, these hardware features can be accessed through two different APIs: [Intel Media SDK](https://github.com/Intel-Media-SDK/MediaSDK) (for older hardware) and the [VPL GPU runtime](https://github.com/intel/vpl-gpu-rt) (for newer hardware) ([source](https://trac.ffmpeg.org/wiki/Hardware/QuickSync#APISupport)). Additionally, there's also [oneVPL](https://github.com/intel/libvpl) (aka libvpl), but this library contains a dispatcher that forwards calls to one of the two libraries. This library cannot provide access to the QSV hardware on its own.
This is also mentioned in the following screenshot, which is taken from the oneVPL Github page:

The problem is that Void Linux provides neither the Intel Media SDK, nor the Intel VPL GPU runtime! Due to this, QSV does not currently function on this distribution. An example of this is ffmpeg, which provides the h264_qsv codec. Attempting to encode a video with this codec results in an error, which says that an MFX session could not be created (libmfx is a library provided by the Intel Media SDK). Interestingly, the repositories do contain a package for oneVPL (the dispatcher library).
In order to make the oneVPL package actually useful, both the Intel Media SDK and the GPU runtime should be added to the Void package repository.
Side note: the Intel Media SDK contains a dispatcher as well. Intel recommends to not use this one, but oneVPL instead. So if the Intel Media SDK ever gets added to the repositories, please disable the included dispatcher to prevent redundancy.
next reply other threads:[~2025-02-04 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 0:37 Kerberoge [this message]
2025-02-04 11:49 ` [ISSUE] [CLOSED] " ahesford
2025-02-04 11:49 ` ahesford
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-54208@inbox.vuxu.org \
--to=kerberoge@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).