[Kdenlive-devel] moved here from kde-multimedia (was Re: Multimedia Frameworks)

[Christian Berger]

Am Montag, 28. Oktober 2002 15:11 schrieben Sie:
> On Monday 28 Oct 2002 11:15 am, Rolf Dubitzky wrote:
> > > > I don't like the idea of threads for a number of reasons :
> > > > Firstly, if the Cutter crashes, it will take the GUI with it.
> > > > Secondly, we would still have to allow the Cutter to run as a
> > > > seperate process so that it could be run remotely or for batch
> > > > processing anyway. Thirdly, it would really screw up my idea of
> > > > having a scheduler for multiple cutters distributed on multiiple
> > > > computers ;-)
> >
> > Ok, I don't want to get envolved with multiple computers too much,
> > because that's my major. But if we want to test this on a 500+ PC
> > cluster at some point I can do it. But using a PC cluster to render a
> > movie is trivial. The task is intrinsicly parallel if you can make the
> > cutter read a XML file and launch it with gst-launch. You just have to
> > tell everybody which frames to render and have a seriealizer in the
> > end. That's what I do all day ;-)
>
> I think the main problem with video rendering over a network is more a
> case of bandwidth - To edit at DV quality, you are looking at 3
> Meg/second AV files, (30 Meg/s or more for some of the more
> "professional" codecs ) which I think could quite easily saturate the
> network.

Well we are talking about _off_line video editing. Besides nowadays 
networks are almoust as fast as harddisks. (whoever can afford raids for 
hight speed harddisks also can afford Gigabit Networks)

> The idea I am playing with at the moment is along the lines of :
>
> Each individual computer would have it's own "local cache" of video
> files. The scheduler would know which files each cutter has, and would
> assign tasks to minimise traffic over the network.

Yes, for example we can schedule simple scenes to the computers with the 
fastest access to the scenes. And more complex ones to computers with 
faster processors.

> Previewing and playback would generally only occur on the GUI computer.
> Potentially, multiple GUI's would be connected to the network and the
> scheduler would assign cutters between the GUI's as necessary.

Well here the GUI could simply issue a request and the local cutter will 
probably take it.

> However, I should point out that I am not at this moment in time really
> looking into network rendering - but I don't want to have to rework the
> entire code base when it comes round to implementing it.

Exactly, but I do not see a problem if we have a simple cutter which can 
simply cut a scene.

> Cheers,
> Jason

Servus
  Casandro

-- 
Warning! (this is no commercial ad)
This e-mail probably will be read by secret services.
Therefore please get pgp or gnupg and send me 
your public key so we e-mail encryptedly.
http://www.gnupg.org/