Perhaps I should create a separate bug report, but also when in the MCE, right click controls the timeline and the time slider in the dope sheet. Shouldn't those also be left click?

Also, once the mask is drawn, you cannot select the vertices and adjust them with left clicking, only with right clicking and dragging. It should all be left clicking.

Not sculpting, but rotoscoping. Drawing a mask for rotoscoping in the MCE.

That would be fine, although I use Detect Features more than I use the Track Setting as Default or Copy Track Settings.

This is very nice, seems to be intuitive.

I agree with you for sure that Blender's accuracy is spectacular. :)

I'm excited to see these tools in the topbar to see how it really feels in action.

Would it be possible to only have one set of Track Settings? Whatever it is set to when you create a new track, that's what the new track uses. If you have a track selected, those controls then apply to that selected track. It's confusing having two, and this would streamline it quite a bit.

In D2106#84303, @adam earle (adamearle) wrote:

So I am wondering is there any need for this kinda thang anymore?

https://www.youtube.com/watch?v=FrPC6nkv7L0

This is interesting, for sure. I'm not sure that in a typical compositing workflow if it would be extremely useful, but from the examples posted, it certainly looks like you can do some very artsy, creative stuff with it.

In D3606#83548, @Michael P. (forest-house) wrote:

Hey @Sean Kennedy (hype), do you think that viewing the matte for cryptomatte objects in the image editor is a useful feature?

Hoping this is in the latest trunk, and makes it to 2.8. I haven't forgotten about these awesome motion tracking updates!

Any more work done on this lately, has it been added to trunk and I missed it? And will it be ported to 2.8? Still looking forward to having this feature!

Interesting idea, being able to set the amount of frames. Right now I believe it works between keyframes, which is how a typical matchmover works in their daily tracking work. I prefer the keyframe way myself, since it's very easy to simply set a keyframe on the last good frame, then go to where the drift is at it's worst and adjust it. If we do add the amount of frames option, let's please still retain the current functionality, as well. I do also like the idea of it being a mode to enable, or even just a checkbox to turn it on or off, so you definitely know when you are in refining mode.

I'm happy to test this if there's any updates and an updated Windows build.

This is great! Happy to test it if a Windows build is available!

I would indeed find this very useful. For example, say I turn on border render to render out a small vfx element faster. Then I get notes on the shot, so I go and do more versions, versioning up as I go, turning off border render because maybe in these new versions the effect is different. Eventually they settle on something very similar to the first version I submitted that had been rendered with border turned on, but I'm now 10 versions later and I've moved the border to other places. My compositing setup (in Nuke) is already setup, so if I can render with the exact same border dimensions as 10 versions earlier, I can easily just drop in the new render and not have to worry about anything. That's how I'd use it most.

Working great when using G to move around the marker, and also works with arrow key nudging after pressing G.

Awesome, thanks! Will test this weekend!

Anyone have a build for Windows I could test? :)

In T51844#441528, @Campbell Barton (campbellbarton) wrote:

• @Sean Kennedy (hype) Good suggestions, added. Question though - is this for tracking points or mask too?

Node-Editor / Compositor:
Corner Pin node:
This node desperately needs a widget. Pretty simple widget, just four corners. I suppose it could also have the soon-to-be-standard transform widget in the center of it, as well (that would be a nice bonus!)

Looks neat! I'd be happy to test it on some vfx type things.

In D1788#50245, @Sean Kennedy (hype) wrote:

And as I was doing a demo scene for a blog post, I noticed that a mesh light on my test object was wrecking the shadow catcher. It's a bit strange that a geometry light was wrecking the scene in my blog test scene, but the mesh light in the other test scene did not. Perhaps it has to do with the positioning and shape of the mesh light. In mt blog test scene, it's a cylinder, and is inset into other geometry a bit. Perhaps that's causing the ground plane to be picking up a big cast shadow from the geometry that is blocking the cylinder light?

Here's the blend file of the scene with the green sphere

I did a couple tests to see if I had any problems in the alpha channel.

I like it so far! Simple to set up, very nice to see in the viewport, and a bit faster and easier to use in compositing. Great work! Looking forward to seeing how it continues to develop.

Thanks for the add! This sounds great!

I understand the issues now, I think. Seems odd to me that there's no way to stabilize the scale without a pivot point, but I'm not a coder, so not sure how much advice I can give on how best to make this work.

Ah, okay, I see. That definitely makes a difference. Indeed it does work. There's still a slight problem that when Zoom is enabled, in my 2 point example, the image drifts upwards. I made a quick video to demonstrate.

What would be absolutely amazing is if once you selected Image Sequence or Movie, the node gave you a little visual timeline to adjust the in/out, placement, and length of the clip.

How does this work? I'd love to test this. Where is the feature found?

Gave it a quick test run this morning, seems to work great! Only tried it with a couple things, so I will explore it a bit more soon. But wow, what a great feature! Thank you guys!

Awesome thank you!

Windows, please. This is one of the most needed features in the compositor. :) Very exciting!

Spectacular! Will this be in buildbot to test in the next day or so?

In D1591#36626, @Campbell Barton (campbellbarton) wrote:

No strong opinion on this, if users find useful - seems OK?

In D1579#35041, @Marcelo Mutzbauer (1xundoredo) wrote:

@Sean Kennedy (hype) Thank you for the report. Mask points are parented individually. The solution I found was to check whether both neighbor points have the same parent. If they do, the new point is also going to be parented to the same track/plane. If they don't the new point won't be parented at all. Does that look like a good solution?

In D1579#34889, @Marcelo Mutzbauer (1xundoredo) wrote:

@Sean Kennedy (hype) Here you are(this is a 64-bit build):

blender_cut_spline_winx64.zip78 MBDownload

Works great so far Thank you

Is this in the daily builds? I'm not seeing it yet.

This is great! Thank you!!

I would love to test this out. Is there a way to get a windows build (I don't compile)?

In D1257#24044, @Sebastian Koenig (sebastian_k) wrote:

Thanks a lot for making a patch out of this! :)
I tested briefly and would propose a few changes:

1. It seems a bit overkill to have different colors for spline and overlay. Wouldn't it be enough to have one color for both, and the alpha which applies only to the color overlay? 1a. Or actually, maybe just keep the current way of coloring when in outline mode, only when line display is changed to "line" (that other patch i believe?) use the mask color for the spline.
2. Maybe it would be possible to change the blending? If I have several masklayers with the same color, I think it would be better to just merge them instead of alphaovering their values. Only if the colors are different, use alpha blending.
3. Feathering should use the colors as well.
   
   What do the others think? @Sean Kennedy (hype)? :)

Awesome!

Sometimes there are stray beams coming in from something not apparent in the input image.

In D655#23, @Lukas Toenne (lukastoenne) wrote:

Ray Length should also get a factor input per pixel to give more control. A typical case where this would be handy is crepuscular rays (aka "god rays") from cloud patterns. These are affected by perspective and should be shorter in the distance, but currently all rays are the same length. Doing this efficiently is possible, but may require a few changes to the compositor code.

In D655#15, @Greg Zaal (gregzaal) wrote:

I think it'd be more natural to control an Angle Offset (like the Glare node) instead of an arbitrary coordinate/vector. It'd also of course be useful to be able to control the ray length and angle using a texture, though this could be added later like the falloff mode.