Bug 392644 - Kdenlive no longer sees libx264
Summary: Kdenlive no longer sees libx264
Status: RESOLVED NOT A BUG
Alias: None
Product: kdenlive
Classification: Applications
Component: Rendering & Export (show other bugs)
Version: 17.12.3
Platform: RedHat Enterprise Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-04-02 17:36 UTC by Jeffrey Rocchio
Modified: 2018-04-19 18:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screen Shot (253.20 KB, image/jpeg)
2018-04-02 17:36 UTC, Jeffrey Rocchio
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeffrey Rocchio 2018-04-02 17:36:27 UTC
Created attachment 111786 [details]
Screen Shot

After working fine for 6 months, Kdenlive is suddenly reporting that it cannot see the codec for H.264 video export or encoding. It plays H.264 videos just fine. Running ffmpeg -codecs in a terminal shows that ffmpeg still sees libx264; and I do have the file usr/lib64/libx264.so.148 on my filesystem. 

ffmpeg -codecs returns this >
DEV.LS h264 H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 (decoders: h264 h264_qsv h264_vdpau h264_cuvid ) (encoders: h264_nvenc h264_qsv h264_vaapi nvenc nvenc_h264 )

I have attached a screen-shot showing that Kdenlive has greyed out the h.264 Render option, next to the Fedora package manager showing that libx264 is installed.

IF you could advise on how Kdenlive determines the presence, and validity, of the h264 codec than perhaps I can work through figuring this out.
Comment 1 Jeffrey Rocchio 2018-04-19 18:32:15 UTC
Resolved. In continuing to dig I discovered that I had two software repositories enabled that both provided the ffmpeg package. But one of those does not compile their ffmpeg with the --enable-libx264 switch. Today, by chance, RPM-Fusion pushed an ffmpeg update to me and that automagically fixed it. It took a *lot* of digging through ffmpeg docs to learn about the libx264 compile switch and then to decode my way through both dnf and packageKit transaction histories to piece together the story of what happened.

It might be too much to ask, but if there were a way to users a richer set of guidance, error messaging, or some such to help them understand these (rather complicated from a user's perspective) software requirements and dependencies that would probably be helpful to many.