On Wed, Mar 10, 2010 at 6:27 AM, el jefe delito wrote:
>> I must admit I had a hard time choosing between Kdenlive and OpenShot.
> An unlikely request, but since both OpenShot and KDEnlive use MLT on the
> backend, I would think that it would be beneficial to the userbases of each
> if the files
Can I just chime in and suggest implementing an importer/exporter for an
existing standard such as the Final Cut Pro XML Interchange Format for
importing/exporting projects, rather than devising a new one that would be
used only by KDL/OpenShot:
http://developer.apple.com/mac/library/documentation
AAF would be another good choice:
http://aaf.sourceforge.net/
On Wed, Mar 10, 2010 at 9:43 AM, Tim M wrote:
> Can I just chime in and suggest implementing an importer/exporter for an
> existing standard such as the Final Cut Pro XML Interchange Format for
> importing/exporting projects, rathe
OpenShot recently added the possibility to import Kdenlive projects but it
simply adds the whole project as a clip, so it's not quite as useful as what
you suggest. I haven't had a look at the openshot file format, but it most
likely would also be an xml file, so converting between one format and t
On 03/10/2010 08:27 AM, el jefe delito wrote:
>> I must admit I had a hard time choosing between Kdenlive and OpenShot.
>>
> An unlikely request, but since both OpenShot and KDEnlive use MLT on the
> backend, I would think that it would be beneficial to the userbases of each
> if the files
> I must admit I had a hard time choosing between Kdenlive and OpenShot.
An unlikely request, but since both OpenShot and KDEnlive use MLT on the
backend, I would think that it would be beneficial to the userbases of each if
the files created in one application could also be used in the other. C
