<!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 14.11.2024 18:38, skrev Andrew
Randrianasulu:<br>
</div>
<blockquote type="cite"
cite="mid:CA+rFky51sAUz3Z+822RV0L2U3iRC5a4cJ_fiAQOXMTDQ-7rvkg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">
<div><br>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">чт, 14 нояб. 2024 г.,
20:27 Terje J. Hanssen <<a
href="mailto:terjejhanssen@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">terjejhanssen@gmail.com</a>>:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Thank
you for the patch.<br>
<br>
A few clarification questions in between before I start:<br>
<br>
Den 14.11.2024 14:21, skrev Andrew Randrianasulu:<br>
<br>
> you need to reset your git tree,<br>
><br>
> something like<br>
><br>
> git reset
--hard 2037bf63cdf25462ca606f4a28636e12df77c2a0<br>
<br>
I did use "git reset --hard" without number at the end for
the previous <br>
patch<br>
<br>
What number here, should I find mine somewhere in my git
tree?<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">you can fig them in 'git log' screen, you should
have two more patches on top of "ORIGIN" line <br>
</div>
</div>
</blockquote>
<br>
Sorry, I'm still a bit confused by the latter "you should have two
more patches on top of "ORIGIN" line"<br>
Here is the top from my git log" output:<br>
<br>
<blockquote>commit 68eb98be2183738684f1f4da2729d1ff9989ad16<br>
Author: Andrew Randrianasulu <a class="moz-txt-link-rfc2396E" href="mailto:randrianasulu@gmail.com"><randrianasulu@gmail.com></a><br>
Date: Sun Oct 27 19:43:06 2024 +0300<br>
<br>
Experimental: try 10bit vaapi encoding<br>
<br>
commit e5a5a6da907dbcd40d8612bdbfeea1a2a0ae6cc8<br>
Author: Andrew Randrianasulu <a class="moz-txt-link-rfc2396E" href="mailto:randrianasulu@gmail.com"><randrianasulu@gmail.com></a><br>
Date: Fri Oct 18 10:07:33 2024 +0300<br>
<br>
Add onevpl support to build system<br>
<br>
commit 8681d13675f32e870ab3632eaf89105415fb3961<br>
Author: Andrew Randrianasulu <a class="moz-txt-link-rfc2396E" href="mailto:randrianasulu@gmail.com"><randrianasulu@gmail.com></a><br>
Date: Wed Oct 23 16:36:19 2024 +0300<br>
<br>
Add DESCRIPTION<br>
<br>
commit 90138debee46e0b91adeb5d8a400158b131b0d61<br>
Author: Andrew Randrianasulu <a class="moz-txt-link-rfc2396E" href="mailto:randrianasulu@gmail.com"><randrianasulu@gmail.com></a><br>
Date: Wed Oct 23 16:29:58 2024 +0300<br>
<br>
Add BUGS<br>
<br>
commit 318c884532617e32904d6f4ec05a2b73832f418e<br>
Author: Andrew Randrianasulu <a class="moz-txt-link-rfc2396E" href="mailto:randrianasulu@gmail.com"><randrianasulu@gmail.com></a><br>
Date: Wed Oct 23 16:22:58 2024 +0300<br>
<br>
Update README build instructions<br>
<br>
</blockquote>
<br>
<br>
<br>
<blockquote type="cite"
cite="mid:CA+rFky51sAUz3Z+822RV0L2U3iRC5a4cJ_fiAQOXMTDQ-7rvkg@mail.gmail.com">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto">you can do</div>
<div dir="auto"><br>
</div>
<div dir="auto">git pull -r </div>
<div dir="auto"><br>
</div>
<div dir="auto">first, it will rebase two patches on top of what
currently in git repo.</div>
<div dir="auto"><br>
</div>
<div dir="auto">then you can use 'git log' to look up those
'commit hashes'. In theory they should be unique, so one I
already provided should work *after rebase* (git pull -r).
Without rebase commits and objects from remote repo do not
exist yet in your local repo <br>
</div>
</div>
</blockquote>
<blockquote type="cite"
cite="mid:CA+rFky51sAUz3Z+822RV0L2U3iRC5a4cJ_fiAQOXMTDQ-7rvkg@mail.gmail.com">
<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">
<br>
><br>
> before applying this patch<br>
><br>
> then run cin like<br>
><br>
> CIN_10BIT_ENC=p010le bin/cin<br>
<br>
No export as before before bin/cin ?<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">you can do export on separate line, but then if
you want to undo its effect you should unset this variable, or
close and reopen terminal window.</div>
<div dir="auto"><br>
</div>
<div dir="auto">I think same-line invocation is easier </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">
><br>
> or replace p010le with whatever equivalents y210le
(?)<br>
<br>
So need to restart Cingg again before using next vaapi
format?<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">for this patch - yes.</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">
><br>
> sorry, I just hanged my X session so can't copy/paste
exact output, <br>
> but if you launch cingg with<br>
><br>
> error=debug in bin/ffmpeg/encode.opts it will print
list of accepted <br>
> by vaapi library formats at encoding attempt.<br>
<br>
Something I have seen and wondered about:<br>
<br>
Is "debug" and "verbose" the same or different ffmpeg
output(s)?<br>
</blockquote>
</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">I think they different, but how much depend on
ffmpeg's code that runs at those moments. For example if you
run vaapi encode than all carefully added logging functions in
qsv encoder will be of no use ....</div>
<div dir="auto"><br>
</div>
</div>
</blockquote>
<blockquote type="cite"
cite="mid:CA+rFky51sAUz3Z+822RV0L2U3iRC5a4cJ_fiAQOXMTDQ-7rvkg@mail.gmail.com">
<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">
<br>
><br>
> I think this is still more like prototype to see if
we can get it <br>
> working, I hope to wire it to existing profile
reading mechanism.<br>
<br>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>