On Fri, 2007-08-10 at 12:06 +0100, mark carter wrote: > On Fri, 2007-08-10 at 12:33 +0200, Herman Robak wrote: > > On Fri, 10 Aug 2007 11:31:12 +0200, mark carter <[EMAIL PROTECTED]> > > wrote: > > > > > > A thought: when you load a file in with iMovie, it actually "imports" it > > > - converting it into its own format (quicktime, or whatever). > > > > I find this behaviour REALLY annoying, especially for the kind of work > > I usually do; doing simple edits on very long recordings. > > > Hmmm. Let me ask these questions then: > * what is the file format that Cinelerra is most robust with?
I use DV-encoded .avi files. I'd like it if it had huffyuv support for working with small video files captured from analogue support. Maybe it does, but I've never got it to work > * what file formats do the "pros" use? Is there a wide range, or is the > scope restricted? Don't know, I'm not a "pro" ;-) > * So how does Cinelerra work: when I see an image in the compositor, for > example, is that a rendering of a so-called VFrame? And how is that > VFrame produced - is it produced "on the fly" from the underlying file > format, is it rendered from a small look-ahead cache produced from the > file reader, is the whole file converted to a list of VFrames which are > then just rendered as needed, or is it "none of the above"? I'm really > stuck on the fundamentals. As I understand it, it precaches images either side of a keyframe. Gordon _______________________________________________ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
