Bug 26904 - kdenlive 20.04.2 can't render to mp4 with ffmpeg 4.3
Summary: kdenlive 20.04.2 can't render to mp4 with ffmpeg 4.3
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: José Jorge
QA Contact:
URL:
Whiteboard:
Keywords:
: 26913 (view as bug list)
Depends on:
Blocks:
 
Reported: 2020-07-06 09:50 CEST by Stig-Ørjan Smelror
Modified: 2020-07-09 20:34 CEST (History)
3 users (show)

See Also:
Source RPM: mlt-6.20.0-2.mga8.src.rpm
CVE:
Status comment:


Attachments
kdenlive render screen (77.98 KB, image/png)
2020-07-06 09:51 CEST, Stig-Ørjan Smelror
Details
Still no mp4/aac encoding in kdenlive (68.13 KB, image/png)
2020-07-06 21:10 CEST, Stig-Ørjan Smelror
Details

Description Stig-Ørjan Smelror 2020-07-06 09:50:57 CEST
I've compiled my own version of ffmpeg to enable non-free codecs and have also recompiled kdenlive to see if that made a difference.

I found one option down the list to render to lossless mp4 and the resulting file was almost 10GB large.
Comment 1 Stig-Ørjan Smelror 2020-07-06 09:51:24 CEST
Created attachment 11733 [details]
kdenlive render screen
Comment 2 Stig-Ørjan Smelror 2020-07-06 09:55:46 CEST
On a sidenote, the webm file of the same video is 90.7MB.
Comment 3 Stig-Ørjan Smelror 2020-07-06 21:10:39 CEST
Created attachment 11734 [details]
Still no mp4/aac encoding in kdenlive

Thanks for all the great work, David.

Still no mp4 rendering option in kdenlive. Haven't tried command line, yet.
Comment 4 David GEIGER 2020-07-06 21:43:27 CEST
Is this a regression or is the same issue on mga7?

Please file a new bug upstream kdenlive.

CC: (none) => geiger.david68210

Comment 5 Lewis Smith 2020-07-06 21:50:29 CEST
Thanks for the screenshot, it often helps a lot to understand a bug.
Is your complaint that the output file is so huge? Does it playback?
Or that kdenlive seems to offer MP4 output, but complains it is unsupported?
You do have tainted enabled?

> I've compiled my own version of ffmpeg to enable non-free codecs
This is treading on thin ice; you are raising a bug with some DIY software.
How does this differ from simply using the Tainted version?
Have a look at Bug 26861 and see whether that helps.

$ urpmq --requires-recursive kdenlive | grep x26
lib64x264_157
lib64x265_188

Is it worth trying to export the kdenlive project to something lossless that works, and play with ffmpg directly to convert it to [lossless]mp4 ? ffmpeg is extremely powerful & versatile, but not easy to drive. (We had a bug where it had been used to make a screencast!).

CC: (none) => lewyssmith

Comment 6 Stig-Ørjan Smelror 2020-07-06 21:58:05 CEST
(In reply to David GEIGER from comment #4)
> Is this a regression or is the same issue on mga7?
> 
> Please file a new bug upstream kdenlive.

I was able to render to mp4 using a non-free ffmpeg when we were at version 4.2.x.

Could be that something has changed in 4.3 that is incompatible with kdenlive somehow.

Will file a report upstream.
Comment 7 Stig-Ørjan Smelror 2020-07-06 22:01:04 CEST
(In reply to Lewis Smith from comment #5)
> Thanks for the screenshot, it often helps a lot to understand a bug.
> Is your complaint that the output file is so huge? Does it playback?
> Or that kdenlive seems to offer MP4 output, but complains it is unsupported?
> You do have tainted enabled?
> 
> > I've compiled my own version of ffmpeg to enable non-free codecs
> This is treading on thin ice; you are raising a bug with some DIY software.
> How does this differ from simply using the Tainted version?
> Have a look at Bug 26861 and see whether that helps.
> 
> $ urpmq --requires-recursive kdenlive | grep x26
> lib64x264_157
> lib64x265_188
> 
> Is it worth trying to export the kdenlive project to something lossless that
> works, and play with ffmpg directly to convert it to [lossless]mp4 ? ffmpeg
> is extremely powerful & versatile, but not easy to drive. (We had a bug
> where it had been used to make a screencast!).

The issue is that kdenlive doesn't offer the option to render to mp4.

Even with all the updates David did today.

Yes, I do have tainted enabled.

Yes, I do compile packages locally to enable CPU optimizations to inch out every ounce of performance I can from my old hardware.
Comment 8 Stig-Ørjan Smelror 2020-07-06 22:18:06 CEST
Upstream report: https://bugs.kde.org/show_bug.cgi?id=423950
Comment 9 David GEIGER 2020-07-07 22:51:40 CEST
*** Bug 26913 has been marked as a duplicate of this bug. ***

CC: (none) => wilcal.int

Comment 10 William Kenney 2020-07-07 23:47:08 CEST
(In reply to David GEIGER from comment #9)
> *** Bug 26913 has been marked as a duplicate of this bug. ***

Confirmed. Same situation here.
Thanks
Comment 11 Stig-Ørjan Smelror 2020-07-08 21:57:52 CEST
Found the culprit.

mlt needs to be either updated or recompiled.

I updated it locally to git master and am now able to render to mp4.

Assigning to Zezinho as the maintainer of mlt.

Source RPM: (none) => mlt-6.20.0-2.mga8.src.rpm
Assignee: bugsquad => lists.jjorge

Comment 12 José Jorge 2020-07-08 22:35:41 CEST
(In reply to Stig-Ørjan Smelror from comment #11)
> Found the culprit.
> 
> mlt needs to be either updated or recompiled.
> 
> I updated it locally to git master and am now able to render to mp4.
> 
> Assigning to Zezinho as the maintainer of mlt.

In fact, I think mlt just needs a rebuild, without git snapshot. I've tried but I get QT5 errors that I'm sure you'll know how to fix much better than me :

http://pkgsubmit.mageia.org/uploads/failure/cauldron/core/release/20200708203058.zezinho.duvel.7589/log/mlt-6.20.0-3.mga8/build.0.20200708203102.log
Comment 13 William Kenney 2020-07-09 00:27:35 CEST
What'a Team, What'a Team!!!!!
Comment 14 David GEIGER 2020-07-09 07:08:51 CEST
mlt fixed and rebuilded!
Comment 15 William Kenney 2020-07-09 17:48:53 CEST
Looks good today.
I've been able to render an MP4 file after updating.
Thanks to all.
Comment 16 David GEIGER 2020-07-09 20:34:34 CEST
Closed!

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.