[Bf-committers] compositor-effect in sequencer

[Ton Roosendaal]

Hi,

I don't think this is a working design (not disputing the fact it would  
be nice!). The compositor is really an extension to the existing  
rendering pipeline, optionally allowing input of images too. I'm  
especially talking from the experience we have in the orange project,  
the compositor allows imaging/rendering beyond anything what was  
possible before, and/or what we had to abuse the sequencer for in the  
past.

The sequencer is also still in use here, this to edit and review the  
'final edit' of the movie. The sequencer works great now thanks to a  
friendly memory consumption scheme, and gives us near-realtime editing  
and viewing. This is the best feature of the sequencer.

This I think is a good core definition of functionality of both systems  
in Blender. This focus also is based on creating animation work, not on  
using the sequencer for editing video, or for using the compositor for  
only editing images for the nice 'custom effects'.
The fact it can be used for this is a nice extra, but secondary.

In the past Blender has always benefited from keeping a clearly  
designed separated functionality for parts, this gives the artists  
clues for an efficient workflow.
For example; the compsosit pipeline is still relative slow, and could  
get work on making this tile-based. There's also need for better  
visualization. All of that work I like to do customized and focused on  
the render/composite pipeline and workflow.

Same goes for sequencing. If you need complex edited effects that take  
minutes (hours) of rendertime, you're better off to render all of that  
in advance first, and use it as input for the sequencer.
The (still acceptable) exception could be to use the "Scene" strip in  
the sequencer, which will also allow you to make full use of the  
compositor. But, by using the scene only, the functionality of both  
systems will still be clearly separated.

-Ton-


On 5 Mar, 2006, at 23:59, Peter Schlaile wrote:

> Hi,
>
> I played a little bit with the compositor this afternoon, and collected
> the following ideas:
>
>> From the perspective of the sequencer the compositor enables us to  
>> create
> custom-effects. I propose, to generate an additional  
> compositor-pipeline
> "Sequencer-Effect-Nodes" (as an addition to material and "regular"
> compositors) that has in _addition_ to the "regular" compositor
>
> - two input-nodes (will serve as input of the effect filter)
> - one output-node (will serve as output of the effect filter) as well  
> as
> - one or more Sequencer-IPO-input-nodes (one in a first stage
>   implementation).
>
> It should be possible to save these pipelines by name (just like the
> materials) and have these pipelines show up in the effect-plugin  
> window of
> the sequencer by name.
>
> That way, one can build filter-pipelines and use them several times on  
> the
> same sequencer timeline. They can then all be controlled by IPOs. (In a
> second stage, one should be able to add more IPO-channels to have a  
> more fine
> grained control of the parameters in the compositor-effect).
>
> One could add more input nodes, but I do not think, that this makes  
> things
> very transparent to the user of the final effect-filter in the  
> sequencer.
> (Nevertheless, it would be very easy to add this feature afterwards...)
>
> Please let me know, what you think about it.
>
> 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
>
>
------------------------------------------------------------------------ 
--
Ton Roosendaal  Blender Foundation ton at blender.org  
http://www.blender.org