Hi, I sent a message to Charles Yates a week or so ago, after reading a post on kino-devel where he mentioned he had been pushing for a client/server arrangement in later versions of Kino. I recieved a reply yesterday saying that he might be interested in collaboration. Below are his reply and my initial post.
Cheers, Jason ---------- Forwarded Message ---------- Subject: Re: Kdenlive (was Re: Proposal for Kino-Development - libkino) Date: Sunday 02 Feb 2003 6:52 pm From: Charles Yates <[email protected]> To: Jason Wood <jasonwood at blueyonder.co.uk> Jason, Sorry for the delay in responding - had a couple of busy weeks here (and then kinda forgot about your mail :-/). Yes, I am always interested in collaboration with existing projects - I'll have a look at you kdenlive sometime during the next week (time allowing) and write a more detailed mail later on. Once again, sorry for the delay. Cheers, Charlie ------------------------------------------------------- ---------- Forwarded Message ---------- Subject: Kdenlive (was Re: Proposal for Kino-Development - libkino) Date: Thursday 23 Jan 2003 12:08 am From: Jason Wood <[email protected]> To: Charles Yates <charles.yates at pandora.be> Hi Charles, I'd like to introduce myself. I am the developer of Kdenlive, a non-linear video editor for KDE (links at the bottom of the page). I took notice due to the following parts of your post: > I've also been pushing for a non-gui core system and have recently > started thinking about a client/server arrangement for this (inspired by > another project that Dan and I are working on at the moment). and > I definitely want to encourage reuse and the idea of a network > abstraction appeals to me... there are other implications regarding the > use of devices that would be resolved with such an architecture too. Now to explain myself :-) You see, calling Kdenlive a video editor is a slight lie - Kdenlive is a non-linear editing GUI front end that manages project management, clip manipulation, effects (well, it will when it is coded), etc. It relies on a seperate rendering engine (piave by Rolf Dubitzky) to perform all playback, rendering, effects, etc. The two applications communicate with each other via a client/server arrangement... does this sound like a familiar idea? I am very interested in the idea of having multiple GUI's and multiple rendering engines which can be mixed 'n' matched to fit the users personal preference and needs. Does this idea appeal to you, would you be interested in seeing if we have enough common ground in our ideas to be able to work together on this to make Kino (if it becomes client/server) and Kdenlive/Piave compatable with each other? Cheers, Jason Kdenlive: Homepage : http://www.uchian.pwp.blueyonder.co.uk/kdenlive.html Sourceforge: http://sourceforge.net/projects/kdenlive/ Piave: Homepage: http://modesto.sourceforge.net/piave/ Sourceforge: http://sourceforge.net/projects/modesto ------------------------------------------------------- -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
