Anne Tennies wrote: > 1. Has anyone figured out how to display audio waveforms when they're > not showing? I get to a point in my projects, and the audio flatlines, > despite having 'draw media' selected. If I notice it disappear I can > hit undo and get it back, but that doesn't help if you never see it in > the first place.
Not sure. The only thing I can suggest is that perhaps you aren't allowing sufficient space for the directory which holds the index files (configured somewhere in the preferences). If this is too small I guess it's possible that some index files in use might get deleted as other media are added to a project. It wouldn't have to be the same project either; if you had two projects (A and B), did work in A for a while and then swapped to B to do some things in that, it's possible that adding clips to A might cause index files used by A to disappear - and then you do get flatlines in your audio waveforms. Having said that your symptoms don't exactly match this scenario. However, it might be worth checking anyway. > 2. After cinelerra crashes I usually can't reopen my project file > without rebooting. The main window shows audio waveforms but no > thumbnails, the compositor shows labels, and neither viewer nor > compositor shows video. Meanwhile the mouse pointer keeps spinning away > and never fully loads the file. Sometimes it'll sit there thinking for > days (if I let it); other times it crashes after a few minutes (see > below). Any thoughts? Only that under heroine's CV I've noticed similar problems on load from time to time. For me it seems that cinelerra simply locks up part-way though loading a project. The precise point of the lockup isn't consistent. I've had lockups when: * no media has appeared in the resources window at all * some or all media has appeared in the resources window * some timelines have been drawn in whole or in part I don't have to reboot to get a successful load however - I just ctrl-C and try again; usually I get a successful load after one or two attempts. I've never left things long enough to see if cinelerra actually crashes out of its own accord. Circumstantial evidence from tests I've done suggests that having "draw media" activated makes the bug more likely to trigger. For me the problem first appeared after I upgraded my machine to Slackware 10.x from an earlier version of Slackware (sorry, can't recall the versions off-hand) and upgraded Cinelerra to v2.1. Thus I can't be sure whether it's a problem triggered by cinelerra 2.1 or the newer glibc which is now in use. In any case, if I had to take a stab at what is happening I'd say there is some kind of race condition or locking error between the thread which reads the project in and the code which draws the media. Machines I've seen this on are an 866 MHz Pentium3 and a 2 GHz Centrino (Dothan) laptop. > FYI, while it was stalled, the terminal only showed the first few > lines... everything after 'signal_entry' showed up after the program > crashed again. I'll see if I can dig up a dump from one of my ctrl-C events; that might show whether we're talking about the same bug. Martin Ellison wrote: > > I have a 2GB Athlon 64 3500+ and I'm running Cin 2.1CV ... > I am detecting a pattern here? In regard to what? The use of Athlon-64? I can't say, except to point out what I've written above. Regards jonathan _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
