[Cin] my rendering is really slow

[Andrew Randrianasulu]

On Sunday, July 18, 2021, Andrew Randrianasulu <randrianasulu at gmail.com>
wrote:

>
>
> On Sunday, July 18, 2021, gorge rankin via Cin <cin at lists.cinelerra-gg.org>
> wrote:
>
>> Hello, just some feedback on my investigation.
>>
>
> thanks for digging & repirting back!
>
>
>
>> 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.
>>
>
> i think mpeg4/h264 use same limited (mpeg) color range, so nothing to
> loose from default already  compressed in h264 input...
>

I searched a bit more..

it seems nvenc can accept full range, but in general for this you might
want to use yet another format switch (dropdown menu) in encoding param
window.. also see nvenc-specific options described here..

https://superuser.com/questions/1296374/best-settings-for-ffmpeg-with-nvenc

https://forums.developer.nvidia.com/t/nvenc-hevc-with-full-range-colors/44454

current nvenc part of ffmpeg uses

vui->videoFullRangeFlag = (avctx->color_range == AVCOL_RANGE_JPEG
        || ctx->data_pix_fmt == AV_PIX_FMT_YUVJ420P || ctx->data_pix_fmt ==
AV_PIX_FMT_YUVJ422P || ctx->data_pix_fmt == AV_PIX_FMT_YUVJ444P);


https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/nvenc.c

so try to play with those parameters too..?


>
>
>>
>> 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".
>>
>
> does plain ffmpeg/shotcut encode such files better (faster) with same
> nvenc?
>
>
>> 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.
>>
>
> thanks, it seems current nvenc might have some not-so-obvious limitations,
> might be worth mentioning in manual (with hw description and driver
> version)
>
>>
>> [image: my-cin-setup-for-obs-videos.png]
>>
>>
>>
>> On Sat, Jul 17, 2021 at 12:22 AM Phyllis Smith via Cin <
>> cin at lists.cinelerra-gg.org> 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
>>> Cin at lists.cinelerra-gg.org
>>> https://lists.cinelerra-gg.org/mailman/listinfo/cin
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20210718/f9896b7c/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: my-cin-setup-for-obs-videos.png
Type: image/png
Size: 199539 bytes
Desc: not available
URL: <https://lists.cinelerra-gg.org/pipermail/cin/attachments/20210718/f9896b7c/attachment-0001.png>