Bug forum was closed so that's why I am posting here...

I have been trying KDEnlive from SVN some days now and I find that it doesn't handle all files well (in other words; a crash!) Sometimes it does work when I cut the file in smaller parts and load them, sometimes it's just a bad coded file I guess.

Question 1 - what's the best way to file a bugreport for this situation? Posting 'my 200mb avi file don't work!' isn't going to help much, so what information should I put in? Testing it with inigo or ffplay, ffmpeg format output etc, just name it guys.

Question 2 - what are the most stable formats to work with? I don't mind filing bug reports but knowing how to get something done without crashtesting would also be nice!

1. Most important thing is to file the GDB output and your version numbers. How do you get this gobbledegook? Well, if you built Kdenlive with the builder wizard it's easy. :) Just run Kdenlive with the kdenlive_start.sh script and choose "GDB output" option from the dropdown menu that pops up. Then if Kdenlive crashes you'll get a nice, detailed log you can attach to a bug report that gives a lot of useful info.

2. Regarding stable formats, I've found that .dv and .m2t (HDV) formats seem very stable for me. I'd guess this is because Kdenlive uses MLT which originally came from the venerable Kino which only supported DV. Anyway, I work with many gig of DV / HDV and it works well for me. Frei0r effects, title clips and luma wipes in slideshows seem to be the main wonky bits at the moment, but development is going on at a breakneck pace in SVN right now so I suspect a lot of this will be cleared up before "Kdenlive Tuesday"... ;)

Re issue 1)

Output from ffmpeg -i filename is always good

If kdenlive does not playback, we will want to know if ffmpeg and inigo does.

So basically you are on track.