Try again with the "-threads 0" removed.

Did you remove -threads 0 from both ffmpeg passes? I have no idea what else it could be. If have some scripts that use ffmpeg and they get the segfault with -threads 0 but not without it.

Regarding the mlt libraries, it looks like you have multiple versions of mlt installed. That could be part of your original kdenlive problem.

You have what looks like the most recent official mlt here:
ls /usr/lib/libmlt* :
/usr/lib/libmlt.so /usr/lib/libmlt++.so.0.4.6 /usr/lib/libmlt++.so.3
/usr/lib/libmlt++.so /usr/lib/libmlt.so.2
/usr/lib/libmlt.so.0.4.6 /usr/lib/libmlt++.so.2
(but /usr/lib/libmlt++.so.2 might be a leftover from an older mlt)

And you have what looks like parts of 2 older mlt releases here:
ls /usr/local/lib/libmlt*
/usr/local/lib/libmlt.so.0.4.3 /usr/local/lib/libmlt++.so.0.4.4
/usr/local/lib/libmlt++.so.0.4.3 /usr/local/lib/libmlt.so.1
/usr/local/lib/libmlt.so.0.4.4 /usr/local/lib/libmlt++.so.2

You might want to wipe out all the mlt stuff, then reinstall. See here
http://kdenlive.org/user-manual/downloading-and-installing-kdenlive/installing-source/installing-mlt-rendering-engine

EDIT: Another weird thing is this:
ldd /usr/lib/mlt/libmltavformat.so
libavutil.so.49 => /usr/lib/libavutil.so.49 (0x00007f3ad222e000)
libavutil.so.50 => /usr/local/lib/libavutil.so.50 (0x00007f3ad1876000)

So it's finding an old version in /usr and a new version in /usr/local. The libavutil is part of the ffmpeg package, so you still have parts of the old ffmpeg installed in /usr.

See the EDIT to my previous post regarding libavutil.

As for the error compiling mlt, I see the linker is complaining about libx264 in /usr/local, but from one of your previous posts I see libx264 is installed in /usr:

ldd /usr/lib/mlt/libmltavformat.so
libx264.so.78 => /usr/lib/libx264.so.78 (0x00007f3acfe3f000)

That is really weird. Do you have libx264 installed in two different places?

I managed to get H.264 going on:

1) click on one of the predefined rendering profiles in the H.264 group
2) click the 'Create new profile' button
3) Give it a name, and replace acodec=libfaac to acodec=libmp3lame
This will then render with mp3+h264

I was also getting crazy for exactly this issue. I managed to compile libx264, ffmpeg, mlt and kdenlive, in this order, get rid of any previous installations of ffmpeg and mlt from ubuntu (karmic) packages, but *always* encoding to h264 was disabled in the kdenlive's rendering" window.

Finally this message gave me the clue: I re-ran the Settings -> configuration wizard and voilà!

So it *must* be clearly advertised somewhere that one MUST re-run this wizard (or delete the kdenlive config file into ~/.kde... dir) for the changes to make effect.

Hope this helps somebody.

You can build a new version of ffmpeg and ffmpeg-extra using ubuntu sources.
You need to somewhat know what you are doing, but this webpage is useful and can be adapted for your needs.
http://ubuntuforums.org/showthread.php?t=1071262

You would need to build both the ffmpeg and ffmpeg-extra packages.

http://packages.ubuntu.com/source/karmic/ffmpeg
and
http://packages.ubuntu.com/source/karmic/ffmpeg-extra

You would not need to edit any debian/ files just install the .diff patch and build with these commands for both ffmpeg and then ffmpeg-extra

Commands:
export DEBEMAIL="Your Name"

debchange --nmu "Rebuild enabling --enable-nonfree --enable-externalcodecs"

DEB_BUILD_OPTIONS="--enable-externalcodecs --enable-nonfree" debuild -rfakeroot -uc -us -b


Install the local packages and re-run the kdenlive config wizard to pick up the changes.

Edit: you may also need to remove the kdenliverc file.

No h264 rendering has been an ongoing problem when updating Kdenlive in the last couple of months from Sunab repos. When I run the config wizard the problem clears up BUT you have to restart Kdenlive to get all the render profiles to actually show up again. (I don't do any compiling myself.)

There are some WebM profiles that are x-ed out still however. No biggie as I've not really wanted to render to this yet but maybe at some point. Hopefully by v 0.8 out soon these will show up as well.

Hi folks,

It seems that a lot of people are misunderstanding what's happening here.

1st: when an encoding profile is X-ed out it means that one encoder used in the profile is not available. You wan to know which one? Just put the mouse on an X-ed out profile and wait for a second -> a tootip will appear informing about the missing encoder.

2nd: encoders are provided by FFmpeg, so a kdenlive update is irrelevant to "solve your problem"

3rd: in Ubuntu and other distributions FFmpeg stock install is "stripped" meaning that many encoders are not provided by default, they are packages in a separate packages called "unstripped or extra". You have to manually install "extra" FFmpeg packages to activate many encoder that are patented in some country ...

4th: Since Ubuntu Karmic, debian/Ubuntu devs have decided to NOT activate, in regular version AND extra version, one encoder named libfaac (nasty patent problems ...) But many kdenlive profiles are using it. Red cross is here!

5th: This is why in my repos you can find a special version of FFmpeg for karmic/lucid with libfaac activated.

6th: The Webm is X-ed out because the libvpx encoder is not found (see the tooltip). FFmpeg version in karmic/lucid is too old to support libvpx encoder, so it will stay X-ed out.

7th: each time Ubuntu official packages are updated for security reasons, my packages are superseded, I need to update my packages too. If you install security updates for FFmpeg from ubuntu official repos, libfaac will be disabled again.

Last words : Karmic end of life is there in 10 days, so it will be time to upgrade ...

Sunab.

AAC is screwed in extra and regular ubuntu libavcodec packages, use the medibuntu ppa, that's the easiest way if you don't want to comple ffmpeg extra again yourself.

http://medibuntu.org/


install that repo and update your ffmpeg extra packages, in particular libavcodec.

after this libfaac will appear in the config wizard and h264's sound won't be completely awful. If it is still re-run config wizard and possibly you may have to go into the h.264 profiles and change AAC to libfaac.