yeah, that is what I was thinking, and maybe not what Thorsten (the OP) was thinking. I think....

A typical DVD has a main movie, special features, trailers. the main movie has chapters, angles, sub titles, multiple audio tracks. I can see how you would want that collection to all be in the same project.

Previously I was thinking that this container would be a way of collecting many inputs and having one output. one container can contain other containers.

video effects would all be containers. They would contain the clips that the effect effects. one of the simplest containers would be concatenate a list of clips/containers.

Perhaps a container is the place to store render parameters.

Carl K


Martin Ellison wrote:
I think Carl is looking more at organising inputs and work in progress
rather than outputs. The final output has an organisation given by a tree of
EDLs. However, that still needs ways of organising all the input assets and
then to keep track of partial results such as EDLs of individual scenes.
[Actually, what do you call something that is longer than a shot but shorter
than a scene?]. Carl, is this right?

2008/6/10 Ichthyostega <[EMAIL PROTECTED]>:

Thorsten Wilms schrieb:
There has been discussion in #lumiera. Instead of containers there will
be meta-clips. A clip is just a collection of audio and video streams to
go together. A meta-clip can contain clips and other meta-clips. In the
timeline each meta-clip will just show the result/mixdown of its
contents. Meta-clips can then be opened in another panel/tab/window.
...to make it a bit more clear: a meta-clip is a complete EDL (or
timeline if you prefer this term), which is placed into another EDL
and appears there like a simple clip. It can even be cut like a
normal clip within this target-EDL. The only limitation is that we'll
detect circular references and flag them as errors.

But it seems it's not quite clear if routing shall happen on a per track
or a per object level or even both.
In this discussion, we talked a lot about the routing via track, because
this is considered the default approach. But to my understanding, you'll
be always able to make direct connections per object explicitly to
override the automatic routing via track. Moreover, while a normal clip
pulls its input from a source reader (i.e. it reads and decodes a media
file), you can fed the output of some clip (or meta-clip) explicitly
to the source input of another clip.

Hermann V.



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





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

Reply via email to