[Bf-committers] Re: float-upgrade to sequencer (Ton Roosendaal)

[Toni Alatalo]

On Thursday 02 March 2006 12:11, Peter Schlaile wrote:
> > Having an entire NodeTree in a sequencer effect strip is possible, but
> > I'm not too fond of the idea still.
> Tell me a different way to have sequencer-tracks as input to the
> compositor and the result fed back to the sequencer.

what about having single nodes, like a colour correction, show as 
plugins/effects in the sequencer? then, with group nodes, which are like 
metastrips -- i.e. a box with many boxes (nodes) inside -- a more complex 
structure would also as a single thing in the sequencer (because a group node 
is also just a node)

i do apologize i did not really think that idea thru this example that you 
gave, gotta do other things now, but will be following you guys up on this 
later

~Toni

> Real world example: we want to do sophisticated color-correction with the
> compositor. It is rather clumsy to render the track in the sequencer into
> a movie file, then load it back in the compositor as input and feed
> that back again as scene-strip into the sequencer...
>
> (Not to mention the quality-loss or disk space used on this operation...)
>
> > I still like it that it's an integrated part of the render pipeline.
>
> Hmm. Maybe I still haven't understood this. Should we integrate the
> sequencer completely into the render pipeline (nice idea) or do you think
> adding an compositor effect to the sequencer will somehow kill the
> compositor-design?
>
> > Or, just putting back the Scene strip in sequencer (temporally disabled,
> > will do... :) also will give the composite features as output.
>
> Output works this way, yes, but the problem is, that input doesn't work!!!
>
> Greetings,
> Peter
>
> ----
> Peter Schlaile <peter at schlaile dot de>
>
>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers