[Kdenlive-devel] Re: Kdenlive start frozen...

[CAULIER Gilles]

Le Jeudi 13 Mars 2003 22:34, Jason Wood a écrit :
> On Thursday 13 Mar 2003 1:38 pm, CAULIER Gilles wrote:
> > Le Jeudi 13 Mars 2003 13:23, Reinhard Amersberger a écrit :
> > > kdenlive-devel at lists.sourceforge.net schrieb am 12.03.03 21:53:23:
> > > > On Wednesday 12 Mar 2003 12:55 pm, you wrote:
> > > > > Jason,
> > > > > It's not a i18n problem (French (:=))). I have the same
> > > > > dysfonctions in english mode.
> > > > >
> > > > > Note : compiled with piave and kdenlive source from actual CVS. MDK
> > > > > 9.0 with KDE 3.0.4 + Qt 3.0.5.
> > > >
> > > > I am not sure, but I think that Reinhard had a similar problem a
> > > > while ago, and solved it by updating something. I've sent this
> > > > message to the mailing list so that he will see it :-)
> > >
> > > My personal 'freeze' problem was solved by replacing the cvs version of
> > > libdv by the original one that comes with mandrake 9.0. At that time
> > > piave freezes when using pplay (utils directory), so as a consequence
> > > kdenlive freezes too, AND also kino freezes!
> > >
> > > Another solution could be to make a fresh checkout of both kdenlive and
> > > piave.
> > >
> > >
> > > greetings
> > > Reinhard
> >
> > Yes. Piave is problably the origine of Kdenlive freeze. I have rename
> > /usr/local/bin/piave to /usr/local/bin/piave.old -> kdenlive start
> > correctly... but it's not usable
> >
> > I will look the version of on my libdv at home.
>

At home, I have :

-> libdv2 release 0.98-4mdk
-> libdvdread2 release 0.9.3-2mdk
-> kino release 0.6-1mdk

Context : MDK 9.0 GPL. 

Piave (CVS) and Kdenlive (CVS) run correctly !!!

> Kdenlive should *not* freeze if the problem is to do with piave. If it does
> then there is a problem somewhere.
>
> Though I'd have liked to add keybaord shortcuts this week, the laptop I am
> currently developing on doesn't have a working build of piave yet (I need
> to install a few development packages), so I am tidying up the ways in
> which kdenlive reacts when a renderer isn't present. Amongst other things
> that I noticed, I have stopped messages from sent to the renderer if the
> renderer is not running :-) I think this might solve some problems that
> have been experienced, I'll commit at the weekend hopefully.

OK

>
> Cheers,
> Jason