-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Doug,
thanks for sharing your detailed insights and experiences. Personally,
I think I am much in line with your findings. Having a visual clue about
the "beats" of a project can be very important.
As a sidenote, frequently I hear people state that reading a musical score
distracts from the real music and emotion. While surely you can't find the
emotion in the score without understanding the music anyways, the general
statement is not quite true. By skimming through a musical score you can
get an almost instantaneous picture of the whole piece. Same is true for
well done raw film footage: By fast forwarding or by scrolling over a
thumbnail view, you can get an intuitive understanding of the rhythm,
the important parts, etc.
Your statement about transitions sounds interesting too. While generally,
I get the impression people want plugins-plugins-plugins plus 10 million
presets, my own experiences point in the contrary direction. I think,
it is much more important to have a small number of rather low-leveled
building blocks, sort of working tools, with the ability to handle them
very convenient an fluently. For most of the day-to-day work, I use only
- - fade/pan
- - contrast+color correction / parametric EQ for sound
- - sometimes a gamma curve tool
- - a general purpose compressor for sound
- - mask
- - blur (gaussian, directional) (and would need noise too, maybe colored noise)
- - unsharp mask
- - simple dissolve transition (sometimes a simple horizontal wipe)
- - layer ordering and (normal, additive, subtractive) overlying,
camera+projector
I'd love to have the ability to create my-personal-tools-and-plugin selection
and to remove all those other plugins, transitions and effects I don't need,
and save this selection in my project or project template. Then I'd love
to be able to group into a small number of tracks the curves controlling
those parameters I need . It would be nice if you could configure for each
parameter if it's shown as overlay or put into a separate track.
Well, that are my preferences -- I am not the one to implement the GUI
(because I concentrate on the middle layer of the new application which
organizes the various elements and objects in a session and carries out
the editing operations sent down from GUI).
But at least I can tell you that we are well aware of that "preview problem"
and strive to build the new application right from start such that the way
how to render previews/output is organized rather cleverly. If it took several
minutes to render a sequence with a demanding effect stack, the system shouldn't
throw away those frames just because you trim the end of the preceding clip.
(Well, that's a bit of a challenge, but it should be doable if we care to
have it work this way, and it could be a "selling point" for the new App...)
Hermann V.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHt6ijZbZrB6HelLIRAsZ3AJ49qDZ0a5jSmyFWw3ap7Qb7wfEqeQCg5Czr
oFhMzgfLdhVhsaMieBEK0t4=
=JW/o
-----END PGP SIGNATURE-----
_______________________________________________
Cinelerra mailing list
Cinelerra@skolelinux.no
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
