From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: gst-plugins-bad1: enable 'va' plugin
Date: Fri, 21 Jul 2023 03:49:41 +0200 [thread overview]
Message-ID: <20230721014941.lwXAqHg6zj8KXjqOMVMqflv0Nk5_PKO11dxdBnRKMDE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45133@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]
There's a merged pull request on the void-packages repository
gst-plugins-bad1: enable 'va' plugin
https://github.com/void-linux/void-packages/pull/45133
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc
---
```
17:55:12 $ gst-inspect-1.0 va
Plugin Details:
Name va
Description VA-API codecs plugin
Filename /usr/lib/gstreamer-1.0/libgstva.so
Version 1.22.2
License LGPL
Source module gst-plugins-bad
Documentation https://gstreamer.freedesktop.org/documentation/va/
Source release date 2023-04-11
Binary package GStreamer Bad Plug-ins source release
Origin URL https://voidlinux.org
vacompositor: VA-API Video Compositor
vadeinterlace: VA-API Deinterlacer
vah264dec: VA-API H.264 Decoder
vah264enc: VA-API H.264 Encoder
vah265dec: VA-API H.265 Decoder
vah265enc: VA-API H.265 Encoder
vajpegdec: VA-API JPEG Decoder
vampeg2dec: VA-API Mpeg2 Decoder
vapostproc: VA-API Video Postprocessor
vavp9dec: VA-API VP9 Decoder
10 features:
+-- 10 elements
```
and I have successfully used it to encoded a video on my amd gpu
prev parent reply other threads:[~2023-07-21 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 15:32 [PR PATCH] " dmarto
2023-07-21 1:49 ` Duncaen [this message]
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=20230721014941.lwXAqHg6zj8KXjqOMVMqflv0Nk5_PKO11dxdBnRKMDE@z \
--to=duncaen@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).