-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 gord campbell schrieb: > I would never try to use a large number of files, you're just asking for > trouble. I would break the project into pieces, with maybe eight files per > piece. Load the eight files, do your editing, render a file. Repeat 20-odd > times.
> Then I would aggregate five pieces, render the result, repeat three more > times. Finally, pull it all together -- if you actually need to. Hello gord campell, Hello Adam, basically I agree, but only with regards to the length and complexity of a single timeline. I did large projects in Cinelerra, e.g. one contained about 30 hours of HD MPEG source material as assets. Having assets in the project in itself doesn't cause problems. But having longer and more complicated timelines with lots of tracks, objects automation and effects increases the possibility to get into an unstable state. Regarding the loading of MPEG: Why do you rely on Cinelerra to generate the index files automatically? There is a small executable called mpeg3toc, which is built and installed alongside with Cinelerra. Is purpose is to generate the index file (*.toc) offline. So, instead of just dropping in MPEG files and force the resource consuming process of index generation on Cinlerra, just use this mpeg3toc to generate the *.toc files, possibly overnight with the use of a shell script. After that, you can just load the *.toc files instead of the mpeg files. This always worked for me almost immediately, and seemingly without any limitations on the size. hope that helps Cheers, Hermann V -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkwToH0ACgkQZbZrB6HelLLqRwCg8L1qQvwNSnYGx+1DJmtyrRbp 04MAoN5zYz/PEfv78NyKMC1272w8BW68 =eqWs -----END PGP SIGNATURE----- _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
