On Fri, 2008-06-06 at 13:47 +0200, Kurt Georg Hooss wrote: > well... erm... sorry i don't understand. that's really compact. > maybe there is some really smart sense in it, so it could be worth > that you please elaborate a bit for dummies like me.
> > http://thorwil.wordpress.com/2008/06/04/containers/ Think of the folders, files and folders within folders on your harddrive. In short: a tree. Now the container concept is about showing such trees in time, where each element has a start time and duration. As the horizontal axis is tied to time, members can not be entirely surrounded by their containers, so I had to think of graphical concept that deals with this. It's just like: (animals(dogs(husky)(collie)) but expressed vertically. The same as tree: animals - dogs - husky - collie Now these containers could be used - to group objects. For example, if you import a video that has stereo audio, you'd get a container with 1 video and 2 audio streams in it. So you could move and cut the whole thing, or move and cut the streams independently. - as patterns: make linked copies of containers - to do sub-mixes: do layer-wise compositing per container - express transport scope: everything in the container shares a playback position, a transport state (playing or paused ...) - set a time reference. wrap up objects in it it make time move slower of faster for them. For doing nodes/graphs: Representing nodes and connections on the timeline allows to have processing graphs changing over time. Containers can wrap them up to have patches (path = graph of nodes, where each node is either a plugin or another patch). -- Thorsten Wilms thorwil's design for free software: http://thorwil.wordpress.com/ _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
