https://bugs.kde.org/show_bug.cgi?id=439770
Bug ID: 439770
Summary: Not able to change encoding profile for proxy clips
Product: kdenlive
Version: 21.04.2
Platform: Flatpak
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: User Interface
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
I'm not able to change the encoding profile for proxy clips. I have an older
GPU that Ubuntu 20.04 has been holding back versions of upgrades. When I enable
proxy clips, Kdenlive appears to be only selecting h264_nvenc. If I set it to
regular h264 or automatic the detailed log is always the same message with the
warning about h264_nvenc.
STEPS TO REPRODUCE
1. Enable proxy clips, set profile to any profile that should be compatible
with the setup (I've tried h264, mpeg2, and automatic).
2. Click apply (issue also happens if I restart Kdenlive after this step)
3. Open existing project
4. Right click on a clip and select proxy clip
OBSERVED RESULT
Kdenlive shows a message that the proxy clip failed to create. The message
always indicates that it tried to use h264_nvenc.
EXPECTED RESULT
I expected Kdenlive's automatic setting to use a different encoding profile if
the driver for nvenc is too old. I also expected that Kdenlive would use any
other encoding profile that I selected.
I've seen this issue on the stable from Flathub as well as the latest stable
appimage (21.11.70). Below is the information from the appimage.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Ubuntu 20.04
KDE Plasma Version: Unknown (not sure where to find that in the app since I do
not see an about system menu item).
KDE Frameworks Version: 5.81.0
Qt Version: 5.14.2 (built against 5.14.2)
ADDITIONAL INFORMATION
Detailed log from Kdenlive:
[h264_nvenc @ 0x180a640] Driver does not support the required nvenc API
version. Required: 11.0 Found: 10.0
[h264_nvenc @ 0x180a640] The minimum required Nvidia driver for nvenc is
(unknown) or newer
Error initializing output stream 0:0 -- Error while opening encoder for output
stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or
height
--
You are receiving this mail because:
You are watching all bug changes.
