On Mon, 2006-05-15 at 08:33 +0200, Piotr Legiecki wrote: > Alex Ferrer wrote: > > > Since cinelerra (or any other NLE for that matter) refers to source file > > for its cuts, audio etc.. it would be of no use to "just" copy what is > > being used. > > When you came back to revisit the edits, you would not have all of the > > original material to be able to change a cut. (like extending a clip or > > other) > > I assume this backup as final, ie no further edits. It is frozen > project, kept just for regenerating to any format cinelerra offers. >
Or perhaps regenerate to improved formats. I've been silently monitoring this list for a while but this topic is dear to me. I find the managing projects with cinelerra is still difficult. The source files, index files, xml files are typically dispersed in a number of places and difficult to isolate for separate projects. My current solution is to create a "user" associated to projects and set its home-dir to a project directory. Then at least, I have one filesystem to backup. I also maintain a Makefile, which removes many of the tmp files I create during the redenring process (since I batch everything). So what's my point? A backup is good for saving source, but should also include all the other project components REQUIRED to get cinelerra back up and running/editing. Whether or not the backup includes all original DV source or just the "used" bits, could be a option on the backup dialog (could even give you a estimated size calculation). A minor detail in my opinion. Restoring a backup should also be "relocatable", meaning that the indexes, xml, etc... are all updated during the restore to reflect the new location. Just some thoughts I hope are useful. Maybe I should start writing some code myself. Cinelerra is written in Fortran right? ;-) -christoph _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
