-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> lör 2008-05-24 klockan 13:12 +0200 skrev Sami Kallinen:
>>> better!  I am for example interested in using a more "Nodal" type
>>> approach
>>> such as employed by the Smoke or Flint workflow.  As long as it's an
>> just curious do you mean "nodal" as in "rooms", "areas" and "modal
>> operation" or nodal as in shake, pd, quartz composer and flame? if
>> the latter, it has been mentioned here a few times but i struggle to
>> see the advantage of that in editing besides of filters and effects.
>
Martin Ahnelöv schrieb:
> AFAIK, this is what's being aimed at. Also, people have expressed that
> they would like to see sub-timelines (sequences in FCP-terms).
>
> Gasten


Hi all,

probably I could help clarifying this questions a bit :-D
(1) yes, internally Lumiera works completely nodes-based and uses pull
    rendering as a paradigm. We just haven't settled down in any way
    about the question how much of this will be visible to the user
    at which point, and -- more importantly -- in which way (s)he
    may be able to deal with it, without loosing the view of the
    "big picture". Any discussion on this subject is welcome.

(2) yes, Lumiera is planned to have several EDLs (we stick to Cinelerra
    terminology here). Each EDL is a collection of clips, effects,....
    arranged on a track-tree along a timeline. According to the current
    state of planning and (on my behalf) started implementation, any EDL
    can appear as "meta-clip" placed within another EDL. (we have to
    detect cyclic dependencies and flag them as an error, though)...

Cheers,
Hermann V.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIOfzfZbZrB6HelLIRAqpfAJ94HxIzSLLioxMK+Vvsf19ZxIqQBQCg8CsF
qv2l0sI+y+LAA/0AMEMpYDs=
=Oxvk
-----END PGP SIGNATURE-----

_______________________________________________
Cinelerra mailing list
[email protected]
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra

Reply via email to