<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>No need to, I've been talked off my ledge. ;) This is a small irrelevant fire, anyway.<div><br></div><div>I only suggested it based on the few experiences I've had so far explaining it to people. Everyone I mention it to thinks it's doing what Mocha does. I'm sure that's just because of the vfx industry, and that's all we have to relate it to. And while I totally get that it is doing more than a standard corner pin tool, everyone seems to understand it perfectly when I say "think of it as a corner pin". </div><div><br></div><div>I don't care what it's called, it's still an awesome tool to have. I'll keep explaining it to vfx folks so they understand it. :)</div><div><br></div><div>sean</div><div><br><div><hr id="stopSpelling">Date: Tue, 13 Aug 2013 10:56:31 -0700<br>From: mierle@gmail.com<br>To: bf-vfx@blender.org<br>Subject: Re: [Bf-vfx] Plane Tracking naming<br><br><div dir="ltr">I will make a proposal but it won't be today; I have other fires to deal with.</div><div class="ecxgmail_extra"><br><br><div class="ecxgmail_quote">On Tue, Aug 13, 2013 at 10:32 AM, Ton Roosendaal <span dir="ltr"><<a href="mailto:ton@blender.org" target="_blank">ton@blender.org</a>></span> wrote:<br>
<blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;">Hi,<br>
<br>
All feedback is welcome, but let's not make it too complex. We do have a procedure in place for how to solve issues like this.<br>
<br>
Proposing naming of features is really a privilege of the developer first, but it should be agreed on by the module team (if there's a debate). If there's still no consensus we can ask related teams to decide (UI team) or the bf-admins in the end.<br>
<br>
So - I suggest to have Keir and Sergey propose and Sebastian and Sean agree with it. If they are all happy discussion can be closed.<br>
<br>
<a href="http://wiki.blender.org/index.php/Dev:Doc/Process/Module_Owners" target="_blank">http://wiki.blender.org/index.php/Dev:Doc/Process/Module_Owners</a><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="ecxHOEnZb"><div class="h5"><br>
<br>
<br>
On 13 Aug, 2013, at 19:04, Sergey Sharybin wrote:<br>
<br>
><br>
> On Tue, Aug 13, 2013 at 9:34 PM, David Jeske <<a href="mailto:davidj@gmail.com">davidj@gmail.com</a>> wrote:<br>
> On Tue, Aug 13, 2013 at 12:36 AM, Sergey Sharybin <<a href="mailto:sergey.vfx@gmail.com">sergey.vfx@gmail.com</a>> wrote:<br>
> I do not happy with calling it "corner pin" because it's not corner pin at all. You could (and probably even should) use more than 4 point tracks to make plane estimation much more accurate. Also, point tracks have no relation with corners at all: you could track points which are not corners of your plane (we showed this in our video).<br>
><br>
> The feature you are calling "plane track" appears *exactly* like corner pinning in Mocha and After Effects. The "corners" referred to in the name "corner track" or "corner perspective pin" are the corners of your "plane" not the trackers themselves.<br>
><br>
> <a href="http://www.youtube.com/watch?v=xRpHgVFPqqk&feature=player_detailpage&t=465" target="_blank">http://www.youtube.com/watch?v=xRpHgVFPqqk&feature=player_detailpage&t=465</a><br>
> <a href="http://www.youtube.com/watch?v=fY4wwZFD5-c" target="_blank">http://www.youtube.com/watch?v=fY4wwZFD5-c</a><br>
><br>
> So is it a question like "let's call feature XXX exactly the same as it's called in software YYY"?<br>
><br>
> The reason it's not called planar-tracking is that it's not 3d, it's a 2d affine image transformation.<br>
><br>
> It's not affine, it's homography if it makes sense.<br>
><br>
> Why do you call it a "plane"? As far as I can see, it's not a 3d-plane, but a 2d-affine compositing surface distorted in camera-space.<br>
><br>
> because it's a plane. You could think of it as a real non-concave plane being warped by a homography estimated from point tracks. Which is like if you watch on a viewplane on which that plane is being projected.<br>
><br>
><br>
> Another usage of plane track might be constraining point tracks to belong to this plane while tracking them. Which means we might support other-way-around usecase: you create point tracks, you create plane out of them, and then starts tracking this point tracks taking plane constraint into account.<br>
><br>
> At that point, the track would be for a 3d-plane, and it would be appropriate to call it a planar-track.<br>
><br>
> That wouldn't be 3d, that'd still be based on homography estimation and making so tracks fits this homography in a best way (well, difficult to explain this in text, whiteboard would be much easier). At this point i couldn't see why or how we'll reconstruct 3D from point tacks in that case.<br>
><br>
><br>
><br>
> --<br>
> With best regards, Sergey Sharybin<br>
</div></div><div class="ecxHOEnZb"><div class="h5">> _______________________________________________<br>
> Bf-vfx mailing list<br>
> <a href="mailto:Bf-vfx@blender.org">Bf-vfx@blender.org</a><br>
> <a href="http://lists.blender.org/mailman/listinfo/bf-vfx" target="_blank">http://lists.blender.org/mailman/listinfo/bf-vfx</a><br>
<br>
_______________________________________________<br>
Bf-vfx mailing list<br>
<a href="mailto:Bf-vfx@blender.org">Bf-vfx@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-vfx" target="_blank">http://lists.blender.org/mailman/listinfo/bf-vfx</a><br>
</div></div></blockquote></div><br></div>
<br>_______________________________________________
Bf-vfx mailing list
Bf-vfx@blender.org
http://lists.blender.org/mailman/listinfo/bf-vfx</div></div> </div></body>
</html>