OK, I traced this down to a libffmpeg update that broke kdenlive.
The last version of libffmpeg that worked with kdenlive is:
the following two updates:
both do break kdenlive on openSUSE-10.3
I have kdenlive working again on my openSUSE-10.3 PC by reverting back to that older libffmpeg version. However I do not have such an older version for openSUSE-11.0, so it remains broken on kdenlive.
I’ll send the packagers (libffmpeg and kdenlive0) an email, asking that they investigate this problem.
Its not uncommon for ffmpeg updates to break applications. The ffmpeg developers make changes all the time, with what appears to on the surface less than prudent regard for the consequences. However I’m NOT a developer, so I concede I have no insight as to what goes on.
The “bad-boy” is the package mlt, it calls av_free_static once. Therefore the compiler doesn’t complain an error as it is declared in the ffmpeg headers as deprecated. but the new ffmpeg libs doesn’t provide this function any longer. So I commented out this single call and did a rebuild of mlt. To be sure that no side-effects jump in, I released also the mlt++ and kdenlive packages as a simple rebuild.
I know that there are newer sources of kdenlive are available, but lets first fix this issue
So please try mlt-0.2.4 (0.pm.4) and mlt+±0.2.2 (0.pm.9) and new kdenlive-0.6 (1791.pm.svn20080105_2) and give me a short note if it works for you.
I updated mlt, mlt++, and kdenlive on both my openSUSE-10.3 and 11.0 PCs, with the latest Packman updates:
Further to the above, the packager advised me of the following:
Nethertheless please check if kdenlive is now consuming memory …
Because the call for av_free_static should return some memory to the system. In the actual svn sources this call is also disabled in the same manner I did it. But just to be sure that we don’t get of the fire into the frying pan.
So please take a hard look at kdelive use wrt to memory, … has it degraded from previous versions?
I noticed a better behavior of kdenlive after yesterday’s update. I did not check the full functionality, but i intent to.
I saw from Kdenlive - Open Source Video For Linux that the developers have no time to update KDE3 version as they are working hard on KDE4 version, for which they intent to release the first beta shortly.
Unfortunately kdenlive crashes constantly. Earlier, using openSUSE 10.3 and kdenlive 0.5 it crashed seldom and the project file could be recovered. Now, however, when it crashes, the chances are that trying to recover the project file, kdenlive crashes. This makes the software unusable as it is. I am reluctant to go back Cinelerra, but the situation leaves no choices.
I assume you are using the latest Packman version?
I have not used kdenlive for a large project for 3 months, so my experience below is based on that experience (ie at least 3 months out of date). Still, there have not been too many updates to kdenlive since then.
How much memory do you have on your PC ? While significant improvements have been made with kdenlive’s error trapping (so not to crash when you try to perform a feature that was not implemented or not intended), inappropriate GUI action can cause problems. [But note I’ve seen / experienced that in every NLE I’ve used]
I found with the old family laptop (which only has 512MB of RAM and a celeron 1.5 GHz processor) it would crash fairly often. (openSUSE-10.3, KDE-3.5.7). But after a while I learned some operations were more prone to crashes than others, and constantly saving meant a crash caused minimal loss of work. My experience is do NOT use the KDENLIVE recovery feature (after a crash) but just go back to your last saved version. I also found it would crash after an hour of safe benign use (likely a memory leak) so I would close down and restart the app every hour or so (on this old notebook PC).
On my test PC (with KDE-3.5.7 and openSUSE-10.3) it performed a bit better. My test PC is an Athlon-1100 with 1 GByte of RAM. Again, occasional crashes, but the crashes could be narrowed down to certain operations. Again, frequent saves are necessary. Still, the crashes were less frequent.
On my main PC (with KDE-3.5.7 and openSUSE-10.3) it performed significantly better. Far far fewer crashes. My main PC is an Athlon-2800 with 2 GByte of RAM. Again, I still saved frequently, so a crash (on the occasions it did happen) had minimal impact. And again the crashes could be narrowed down to happen more often with certain operations.
My assessment is kdenlive is DEFINITELY useable on all 3 PCs. Even the old laptop. I concede kdenlive is more frustrating to use on the laptop, and I also note kdenlive crashes far far less on my main PC. I have no qualms about recommending kdenlive, but I do caution that familiarity is necessary.
I have yet to find a superior app in Linux. I tried other Video NLE (Non Linear Editors) under Linux (kino, cinelerra, LiVES … etc … ), and I found them all to be less stable than kdenlive. Also, my wife uses some Video NLE on MS-Windows on her PC (Sempron-2600, 1GByte RAM) and she finds the MS-Windows apps crash just as often as the Linux versions.
Unfortunately, this sort of instability seems to be a feature of all NLE, and it is mainly minimized by familiarity with the specific application. ie learn what causes the probability of a crash to happen, and before attempting that operation, ensure you have a current backup.
I’ve had nothing but bad experience with Cinelerra, and I definitely recommend against Cinelerra for all users. I dread the thought of thinking about how much time I wasted with Cinelerra for no useable output. On the other hand, I have produced over a dozen home/family videos (of 30 minutes of length) with KDENLIVE. (although typically with kdenlive, I keep the video down to 5 to 10 minutes or so, and I paste the pieces together later with other software).
My experience on 3 different PCs (same as my above post) is Cinelerra is far less stable than kdelinve. And Cinelerra’s user interface is very counter intuitive (IMHO, of course).
I’ll take a look this weekend, and see if I can create a 5 to 10 minute video, checking out the usability and stability (or lack there-of).
Again, I’ve never used the kdenlive recovery option, but I have always gone back to my last saved set.
On one of the pre-merge forums, We used to have a Cinelerra thread, where users talked about its features. You may find it useful to start a Cinlerra thread, if you do find it helpful to go back to Cinelerra.
If one is inserting a lot of still images into one’s video (in kdenlive) then another technique to minimize kdenlive crashes, and to enhance its performance is to reduce the images before hand to an appropriate small resolution.
ie if creating a NTSC DVD then reduce the images from the camera resolution (which could be something like 2272 x 1704 or even larger, to a simple 640 x 480). That has a significant improvement on display and rendering performance, and I find significantly reduces crashes.
Thus far this evening, I’ve created up to 90 seconds of video clip (made up of mostly still clips and also panoramic panning of still clips using the “pip” transition function) with a music sound track. I’ve had a few crashes, but in all 3 cases they were because I had forgotten that a certain function is unstable. Specifically if one has a clip of about 10 seconds or so, with a transition along its entire length, and one tries to move that clip and transition to a different video track, kdenlive will crash.
The solution in this case is to quickly note what the transition details are, … delete the transition, … move the clip, and add the transition back.
I also found it useful go close the clip nominally some times, such that when one opens it again, one simply has to go to “recent clips” and have it quickly open. That is very useful to speed up the video “under contruction” load into kdenlive (no navigation thus necessary) after a crash.
Ok, I finished the video clip I planned. It turned out to be 11 minutes long.
I had over a dozen crashes in the process, but this is typical. I experienced far worse in Cinelerra and my wife experiences the same (maybe a bit worse) in MS-WinXP Movie Maker.
The crashes happened:
a. crash when I moved a large 10MByte image-clip (converted to a pan movie view) with a PIP transition (pip is to create the pan) to another video track. I had a few crashes due to this until I localized the cause-effect. The work around as noted above is NOT do do this. … simply remove the transition and then move the video, and then add the transition back.
b. crash when saving. This happened a few times. I save constantly (after every few clip insertions) … and it is hard to determine what caused the crash. I believe it is because the crash was still taking place, when I started dragging video clips around. I think one needs to let the save complete. (but I’m not sure if that was the cause ). I view this memory leak as very serious (I may raise a bug report).
c. crash when rending. This happened a few times. It appears the application “inigo” has a major memory leak. Rendering my 11-minute video had memory consumption soar from 13% (by inigo) to 52% (by inigo) when the rendering successfully completed. When it wasn’t successful I simply ran out of memory !! In a few previous crashes I had many other apps open (using memory) and my 2GByte RAM PC simply got low on memory. … I do not normally make 11-minute clips (rather I make many smaller clips) so this is the first time I have encountered this.
d. a few crashes when deleting a duplicate image clip. I had mistakenly input the same digital (still) image clip a second time. I deleted it from the timeline, but when I deleted a double entry from the project tree it would crash. The work around is to not delete this incorrectly displaying duplicate entry in the project tree.
e. a few other crashes that I can’t “pin” down. Typically they happened when I was rapidly adding transitions and draging videos around, … but they are different cases from item-a above, and I can’t sort it.
Coming back again to this topic. My computer is well competent, Dual Core Pentium 4 + 4 GB memory, so ot cannot be a performance issue. I updated kdenlive to its newest (0.6.0-2192.pm.svn20080520) and hoped to get some improvements. On the contrary, now it crashes immediately before I can even do anything. Error is:
mlt_repository.c, mlt_repository_init: failed to dlopen /usr/lib/mlt/libmltavformat.so
I tried to update/downgrade mtl with no results.
I have never used it either. My point was that it is very frustrating when I try to open a saved set, it then crashes. What could I do then? I once temporarely fixed the project xml file by removing one audio file by hand. The next time it happened, this technique did not work again.
BTW: I tried to edit with Cinelerra but it cannot handle partial slow-motion effects that virtually all my videos are made of.
You have something configured wrong. My PCs have a fraction (maybe 1/2 to 1/3) the memory/cpu processing yours have, and I can run kdenlive with no major problems. Definitely no crashes such as you described. You have done something to your system.
have you installed any “cutting” edge apps in the above? (I stick with the nominal basic openSUSE packages).
The only thing I can thing of to do is for us to compare versions, to see if we can see where you went astray. Thats a real pain (especially since its not my problem - my kdenlive works fine ) but since I’m a volunteer, I’m willing to help out here. So you need to check each of the above, post the version number, and I’ll compare it to what I have installed.
Also, if using kde3, you could remove you kdelive config file, and start from scratch. You can do that by renaming
/home/username/.kde/share/apps/.kdenlive to /home/username/.kde/share/apps/.kdenlive-old
I know a number of Mac users, and MS-Windows users (and even more Linux users) who use video editing software other than kdenlive.
All of them complain about the number of crashes. NOT ONE of them will state they have never had a crash, especially when their project starts getting bigger.
With my having tried more than a half-dozen different Linux packages, IMHO kdenlive is more stable than the other Linux apps. And with my having compared notes with my friends who use Mac and Windows video editors, kdenlive has similar behaviour wrt stability.
Now IMHO if you find a package Windows based, Mac Based, or Linux based, that gives you the stability you want, then use it. Be practical, and don’t let a preference for an OS sway your practicality.
I tried to compile the newest version from svn using a script but surprise, surprise it did not compile giving me bunch of errors. Since I was on a tight schedule (I needed my video by Saturday the latest) drastic measures were required. As much as I love openSUSE, I installed Kubuntu instead and it had kdenlive 0.6.0. I was very pleased to discover that this version is much more stable and I had the time to finish my video on time! I had several crashes all right but I was always able to recover the project file - the action that I failed on numerous occasions with kdenlive 0.5 on openSUSE.