Been using kdenlive for many years. After the last couple of system updates, it fails to render a long file. Tried it with 3 different mp4 files that are between 1:30 and 2:00 hours long. These are personal videos shot by me. Works perfectly with shorter videos and different sections of the 3 long files. It renders for several hours then pops up an error saying it aborted and the file is corrupted. When it crashes, the resulting file size is 2.8MB.

kbuntu 64bit 14.04 LTS, fully updated with latest (from ubuntu repositories) kdenlive, melt, etc.

Here's the error I get.
Rendering of /home/jeff/kdenlive/untitled.mp4 crashed
medium: [ ref=1, _mlt_properties_load=medium, __mlt_properties_load=medium ]
[mp4 muxer @ 0x7f7cd04c7320] [Eval @ 0x7f7cd51764a0] Undefined constant or missing '(' in 'faststart' [mp4 muxer @ 0x7f7cd04c7320] Unable to parse option value "faststart"
[libx264 @ 0x7f7cd04c8dc0] interlace + weightp is not implemented

I'm not using any transitions or special effects. I haven't narrowed it down to exactly how long a video it will render properly. I've tried rendering 20 minute sections of each file and it works just fine. It will render 20 minute sections from the start, middle and end of these videos, but not the entire video.

I've tried to add several PPA repositories, as suggested in the forum, but when I do an update adding them, I get 2 errors no matter what 3rd party repositories I use. They have something to do with finding 64bit and 32bit programs.

Not sure why it works great on short videos, but not long ones. I would think it would come across this error even on shorter videos.
Any help would be appreciated.

I use Manjaro 16 KDE and I have trouble rendering long movies as well. Yesterday I tried to render a movie which should be just a bit longer than 1 hour. It is built up of smaller movies which have all been rendered already. These smaller ones give no problem at all. During the longer movie the computer crashes on me. Only thing to do is to pushing the reset button on the computer. I can't find any error messages about it.
Today however it worked. Using Conky I monitored the CPU power and temperature and they both reached the limit for quite some time, but rendering was okay.

One thing which comes to mind is I used Google-Chrome yesterday while rendering and maybe that combo was just too much.
This is my computer:

Code: Select all

System:    Host: Manjaro16 Kernel: 4.9.20-1-MANJARO x86_64 (64 bit gcc: 6.3.1)
           Desktop: KDE Plasma 5.9.4 (Qt 5.8.0) Distro: Manjaro Linux
Machine:   Device: desktop Mobo: ASUSTeK model: M5A97 R2.0 v: Rev 1.xx BIOS: American Megatrends v: 2601 date: 03/24/2015
CPU:       Octa core AMD FX-8350 Eight-Core (-MCP-) cache: 16384 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm) bmips: 67452
           clock speeds: max: 4200 MHz 1: 1400 MHz 2: 1400 MHz 3: 1400 MHz 4: 1400 MHz 5: 1400 MHz 6: 1400 MHz
           7: 1400 MHz 8: 1400 MHz
Graphics:  Card: NVIDIA GK104 [GeForce GTX 760] bus-ID: 01:00.0
           Display Server: X.Org 1.19.3 driver: nvidia Resolution: 1920x1080@60.00hz
           GLX Renderer: GeForce GTX 760/PCIe/SSE2 GLX Version: 4.5.0 NVIDIA 375.39 Direct Rendering: Yes
Audio:     Card-1 NVIDIA GK104 HDMI Audio Controller driver: snd_hda_intel bus-ID: 01:00.1
           Card-2 Advanced Micro Devices [AMD/ATI] SBx00 Azalia (Intel HDA)
           driver: snd_hda_intel bus-ID: 00:14.2
           Sound: Advanced Linux Sound Architecture v: k4.9.20-1-MANJARO
Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
           driver: r8168 v: 8.043.02-NAPI port: d000 bus-ID: 02:00.0
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 2256.5GB (43.1% used)
           ID-1: /dev/sda model: ADATA_SP900 size: 128.0GB
           ID-2: /dev/sdd model: ST1000DM003 size: 1000.2GB
           ID-3: /dev/sdc model: ST1000DM003 size: 1000.2GB
           ID-4: /dev/sdb model: ADATA_SP900 size: 128.0GB
Partition: ID-1: / size: 32G used: 16G (54%) fs: ext4 dev: /dev/sda1
           ID-2: /home size: 70G used: 2.0G (3%) fs: ext4 dev: /dev/sda3
Sensors:   System Temperatures: cpu: 15.0C mobo: N/A gpu: 0.0:34C
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 228 Uptime: 2:37 Memory: 2185.2/15787.1MB Init: systemd Gcc sys: 6.3.1
           Client: Shell (bash 4.4.121) inxi: 2.3.8

[EDIT] Forgot to say I use Kdenlive 16.12.3, MLT version 6.4.1, KDE 5.9.4

Was the movie that got rendered the same one that didn't get rendered before?

The error message implies there's an option that is passed that it can't understand. Why doesn't the error show up on shorter videos? What is it that the program is doing on a long video that it isn't on a shorter video?

Since there seems to be a certain threshold of length where is works or doesn't work. I'd be interested to see what would happen if you tried a longer video.

I'm also open to any ideas on how to troubleshoot this further. I've been using kdenlive for a long time, on long videos and it has worked flawlessly over the years, until some update broke it.

I'd also be interested in how to roll back to an earlier version including all dependencies.

jeffjordan wrote:Was the movie that got rendered the same one that didn't get rendered before?

The error message implies there's an option that is passed that it can't understand. Why doesn't the error show up on shorter videos? What is it that the program is doing on a long video that it isn't on a shorter video?

Since there seems to be a certain threshold of length where is works or doesn't work. I'd be interested to see what would happen if you tried a longer video.

I'm also open to any ideas on how to troubleshoot this further. I've been using kdenlive for a long time, on long videos and it has worked flawlessly over the years, until some update broke it.

I'd also be interested in how to roll back to an earlier version including all dependencies.

Hi Jeff, yes the video was the same as the one I rendered yesterday. It consists of already rendered shorter movies which are placed one after the other on the timeline. The shorter movies have effects and transitions in them, the larger one not.
It would be strange if Kdenlive would have a maximum length of movie it can render, something I can not believe.
If you have rendered long(er) movies before with older versions of the program then yes, something could be broken by some update. I don't use Kdenlive that long.
No idea how to rollback to a previous version, I guess that's something the KDE people should be able to tell you.
Success.

Hello,

'faststart' is a libavcodec parameter that takes effect at the end of MP4 rendering

(basically it moves the MP4 indexes to the beginning of file, so that is can start to play before end of downloading).
Rolling back libavcodec would break every multimedia thing in your distro

Are you using an official export setting, or a custom one?

note: the flag is set from MLT presets, typically in
/usr/share/mlt/presets/consumer/avformat/
(MPEG-4*, x26*-medium*)
if your output file is really huge and makes reloacting index to fail,
maybe try to edit your MP4 profile and remove "properties=x264-medium"

I tried 2 different 'standard' export selections. Same results.

Demus mentioned that he had trouble rendering a long movie one day, but it worked the next day. I wonder what changed.

I see that there are numerous x264-medium files in that directory. You mentioned: maybe try to edit your MP4 profile and remove "properties=x264-medium"

BTW, the files should be no more than 6GB to 8GB from past experience. On the timeline they show to be 2 hours. Memory usage doesn't seem to be a problem. I've rendered long movies before on much less horsepower than I'm using now.

Sorry for being such as newb, but kdenlive has always just worked for me, so I never delved into editing profiles. How do I do that? I can't find anything in any menu.