On Thu, 2008-03-27 at 00:36 +0100, [EMAIL PROTECTED] > Can you get it to work better if you turn off background rendering? > -- Hannes > Turning off background rendering doesn't seem to make any difference.
> Anne, > I wonder if it is a corruption somewhere in the XML. Can you open a > second instance of Cinelerra, create a new project with the same > settings, paste in your video and keyframes from the first instance, > save it under a new name and then see if the new project crashes? > > Awhile back, I had a problem where the XML EDL file became huge > (>2MB), with a bunch of repeating tags. Normally, the XML should be > pretty lightweight (<200K). What size is it? > > scott My xml file is 470K, but it's a pretty densely edited half-hour project, and I haven't noticed a huge amount of repetition in the code (but I've only skimmed through it) The problem is less that it crashes and more that it won't re-open afterward... but I can give it a shot. Usually when I finally have it open I just want to get some work done! > Hi, have you already tried with a fresh ~/.bcast ? (i.e. moving or > deleting ~/.bcast before starting cinelerra). That often seems to > resolve weirdness. > > -- > goibhniu Deleting .bcast allowed me to open my project again, but I'm not sure it'll fix the problem for good. Any idea which file in there might be likely to screw things up? (so I don't need to keep rebuilding index files) Thank you all for your help, Anne -------------- Original message ---------------------- From: Anne Tennies <[EMAIL PROTECTED]> > I'm having trouble reloading my current project after cinelerra crashes > -- and sometimes after I close it normally -- regardless of whether I've > saved my file. Sometimes I can get it going by manually editing my .xml > file to close tags (label, brightness), but that's not always a problem. > I end up trying a bizzare combination of opening the .xml in a text > editor and saving it (sometimes adding and deleting a space so it > changes a little), opening a different project in cinelerra first and > then trying again, and checking my system monitor to make sure I don't > have any traces of the program still open. Eventually, I can usually > coax it to open so I can get more work done, but if anyone has a better > idea, I'd really appreciate the help. > > I'm running Ubuntu Gutsy on an Athlon 64 3500+, and it was tricky enough > to get cinelerra running right that I'm reluctant to update/upgrade > until I finish this particular video. > > In the terminal, as soon as I see the 'run 1 killing pid' line, I know > it's not going to work, even though cinelerra will stay open for days > and say it's loading (if I let it) > _____ > > [EMAIL PROTECTED]:~$ cinelerra > Cinelerra 2.1CV Wed Sep 27 20:49:50 CDT 2006 SVN Version 905 (C)2006 > Heroine Virtual Ltd. > > Cinelerra is free software, covered by the GNU General Public License, > and you are welcome to change it and/or distribute copies of it under > certain conditions. There is absolutely no warranty for Cinelerra. > BRenderThread::start 1 map=11842695 equivalent=0 brender_start=14783 > result=14783 end=14783 > RenderFarmClient::main_loop: client started > RenderFarmClientThread::run: Session finished. > BRenderThread::start 1 map=14783 equivalent=0 brender_start=14783 > result=14783 end=52109 > No accelerated IMDCT transform found > No accelerated IMDCT transform found > RenderFarmWatchdog::run 1 killing pid 9809 _______________________________________________ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
