<br><br>On Tuesday, July 27, 2021, Andrea paz via Cin <<a href="mailto:cin@lists.cinelerra-gg.org">cin@lists.cinelerra-gg.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I did some tests with the new and old x265. I report some data, while<br>
the terminal output is attached in test-x265.txt.<br>
<br>
I used a 5 min video in h264 4.2.0 but good quality. Size= 471 MB.<br>
<br>
<br>
x265-10bit: CPU 50-80% (multithread) 27.5 fps file size 46 MB<br>
<br>
x265-12bit: CPU 50-80% (multi) 25.5 fps file size 45 MB<br>
<br>
x265-Hi: CPU 80-90% (multi) 10.6 fps file size 1.7 GB<br>
<br></blockquote><div><br></div><div>wow, this one is big! </div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
x265-Lo(w): CPU 40-70% (single/multi) 34 fps file size 67.5 MB<br>
<br>
HEVC-vaapi CPU 0-50% (single) 85.8 fps file size 117 MB<br>
(I could not see the GPU engagement)<br>
<br>
Only in x265-lo do I perceive a small decay in quality compared to the<br>
original. All others are comparable.<br>
<br>
For me a great news (thanks Andrew!) is the exploitation of<br>
multithread; on the terminal you can read the sentence:<br>
"Thread pool created using 16 threads"<br>
I have a CPU 8c/16t.</blockquote><div><br></div><div>it also seems to use assembler as planned) </div><div> </div><div>but a bit of concern difference between reported number of encoded frames by x265 itself and Cinelerra:</div><div><br></div><div>encoded 7470 frames in 272.39s (27.42 fps), 1167.83 kb/s, Avg QP:32.61</div><div>Render::render_single: Session finished.</div><div>** rendered 7500 frames in 272.418 secs, 27.531 fps</div><div><br></div><div><br></div><div>does this mean you lost 30 frames somewhere? was this bug/difference present in unpatched Cin? </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
The only thing I regret is that the new x265 drivers introduce a CinGG<br>
build delay of 15 min. Before my entire compile was 5 min, now it's 20<br>
min.<br>
</blockquote>