Registered Member
|
On my 32-bit ubuntu installation libmltavformat is happy using the latest libavutil.
EDIT: meant to say libavutil ldd -r /usr/local/lib/mlt/libmltavformat.so | grep avutil libavutil.so.50 => /usr/local/lib/libavutil.so.50 (0xb761d000) Note I have mlt in /usr/local because I installed it from source code. I also have kdenlive, ffmpeg, and libx264 installed from source code. |
Registered Member
|
My apologies for taking a long time, but I went looking and the info given is very valuable.
It seems that I built mlt with an older ffmpeg version, version, resulting in libavutil.so.49. What I find strange is that I'd say that it should link to libavutil.so instead of libavutil.so.49 (why else use dynamic linking?) What you _can_ try, is linking your libavutil to a libavutil.so.49, then run ldconfig, so that the file is found. For the time being this is the best solution I can think of. It's defenitely not the cleanest way to accomplish this though, but ought to be a fairly safe temporary fix. In a newer install script I will try to check out and see if this can be realized during install. |
Registered Member
|
Okies, I'm just giving that a go right now. I think the problem exists for both the x86_32 as well as the x86_64, btw.
I used the following command, as root; cd /usr/lib64 ln -s libavutil.so libavutil.so.49 Not tried it with any videos yet (just tried it now) but it seems to have removed the error. Kdenlive now puts a tick next to all of the installed modules, and there's a long list of avaliable codecs :) . Edit: I tried it briefly to see if it would load a .flv file from youtube, so far so good. ljones |
Registered Member
|
Registered users: Bing [Bot], blue_bullet, Google [Bot], Yahoo [Bot]