From: github-actions [bot] <"github-actions [bot]"@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: nv-codec-header: update to 12.0.16.1.
Date: Thu, 23 May 2024 03:46:33 +0200 [thread overview]
Message-ID: <20240523014633.AE80A21147@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-44781@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]
There's a closed pull request on the void-packages repository
nv-codec-header: update to 12.0.16.1.
https://github.com/void-linux/void-packages/pull/44781
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
I've build ffmpeg successfully with this version and also tested streaming with the codec via obs studio with my Nvidia Geforce RTX 2080 Super.
#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- x86_64-musl
- aarch64-musl (crossbuild)
- armv7l (crossbuild)
- armv6l-musl (crossbuild)
We could also update to 12.1.x but this versions are no longer compatible with ffmpeg 4.4.4.
That's why for the moment I would update only to 12.0.16.1. This versions builds successfully with all packages that rely on it.
The new version would no longer allow users of nvidia470 to use the package. But 12.x brings so many relevant features for last and current generations of Nvidia graphics cards that this shouldn't be an argument.
prev parent reply other threads:[~2024-05-23 1:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 8:56 [PR PATCH] nv-codec-header: update to 12.0.16.0 dataCobra
2023-07-05 14:32 ` [PR PATCH] [Updated] " void-linux
2023-07-10 7:49 ` dataCobra
2023-07-10 18:04 ` dataCobra
2023-07-10 18:11 ` dataCobra
2023-07-15 8:37 ` dataCobra
2023-07-16 9:16 ` dataCobra
2023-07-21 5:15 ` dataCobra
2023-07-24 6:36 ` dataCobra
2023-10-05 15:42 ` dataCobra
2023-10-17 0:07 ` tm512
2023-10-17 12:00 ` dataCobra
2023-10-17 12:08 ` [PR PATCH] [Updated] " dataCobra
2023-10-17 20:55 ` nv-codec-header: update to 12.1.14.0 tm512
2023-11-08 14:15 ` [PR PATCH] [Updated] " dataCobra
2023-11-08 14:18 ` [PR PATCH] [Updated] nv-codec-header: update to 12.0.16.1 dataCobra
2024-02-07 1:44 ` github-actions
2024-02-07 14:09 ` [PR PATCH] [Updated] " dataCobra
2024-05-09 1:46 ` github-actions
2024-05-23 1:46 ` github-actions [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=20240523014633.AE80A21147@inbox.vuxu.org \
--to=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).