<div dir="ltr">So skipping the idea to mix VSE and compositor is it feasible to think about a better way to manage input sequence in the compositor?<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
2014-05-23 18:21 GMT+02:00 Ton Roosendaal <span dir="ltr"><<a href="mailto:ton@blender.org" target="_blank">ton@blender.org</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all,<br>
<br>
Sequencer is currently not in active development, we try to bring that back in control, which might take many months or more even.<br>
<br>
However: Compositor and Sequencer should be kept as seperated functional parts in Blender, it helps design focus and it mimics how workflow for animation/vfx film works in general.<br>
<br>
(You can find long debates on this in many places, I suggest everyone here to inspect that as well and not do this all over again.)<br>
<br>
In short:<br>
<br>
- Compositor is a real-time editor for frames, to make a shot.<br>
- VSE is meant to be a real-time editor for shots, to edit/grade a (short) film or sequence.<br>
<br>
The compositor unit is a frame, the VSE unit is a shot.<br>
<br>
Design focus helps to remind everyone what always should work, and it defines what kind of work should be done to improve it. These editors should work together well, and there can be overlap in parts even. But we keep them separated well.<br>
<br>
Whether or not sequencer should get blur or nodes is quite irrelevant now, and will come back later when VSE is back in active support.<br>
<br>
-Ton-<br>
<br>
--------------------------------------------------------<br>
Ton Roosendaal - <a href="mailto:ton@blender.org">ton@blender.org</a> - <a href="http://www.blender.org" target="_blank">www.blender.org</a><br>
Chairman Blender Foundation - Producer Blender Institute<br>
Entrepotdok 57A - 1018AD Amsterdam - The Netherlands<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On 22 May, 2014, at 7:08, David McSween wrote:<br>
<br>
> This is slightly off topic, but I wonder if it is possible to extend the function of VSE strip modifiers to use compositor nodes?<br>
><br>
> That is allow re-using simple 'node code' like blur, to alter strip frames in the VSE.<br>
><br>
> We already have Curves and Color Corrector as well as Masks.<br>
><br>
> I propose simply adding 'discreet task' modifiers but also wonder if you can realistically port a compositor node tree into a VSE strip as a frame modifier?<br>
><br>
> One of the most annoying deficiencies in the VSE currently is the lack of Blur filters.<br>
><br>
> Thanks for your consideration.<br>
> David McSween<br>
</div></div><div class="HOEnZb"><div class="h5">> _______________________________________________<br>
> Bf-compositor mailing list<br>
> <a href="mailto:Bf-compositor@blender.org">Bf-compositor@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
<br>
_______________________________________________<br>
Bf-compositor mailing list<br>
<a href="mailto:Bf-compositor@blender.org">Bf-compositor@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Francesco Paglia<div>Vfx and Production Supervisor</div><div><br></div><div>mobile +39 347.82.12.473</div><div><div>e-mail <a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a></div>
</div><div><br></div>
</div>