Okay, so I am having issues rendering. I scanned other posts, of other people with rendering issues. Usually while rescaling, I am not rescaling, but it may not matter, I don't know because I don't know about these things. The final response for many of these problems, (im assuming the people who posted them solved their problems) is that it is probably an mlt memory leak bug. Then there is a link to information on the bug. Then . . . nothing at the link of any use to someone that doesn't know about these things. In terms that someone who doesn't understand mlt sourcecode could understand: How the hell do I fix the memory leak bug if it is indeed the memory leak bug that is causing my problem?

Thank you.

I would suggest you provide many more details about the specific issue you are having. Such as..
What kind of input videos you are using and what kind of output you are rendering. What happens and when (crash, doesn't play, gives error, etc). What system (ie. Fedora 11 64 bit or Ubuntu Karmic 32bit, etc....). Where did you get kdenlive from. What version of kdenlive? Does it happen on all formats, with/without effects, etc.. And more....
Without this information nobody can help you.
Thanks.

Im running Ubuntu 9.10 Karmic Koala. Its 32bit. I have Kdenlive 7.7.1. I installed it using the PPAs. I can render videos that are 30 seconds long with minimal effects. I cannot render longer videos with audio tracks added to them. I cannot render to any format. The rendering crashes almost immediately, then the project progress bar shoots up to 100%. My clips are from a HD camcorder that saves to AVCHD. I converted the files using WinFF to MPEG4s. These same clips render in shorter videos. The output on kdenlive when I try to render looks like this:

[mp3 @ 0x9cc6b40]mdb:225, lastbuf:0 skipping granule 0
Last message repeated 1 times [mp3 @ 0x9d018d0]mdb:225, lastbuf:0 skipping granule 0
Last message repeated 1 times [mp3 @ 0x9d4c120]mdb:33, lastbuf:0 skipping granule 0 [mp3 @ 0x9d3a040]mdb:33, lastbuf:0 skipping granule 0
[mp3 @ 0x9d9a640]mdb:33, lastbuf:0 skipping granule 0 [mp3 @ 0x9dc6420]mdb:33, lastbuf:0 skipping granule 0
Unable to parse option value "dv_ntsc_wide": undefined constant or missing (
Last message repeated 1 times [mp3 @ 0xa801000]mdb:225, lastbuf:0 skipping granule 0
Last message repeated 1 times [mp3 @ 0xa8754e0]mdb:225, lastbuf:0 skipping granule 0
Last message repeated 1 times [mp3 @ 0xa882650]mdb:33, lastbuf:0 skipping granule 0
[mp3 @ 0xa8b4f40]mdb:33, lastbuf:0 skipping granule 0
[mp3 @ 0xa8d37c0]mdb:33, lastbuf:0 skipping granule 0 [mp3 @ 0xa8ff5a0]mdb:33, lastbuf:0 skipping granule 0
[mp3 @ 0xa79a570]mdb:33, lastbuf:0 skipping granule 0 [mp3 @ 0xa79aac0]mdb:33, lastbuf:0 skipping granule 0

If someone could tell me how to render from the terminal, I could get more information, but I don't know how to run kdenlive from the command line.
Any thoughts?

Hello,

Do you mean this threat?
http://www.kdenlive.org/forum/cant-render-0771#comment-8247

One workaround is, to create a new render profile from the one you want to have, and to erase the option "s", scaling. In that case the video is rendered using the resolution that were set in the project options.

The bug appears when in the project options another resolution is set than in your render profile. So without option "s" the problem does not appears.

The workaround works for me for short projects (30 sec video), but not for bigger projects (5 min video; i tried only once). So i am not sure there were 2 problems, maybe both are solved in the MLT version 0.5.4, but it seems the workaround works not always.

Something sad is, it is not possible to add a comment, even as owner, to a bug report on mantis.

Oh, just another thing that worked always for me: i rendered with only one pass.
The output is not as good as the output with two passes, but that's life...

Hi shipp, It is unlikely that I will be able to help you since I'm not a developer and use Fedora 12 now instead of Ubuntu. However, some more info and tests might help you get information from someone here that has more knowledge on this. I can let you know that the latest 7.7.1 works very well on my computer right now and I have very few problems working with my HD mpeg (.m2t) files.

-Maybe you could post an example of one of your input files for others to try; both as AVCHD and your converted format.
-Try converting the AVCHD to some different intermediate formats to test.
-What kind of camcorder?
-Try deleting your .kdenliverc file and re-running config wizard in menu. (no idea if this would help or not, but if you've done upgrades seem reasonable).
-Are you sure it's not one or two specific problem files?
-File a bug report the kdenlive bug website.
-What version of mlt are you using?
-Where did you get the kdenlive packages?
-Provide more detailed error messages.

Let us know. Thanks.

I am not sure whether it will help you or not... but I stumbled across this tread as I was having a similar issue - rendering crashes no matter what format I chose.

I was getting errors like this:

Rendering of /home/fativan/test5.mp4 crashed
[mp3 @ 0x148c130]mdb:511, lastbuf:0 skipping granule 0
Last message repeated 1 times
[mp3 @ 0x148c130]mdb:511, lastbuf:0 skipping granule 1
Last message repeated 1 times
[mp3 @ 0x14b0940]mdb:511, lastbuf:0 skipping granule 0
Last message repeated 1 times
[mp3 @ 0x14b0940]mdb:511, lastbuf:0 skipping granule 1

After some investigation I couldn't find a solution... until I noticed that the default "output file" directory was incorrect - it didn't exist! (I started editing the video on a friend of mine's rig, and his user is called 'fativan'). I changed the "output file" directory on the "render project" window to a valid location, and now I am able to render stuff again.

I am not sure whether this is the same for you, but I thought it might point to something similar, or maybe a permission/quota issue? Perhaps this error occurs if the destination doesn't exist or you don't have permission to write there or something like that?

Can I suggest that kdenlive should validate that the user is able to write to the output directory/file and throw a bit more of a meaningful error if this is the case? I realise this was my fault... but the error doesn't really point to the cause in my case.

Anyway, hope this helps anyone who stumbles across this thread and has the same (simple) problem as me :)