<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<br>
<br>
<br>
<div class="moz-cite-prefix">Den 22.12.2024 00:04, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite"
cite="mid:CA+rFky5UQsU7sobxCnb7CaF7=sBRcYhc4KCwPEnM4gNUKLL=LQ@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">вс, 22 дек. 2024 г., 01:53
Phyllis Smith <<a href="mailto:phylsmith2017@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">phylsmith2017@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div style="font-size:small" class="gmail_default">Andrew,<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div dir="auto">most likely our nv headers drifted
from that ffmpeg-7.0/proprietary driver assumes
at runtime.</div>
</div>
</blockquote>
<div><span class="gmail_default"
style="font-size:small">I have been wondering
about nv-codec-headers as we are at:</span></div>
<div><span class="gmail_default"
style="font-size:small"></span> <span
class="gmail_default" style="font-size:small"> </span><a
href="https://github.com/FFmpeg/nv-codec-headers/releases/tag/n10.0.26.0"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/FFmpeg/nv-codec-headers/releases/tag/n10.0.26.0</a></div>
<div>
<div style="font-size:small" class="gmail_default">but
I am unsure about updating to: <br>
</div>
<div style="font-size:small" class="gmail_default">
<a
href="https://github.com/FFmpeg/nv-codec-headers/releases/tag/n12.2.72.0"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/FFmpeg/nv-codec-headers/releases/tag/n12.2.72.0</a></div>
<div style="font-size:small" class="gmail_default">because
if you look at:</div>
<div style="font-size:small" class="gmail_default">
<a
href="https://github.com/FFmpeg/nv-codec-headers/releases/"
target="_blank" rel="noreferrer"
moz-do-not-send="true"
class="moz-txt-link-freetext">https://github.com/FFmpeg/nv-codec-headers/releases/</a></div>
<div style="font-size:small" class="gmail_default">the
release versions go from 12.xx to 8.x and it is
really weird AND there is no year on the release
dates but just day and month.</div>
<div style="font-size:small" class="gmail_default">Since
it is such an important part of ffmpeg inside
CinGG, I am concerned but will at least try the
12.2.72.0 just to see what it does.<br>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">in theory it should give users of new nvidia
hardware av1 encoding ...... but not sure how it will work
with older drivers and hardware.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote gmail_quote_container">
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">you can try to install something
like nv-codec-headers and then add <br>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
Andrew,<br>
As far as there might be a workaround also for the nvenc tff
interlace issue, I didn't do more about the latter than searching
the most similar package<br>
ffnvcodec-devel (FFmpeg version of NVIDIA codec API headers)<br>
<br>
Additional I think an AppImage built successful of my dynamic build
ffmpeg-7.1 with <br>
sh ./bld_appimage.sh bin_use_system_ffmpeg-71<br>
It works on the build-machine, and I will test it on the older
machines too.<br>
<br>
Phyllis,<br>
I was about to send a little comment to your first News version,
regarding relative "new" Intel hardware.<br>
The SkyLake/ KabyLake test machines are from 2015/ 2016 respectively
:)<br>
Of course they have lesser codecs support than the relative new
bult-machine.<br>
<br>
<br>
<br>
<br>
</body>
</html>