Hello, just some feedback on my investigation. I've discovered that if I use mpeg color range instead of YUV, my speed to render out to yuv420p/nvenc are same as shotcut (for reference purposes). Near realtime (10 sec video renders in 10 seconds with no edits). Colors of output video seem to be same as input. I've been using kcolorchooser and I cant find a diff. I see in the manual, that 'mpeg' offers less color range than jpeg, but my outputs look just like my input videos. If there is a difference, I certainly cannot see it. However, the speed only holds if I use 60fps video or less. Making color changes, brightness, zoom all seem to be reasonable and on par to what I'm used to seeing in shotcut. However, if my source material is over 60 FPS , the speed of encoding significantly drops off for something as simple as "trim". Going forward, I can convert my sources in ffmpeg, no biggie. I'll have to keep my sources tho for future 'just in case'. Attached is a photo of my settings that I'm using for OBS and cin with nvenc for going forward. [image: my-cin-setup-for-obs-videos.png] On Sat, Jul 17, 2021 at 12:22 AM Phyllis Smith via Cin < [email protected]> wrote:
There are no errors at all printed to the console if I launch cin from the
terminal.
Just FYI, on a non-Nvidia laptop, you will get the following errors on the terminal where there is no Nvidia graphics card:
[h264_nvenc @ 0x7f0780085a40] Cannot load libcuda.so.1 FFMPEG::open_encoder err: Operation not permitted int FFMPEG::open_encoder(const char*, const char*): open failed h264_nvenc:/tmp/testnvenc.mp4
So, it sure looks like "nvenc" is working in Gorge's case.
Also in the nvidia control panel, and I can see this:
But the percentage will hit up to 30-50% many times.
--
Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
