search

google-code-export / flowblade

Automatically exported from code.google.com/p/flowblade
1 stars 0 forks source link

import of kdenlive project #15

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Flowblade opens the project file saved in kdenlive (as flowblade is also based 
on MLT). But it shows the full sequence as one single clip, and it makes 
difficult to further manipulate. It would be helpful if flowblade splits those 
clips. So that i can import all my kdenlive projects into flowblade.

Original issue reported on code.google.com by mohan...@gmail.com on 22 Aug 2012 at 7:03

GoogleCodeExporter commented 9 years ago 
This will unfortunately have to go WontFix as the needed work/versus benefit 
ratio is not good enough.

I'm also really surprised how Flowblade opens kdenlive projects at all.

Original comment by janne.li...@gmail.com on 23 Aug 2012 at 8:48

GoogleCodeExporter commented 9 years ago 
because flowblade is based on MLT right. Then MLT's open XML architecture is 
same for every app that uses MLT, Hence i could import kdenlive, openshot saved 
XML project as footage in flowblade.

Original comment by mohan...@gmail.com on 24 Aug 2012 at 4:49

GoogleCodeExporter commented 9 years ago 
Openshot and KDEnlive save projects in XML, and could in principle open each 
orhers project files.

I'm using python pickle -module and saving projects as serialized python 
objects. Despite this I tried to open the a KDEnlive project but the file 
dialog didn't even see it, because it is filtering for Flowblade project files.

Original comment by janne.li...@gmail.com on 24 Aug 2012 at 11:28

GoogleCodeExporter commented 9 years ago 
No, Try importing it as footage, and not as project file.

Original comment by mohan...@gmail.com on 25 Aug 2012 at 4:46

GoogleCodeExporter commented 9 years ago 
Holy hell, it did open it! Thank you for bringing this to my attention. 

I knew that MLT/melt had some XML serialization mechanism, but I didn't realize 
that I could import the resulting files as a Mlt.Producer. I'll have to 
consider how I make this functionality more apparent to user.

KDENlive save system seems to be using this MLT system, or probably is a 
compatible super set of it, don't know exactly.

I'm still going to keep your request as WontFix, sorry, because interpreting 
KDEnlive projects well enough to put the cuts back in would require maybe 4 
times MORE lines of code then my own save system takes.

Original comment by janne.li...@gmail.com on 25 Aug 2012 at 10:32