<div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:small">Hi, Andrew, sorry for the late reply and THANK YOU for the information about nvenc below.<br></div><div class="gmail_default" style="font-size:small"><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_default" style="font-size:small"><span class="gmail_default" style="font-size:small"></span>as you can
see it choked at "git clone yes ffmpeg.git" ... may be removing 'yes'
will make it work, until finish or at least next err... Time to patch.</div></blockquote><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">GG checked a patch into the GIT repository today. The short response is use the latest GIT with this:</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">#!/bin/bash<br>( ./autogen.sh<br> ./configure --with-single-user --with-booby --with-git-ffmpeg=<a href="https://git.ffmpeg.org/ffmpeg.git">https://git.ffmpeg.org/ffmpeg.git</a><br> make && make install ) 2>&1 | tee log<br>mv Makefile Makefile.cfg<br>cp Makefile.devel Makefile</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">He says you will understand the above. Basically you do not provide the "yes" but rather the actual URL location of the ffmpeg git.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">The procedure for obtaining the latest ffmpeg IS NOT KEPT UP-TO-DATE. So the line numbers will always change. He generally only updates those line numbers when he adds a new released/stable version of ffmpeg to CinelerraGG. Ffmpeg is constantly changing and many times the git version is not as stable as desired (just like CinGG sometimes in the middle of the month.) But he has updated it today and he ran it and it built correctly so it should for you too.</div><div class="gmail_default" style="font-size:small">-----------------------------------------------------------------------------------------------------------------------<br></div></div></div><div class="gmail_quote"><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">
<b>PS: reason why I tried this was interesting commit in ffmpeg, removing nvenc from non-free:<br>
</b></blockquote><div><b> </b></div><b><font size="4">WHOA!!! Huge Thank You for discovering this and passing it along.</font></b></div><div class="gmail_quote"><b><font size="4"><span class="gmail_default" style="font-size:small"></span></font></b><font size="4"><span class="gmail_default" style="font-size:small">-------------------------------------------------------------------------------------------------------------------------</span></font><b><br></b></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><b>
</b><br>
Also, I found this text, explaining various options you can pass to hw encoders:<br>
<br>
<a href="https://gist.github.com/Brainiarc7/4b49f463a08377530df6cecb8171306a" rel="noreferrer" target="_blank">https://gist.github.com/Brainiarc7/4b49f463a08377530df6cecb8171306a</a><br>
FFmpeg and libav's playbook: Advanced encoding options with hardware-based acceleration, NVIDIA's NVENC and Intel's VAAPI-based encoder.<br>
-----------------<br>
<br>
ffmpeg -h encoder=h264_vaapi<br>
<br>
Encoder h264_vaapi [H.264/AVC (VAAPI)]:<br>
General capabilities: delay <br>
Threading capabilities: none<br>
Supported pixel formats: vaapi_vld<br>
h264_vaapi AVOptions:<br>
-qp <int> E..V.... Constant QP (for P-frames; scaled by qfactor/qoffset for I/B) (from 0 to 52) (default 20)<br>
-quality <int> E..V.... Set encode quality (trades off against speed, higher is faster) (from 0 to 8) (default 0)<br>
-low_power <int> E..V.... Use low-power encoding mode (experimental: only supported on some platforms, does not support all features) (from 0 to 1) (default 0)<br>
-----------------<br></div></blockquote><div><span class="gmail_default" style="font-size:small">I will have to study the meaning of the above.</span> <br></div><div><div style="font-size:small" class="gmail_default">------------------------------------------------------------------------------------------------------------------------</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>
<br>
Also, I wonder if some ffmpeg filters, based on va-api (deinterlace, scale, brightness ...) or opencl will work for at least Intel/AMD ... But then Cinelerra probably should understand what kind of hw (GPU) based filters attached to track, and not call download from GPU until first sw effect appear ... (a bit like it should work with OpenGL today).<br></div></blockquote><div><br></div><div style="font-size:small" class="gmail_default">Hmmm. GG has not had a chance to think about this yet. But first he is going to see if he can get ffmpeg nvenc working with Cinelerra. Earlier when he first looked into it, there was still a requirement for a lot more libraries to be included. gg/Phyllis</div></div></div>