<div dir="auto"><div><br><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">вт, 12 нояб. 2024 г., 00:31 Terje J. Hanssen <<a href="mailto:terjejhanssen@gmail.com">terjejhanssen@gmail.com</a>>:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><u></u>
<div>
<br>
<br>
<br>
<div>Den 11.11.2024 22:20, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">пн, 11 нояб. 2024 г.,
23:43 Terje J. Hanssen <<a href="mailto:terjejhanssen@gmail.com" target="_blank" rel="noreferrer">terjejhanssen@gmail.com</a>>:<br>
</div>
<div dir="ltr" class="gmail_attr"><br>
</div>
<div dir="ltr" class="gmail_attr">{snip}</div>
<div dir="ltr" class="gmail_attr"><br>
</div>
<div dir="ltr" class="gmail_attr"><br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> <br>
<blockquote type="cite">
<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>
<blockquote type="cite">
<div dir="auto">
<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>
<blockquote type="cite">.<br>
</blockquote>
<br>
<br>
hevc_qsv.mp4 revised:<br>
pixel formats p010le and y210le
render again to yuv420p10le and
.yuv422p10le respectively<br>
Woops; only when these window
lines are commented out as written
in my previous post !<br>
<blockquote><font face="Courier New, Courier, monospace"># profile=main</font><br>
<font face="Courier New, Courier, monospace"> # cin_pix_fmt=nv12</font><br>
</blockquote>
Works both with and without <br>
export CIN_10BIT_ENC=1<br>
before cin/bin<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">we most likely will need
new profiles for 10bit everything anyway
...</div>
<div dir="auto"><br>
</div>
<div dir="auto">thanks for continued (and
very exhaustive!) testing <br>
</div>
</div>
</blockquote>
<br>
Also the preset's combination of pixel formats
and the right (ffmpeg) codec profiles would
need an overhaul. <br>
<br>
As mentioned already above:<br>
<br>
hevc_qsv.mp4 revised:<br>
pixel formats p010le and y210le render again
to yuv420p10le and .yuv422p10le respectively<br>
Woops; only when these window lines are
commented out as written in my previous post !<br>
<blockquote> <font face="Courier New, Courier, monospace">#
profile=main</font><br>
<font face="Courier New, Courier, monospace">
# cin_pix_fmt=nv12</font><br>
</blockquote>
<br>
I experimented additional and got<br>
<br>
y210/profile=1 ==> yuv422p10le<br>
<br>
y210/ profile=main10/ profile=2/ profile=3
==> yuv420p10le<br>
<br>
I got similar results with my own dynamic
Cingg built with ffmpeg 7.1.<br>
<br>
--------------------------<br>
<br>
So a question beside:<br>
<br>
Yesterday I did a new (monthly) upgrade of
Tumbleweed-Slowroll, which replaced Packman
package libs and ffmpeg 7.1<br>
<br>
After that, the static Cingg with onevpl and
10bit patch would not render hevc_qsv.<br>
<br>
Today's upgrade with new Packman packages
up-to-date with the new Slowroll version, and
now Cingg worked as before:<br>
<br>
ffmpeg-7 ffmpeg-7-libavcodec-devel
ffmpeg-7-libavdevice-devel
ffmpeg-7-libavfilter-devel<br>
ffmpeg-7-libavformat-devel
ffmpeg-7-libavutil-devel
ffmpeg-7-libpostproc-devel
ffmpeg-7-libswresample-devel<br>
ffmpeg-7-libswscale-devel libavcodec61
libavdevice61 libavfilter10 libavformat61
libavutil59 libpostproc58<br>
libswresample5 libswscale8<br>
<br>
So even Cingg with onevpl is static built, it
looks like it is dependent of one or more
system packages/libs beside?<br>
Any idea what packages it can be ?<br>
</div>
</blockquote>
<div><br>
</div>
<div><br>
</div>
<div>onevpl/vaapi/vdpau - they all linked
dynamically (not sure if static version of them
even possible)<br>
</div>
</div>
</div>
</blockquote>
<br>
Ah, I see.<br>
<br>
I tried to compare the two configure lines for my full
dynamic Cingg/ffmpeg7.1 built and static-dynamic
Cingg/ffmpeg7.0 respectively:<br>
<br>
./configure --with-single-user --disable-static-build
--without-thirdparty --without-libdpx<br>
./configure --with-single-user --with-onevpl<br>
<br>
As the first line didn't mention "vpl" I searched
backwards and got the understanding that the source code
was patched to use the system libvpl.<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">not exactly, in first case it just uses libav*
from system ffmpeg package... and this in your case uses
libvpl.</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div> In the second case the build-system itself was
patched with onevpl (default off) to use the same system
libvpl, I assume?<br>
<br>
Is/will possibly the current or upcoming Cingg
appimage/rpm available with the onevpl patch, so it can
be switched on and tested on other available hardware?<br>
</div>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">I was about to ask if onevpl patch can be added
to git ...</div>
<div dir="auto"><br>
</div>
<div dir="auto">Dear Phyllis, can you add onevpl.patch so future
QSV testing will be easier (it defaults to off so should not
break anything ... by default).</div>
<div dir="auto"><br>
</div>
<div dir="auto">while there, Terje, can you pack your latest
profile work and send it separately? I think we use
codec_encoder_additional_params.container as format</div>
<div dir="auto"><br>
</div>
<div dir="auto">so 10bit 420 hevc qsv for mp4 will look like</div>
<div dir="auto"><br>
</div>
<div dir="auto">hevc_qsv_10bit.mp4</div>
<div dir="auto"><br>
</div>
<div dir="auto">with content you experimentally determinated.</div>
<div dir="auto"><br>
</div>
<div dir="auto">and y210 probably will be named</div>
<div dir="auto"><br>
</div>
<div dir="auto">hevc_qsv_y210.mp4</div>
<div dir="auto"><br>
</div>
</div>
</blockquote>
<br>
What about <br>
<br>
hevc_qsv_10bit-420.mp4<br>
<br>
and<br>
<br>
hevc_qsv_10bit-422.mp4<br>
<br>
respectively?<br></div></blockquote></div></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto">if those relative long names fit their box - then ok ...</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><blockquote type="cite"><div dir="auto"><div dir="auto"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br><br></div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</div>
</blockquote></div></div></div>