<div dir="ltr">Jeroen, <div>I think that the original question is not just about blur.... it's about the ability to build some nice effects over a strip.</div><div>Today it's all about blur... tomorrow focus will go on.. let say keying, the day after on any other stuff that someone else would need for a specific purpose.. </div>
<div>Of course to add a blur modifier in the VSE will, in some way, help but to me is like a patch in an always growing hole...</div><div><br></div><div>As Sean pointed out, there are other priorities that have to be addressed and in my opinion there's nothing more important than canvas and caching because the first one will allow us to effectively use properly picture of any size and the second one will finally allow us to see what we are doing through a series of frames without render out sequence over sequence while getting sad just because we would only see slight modification on a single node...</div>
<div><br></div><div>Jeroen, I know talking about this topic is useless at the moment but I believe users will not get confused if proper design will be made for such a huge change that definitelly is a new way of thinking the relationship between 3D, compositor and VSE.</div>
<div><br>
</div><div>Consider that every time I have to work with element that can change their position along time due to creative choices and the result of that element reflects on the background I'm forced to leave blender compositor and use another solution simply because if I have to change something there is literally a pain.</div>
<div><br></div><div>Someone can argue saying that I could render out strips and modify them on another edit... well of course I could... but I'm not interested in having dozen of blend file for something that can be just a little step more complex than a simple edit... at least it's not an option if time constraints are very critical.</div>
<div><br></div><div>Back to Sean proposal I tremendously agree with the ideas of an "edit node" that looks really like the Combustion "edit node" where there's only a layer allowed but with the useful difference that it can have multiple strip as input and there are some operation allowed like trim, cut, revert, retime freeze a frame.</div>
<div>Here a quick reference:</div><div><a href="https://www.youtube.com/watch?v=pLWaNwiVoHU#t=57">https://www.youtube.com/watch?v=pLWaNwiVoHU#t=57</a><br></div><div><br></div><div>However this tool that would really rock, solves just a part of the problem we are arising here with this discussion simply because it doen't put each input in relationship with the others that is essential especially for motion graphic jobs.</div>
<div><br></div><div>Thanks for your time reading my mail</div><div>Ciao</div><div>Francesco <br></div><div> </div><div> <br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-05-23 7:09 GMT+02:00 Sean Kennedy <span dir="ltr"><<a href="mailto:mack_dadd2@hotmail.com" target="_blank">mack_dadd2@hotmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div dir="ltr">Hey guys,<div><br></div><div>Interesting conversation. While I agree it'd be cool to have simple fx in the VSE, like blur, I also hate to think that developers would be taken off other things to do something that can already be done in another part of blender. Layer-based timelines are definitely important. Animating things over time and offsetting individual clips is so easy to do in After Effects that it barely requires thinking. But then, AE doesn't play extremely well with Premiere (no matter what hype Adobe puts out saying it does), giving it the same issues we're ultimately discussing here. Making the compositor and VSE work together in the most efficient way. </div>
<div><br></div><div>I have no clue what that is. I've used most compositing software out there, and each has their strengths and weaknesses. Offsetting clips in time is trickier in Nuke, so they actually just wrote a layer-based timeline for it. I haven't used it yet so I don't know how it works together with nodes, but it's interesting.</div>
<div><a href="http://cdn2.digitalartsonline.co.uk/cmsdata/slideshow/3492614/DopeSheet_02_271113-1500.jpg" target="_blank">http://cdn2.digitalartsonline.co.uk/cmsdata/slideshow/3492614/DopeSheet_02_271113-1500.jpg</a></div>
<div><br></div><div>I used to think it'd be a great idea to have a a "timeline node". A node that, with footage plugged into it, would show you a timeline of the in and out settings of the project, and you could easily position your footage visually, and it would perform the time offsets you set. </div>
<div><a href="https://www.dropbox.com/s/u5nfbms8asltbsn/timeline_node.jpg" target="_blank">https://www.dropbox.com/s/u5nfbms8asltbsn/timeline_node.jpg</a></div><div><br></div><div>I've also thought it would be cool to have a timeline based fx program where you could double click on a layer and it would go into a node view for all fx work. Sort of like a nested compositor inside of a editing program.</div>
<div><br></div><div>I wish I knew more about Inferno and Flame, because I believe that is their strength - editing and vfx working together.</div><div><br></div><div>Just thinking out loud here. I personally think there are much bigger issues that should be worked on, like caching, canvas compositing, etc. I'm sure there are much bigger things to be worked on in the VSE as well, things that are much more of a solid foundation. I don't know anything about code at all, or how all these modules talk to each other in Blender, but I'm sure it's not easy. </div>
<div><br></div><div>sean<br><br><div><hr>Date: Fri, 23 May 2014 14:18:05 +1000<br>From: <a href="mailto:3pointedit@gmail.com" target="_blank">3pointedit@gmail.com</a><br>To: <a href="mailto:bf-compositor@blender.org" target="_blank">bf-compositor@blender.org</a><br>
Subject: Re: [Bf-compositor] Extending some node functions to VSE<div><div class="h5"><br><br><div dir="ltr">Hi Jeroen,<div><br></div><div>I agree that the compositor is a powerful tool for individual shots.</div><div>However the artist should be able to make timing decisions (lining shots up relative to other shots in a composite) in the VSE, then send those times to the compositor. Whether they are animated 3D scene elements or live action video source should not matter.</div>
<div>Currently we can do that from python scripting, but we cannot easily modify the timings if there is a creative change. Currently what is the Blender preferred 'workflow' for setting up frame offsets and media durations in the compositor? Answer - a notepad.</div>
<div>But I am not sure how best to stop this becoming a feedback issue?</div><div><br></div><div>Finally I agree that the VSE at least lacks a simple blur and this would be most helpful as a strip modifier instead of a Effect Strip. This way you could more easily mask elements of the shot that needs blurring.</div>
<div><br></div><div>D</div><div><br></div></div><div><br><br><div>On Fri, May 23, 2014 at 5:32 AM, Jeroen Bakker <span dir="ltr"><<a href="mailto:j.bakker@atmind.nl" target="_blank">j.bakker@atmind.nl</a>></span> wrote:<br>
<blockquote style="border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>Hi All, <br>
<br>
This topic has been discussed many times over, but on a pipeline
point of view it is not that easy. Compositor works on shots, not
on sequences. You first composite, then you sequence you don't
want to mingle these tasks as it will only create confusion to
users and developers. But you might want to think about a
different system that could be used inside the sequencer. This
system could share blurs and other features, But are we convinced
how such a node based system will work with what cases, and what
cases it really doesn't work? <br>
<br>
IMO someone should invest to get a blur strip going? It fits good
in the architecture of Blender's sequencer, fairly easy to develop
and solves the original question.<br>
<br>
Regards, <br>
Jeroen Bakker<div><div><br>
<br>
On 05/22/2014 04:07 PM, Francesco Paglia wrote:<br>
</div></div></div><div><div>
<blockquote>
<div dir="ltr">Hi Cezary,
<div>Well the workarond you proposed can be used but in my
opinion it became useless as soon as you want to replicate
this action for many clips in the same edit... you'll end up
getting crazy trying to remember which scene contain the data
you're looking for.</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div><br>
<br>
<div>2014-05-22 15:49 GMT+02:00 Cezary
Kopias <span dir="ltr"><<a href="mailto:cezary.kopias@gmail.com" target="_blank">cezary.kopias@gmail.com</a>></span>:<br>
<blockquote style="border-left:1px #ccc solid;padding-left:1ex">This maybe
something you know but its possible to use comp nodes on
footage and use it in vse.<br>
Make scene with only movie clip node than blur or watever.
You can also set clip range in vse of this scene. Than just
import this scene in another (called "VSE" ?) and disable
openGL preview to compute nodes. I think the main reson for
the lack of nodes as modifirers is their non realtime speed.<br>
<div>
<div><br>
<br>
<br>
On Thu, 22 May 2014 15:08:15 +1000<br>
David McSween <<a href="mailto:3pointedit@gmail.com" target="_blank">3pointedit@gmail.com</a>>
wrote:<br>
<br>
> This is slightly off topic, but I wonder if it is
possible to extend the<br>
> 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<br>
> 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<br>
> can realistically port a compositor node tree into
a VSE strip as a frame<br>
> modifier?<br>
><br>
> One of the most annoying deficiencies in the VSE
currently is the lack of<br>
> Blur filters.<br>
><br>
> Thanks for your consideration.<br>
> David McSween<br>
<br>
<br>
</div>
</div>
<span><font color="#888888">--<br>
ck <<a href="mailto:cezary.kopias@gmail.com" target="_blank">cezary.kopias@gmail.com</a>><br>
</font></span>
<div>
<div>_______________________________________________<br>
Bf-compositor mailing list<br>
<a href="mailto:Bf-compositor@blender.org" target="_blank">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 <a>+39 347.82.12.473</a></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>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Bf-compositor mailing list
<a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a>
<a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a>
</pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
Bf-compositor mailing list<br>
<a href="mailto:Bf-compositor@blender.org" target="_blank">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></blockquote></div><br></div>
<br>_______________________________________________
Bf-compositor mailing list
<a href="mailto:Bf-compositor@blender.org" target="_blank">Bf-compositor@blender.org</a>
<a href="http://lists.blender.org/mailman/listinfo/bf-compositor" target="_blank">http://lists.blender.org/mailman/listinfo/bf-compositor</a></div></div></div></div> </div></div>
<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>
<br></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>