[Kdenlive-devel] Another commit and time to start mentioning piave bugs ;-)

[Rolf Dubitzky]

On Monday 10 February 2003 12:42 am, Jason Wood wrote:
> Finally, here is a very reproducable bug on my computer - The piave
> workspace monitor appears for a couple of seconds, and then crashes.

Hi Jason,

 yes, piave HEAD is very unstable at the moment :-(. It's not so easy to 
debug, since kdenlive doesn't work at all for me right with piave installed. 
If I don't have it installed, kdenlive works sometimes, but very frequently 
it will start, and imediatly freeze. No reaction to neither mouse, nor 
keyboard. Unfortunately, with piave installed, this happens in 95% of the 
cases. I am not realy able to debug, because I don't get a scenelist. In the 
few cases where kdenlive doesn't freeze imediately, none of the two piave 
processes receives a <setScenelist> command. There should be two ways to make 
kdenlive send <setScenelist>, right? 
a)  add clip to project list.  double click the file. 
      shouldn't that display the first frame of the file in the clip monitor?
      it doesn't right now for me.
b)  insert the clip to the timeline ...
      this doesn't work at all for me right now. when I try to d'n'd a clip 
      from the project list to the timeline, the clip doesn't 'drop' i.e. the 
      small square that is displayed next to the mouse coursor just stays 
      where it is and nothing else happens. no clip in the timeline.

After these freezes I see _many_ processes like this 
kdeinit: kio_file file /var/tmp2/ksocket-dubitzky/klauncherBjP76a.slave-socket 
/var/tmp2/ksocket-dubitzky/kdenliveeaQfpa.slave-socket

That's probably normal?

I started seperating the xml parser from the kdenlive part inside piave. Then 
I will be able to feed VEML files to pplay. That way I will be able to test 
piave without having to startup kdenlive and it'll be a usefull feature 
anyway.

Can you/anybody reproduce this freezing and/or d'n'd not working? 

I commited many changes to piave anyway, some bugs are fixed, but I couldn't 
check if it works. Just for testing, I replaced the "empty frame" (the frame 
which is displayed, when nothing else is specified for a given time) to red. 
just so that I can see something happen at all, don't be surprized.

Cheers, Rolf

P.S.   Since I wasn't able to realy check it out, I am not sure, but I think 
that the effect list and the effect setup should be visible at the same time, 
no?

PP.S.   kdenlive always crashes on exit:

 QSocket::writeBlock: Socket is not open
 QSocket::writeBlock: Socket is not open
 QSocket::writeBlock: Socket is not open
 KCrash: crashing.... crashRecursionCounter = 2
 KCrash: Application Name = kdenlive path = <unknown> pid = 4161
 Alarm clock


PPP.S.   I removed all dependencies to libxml++. I wanted to update to the 
last version, 0.18.0, that was easy enough, but the next day, there was 
already 0.19.0 and that depends on a version of libxml that wasn't even 
installed on my RH8.0 box!! I got tired of that crap and am now using libxml 
directly, no crappy C++ wrappers anymore.


***************************************************************
 Rolf Dubitzky  
 e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de
 s-mail see http://hep.phy.tu-dresden.de/~dubitzky/
***************************************************************