Am 23.07.2018 um 19:35 schrieb johnar1:
Thanks again, for your efforts! (Ich vermute, dass du ebenfalls Deutscher bist, also nochmal danke haha.) *I have 100% and with absolute certainty figured out what the actual problem is.*

I have compiled melt from the latest git available here: https://github.com/mltframework/mlt/releases/tag/v6.10.0
I just ./configure and make && make install
I then use this melt executable by selecting it in the kdenlive environment tab.

Here is the kicker:

When I use ./configure --enable-gpl --enable-gpl3  to compile melt---> NVENC does not --->CPU utilization 100% on 1 core, 20% - 30% on the rest, GPU utilization= 4%

When  I use ./configure without these two flags ---> NVENC works --> CPU utilization = 100% on all cores /GPU utilization = 90%


Here is kicker number 2:

I originally thought this was a problem with NVENC, but that is not true.

When compiling with --enable-gpl and --enable-gpl3, Kdenlive subsequently only uses 1 single CPU core for rendering. (Despite having 4 threads selected in the render dialog, kdenlive environment and even in the generated render script)

*That *is why NVENC *appears* to not work, because the CPU is not being used properly, hence it cannot feed the GPU enough frames. There is some GPU utilization

Now I have read that enabling the license also enables a bunch of qt modules, and qt obviously heavily pertains to concurrent CPU scheduling.

You'd think that the problem could be solved by simply not using --enable-gpl and --enable-gpl3, but unfortunately that excludes the libmltqt.so module, which I need for title clips in kdenlive.


So basically, without gpl I get crazy render speeds and almost 100% GPU/CPU utilization, but not title clips. And with gpl only 1 single CPU core is being used for rendering, no matter how many times I specify 4 threads, but title clips work.
*_
_*
*_We are sooooo close to solving this omg!_**_
_*



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On July 22, 2018 6:46 PM, Eugen Mohr <eugen.m...@gmx.net> wrote:



You render it with MLT 11.0. Kdenlive refactoring runs MLT 10.0. Try with the actual AppImage 18.08.Beta 18.



Am 22.07.2018 um 16:15 schrieb johnar1:
Ok, I think I have isolated the problem now.

I just compiled kdenlive from the latest git, everything works and I get the following warning before launching it. (Screenshot attached)

The following codecs are missing: libx265, nvenc_h264, h264_nvenc

The Appimage version does not state this warning as it probably already comes with the necessary stuff.

So the final question is, how do I get these codecs?
The only thing you can manually install that is related to nvenc, are the headers themselves, which I already have installed.

Any ideas?


Sent with ProtonMail <https://protonmail.com> Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On July 16, 2018 2:48 PM, Eugen Mohr <eugen.m...@gmx.net> wrote:

On a first look:

File which runs:

MLT version 6.7.0

frame_rate_den="1"

60 fps

name="length">53282


file which doesn't run:

MLT version 6.10.0 → version of the Kdenlive refactoring

frame_rate_den="1001"

29.97 fps

name="length">00:14:48;00


check this parameters with other files



*Gesendet:* Montag, 16. Juli 2018 um 07:51 Uhr
*Von:* johnar1 <john...@protonmail.com>
*An:* "kdenlive@kde.org" <kdenlive@kde.org>
*Betreff:* Incredible Render Performance In Kdenlive With NVENC - But 1 Big Problem


System: i5 6600K, 1050TI, Ubuntu 18.04, Kernel 4.16
I have successfully compiled mlt and ffmpeg with nvenc support using the official nvenc headers stripped from the Nvidia SDK. Rendering the first minute of the 1080p Sintel version, with 4 threads specified and my nvenc profile, finishes in 10 seconds. Sintel can be downloaded here: https://durian.blender.org/download/ <https://durian.blender.org/download/[/url> Nvenc Profile: (compatible with recent mlt versions who are nvenc enabled by deafult) f=mp4 vcodec=nvenc_h264 global_quality=21 vq=21 preset=slow bf=2 ab=384k


Now here is the problem that I do not understand:
Using the latest version of kdenlive from the kdenlive-master ppa combined with the newly compiled versions of ffmpeg and mlt works perfectly, but only under very specific circumstances.

I have only been able to get rendering with nvenc to work properly when I use and open this specific kdenlive [b]save file[/b] which I made of the first minute of the Sintel short film with the Appimage Version of Kdenlive. After launching the ppa/installed version of kdenlive and opening this save file, rendering with nvenc works flawlessly.

If I simply start a new project, adding the whole Sintel short film to the project bin, cutting the first minute and render it, nvenc simply does not work and the render time is tripled, despite having changed nothing else, including the nvenc render profile.

If I create a save file of the first minute of Sintel with the installed version and open it on the Appimage version, nvenc does not work again.

Conclusion: There must be something in this save file, maybe a parameter, additonal settings or any type of code not present in the default kdenlive project profiles, which enables NVENC.

I would greatly appreciate it if we could find out the source of this problem together.

Kdenlive Appimage Save File with which NVENC works:
https://pastebin.com/rzjR57DJ

PPA/Installed Version of Kdenlive created Save File which breaks NVENC:
https://pastebin.com/3uQ8sP0C




Reply via email to