Motion tracking for VFX, based on the Libmv a structure from motion library. This is a subproject of the VFX & Video module. There are two main areas here, Tracking and Masking.
Important links:
Contacts
Wow, the Eldritch Bug! Love it!
I can confirm this on the 2.92.0 release and the latest 2.93.0 Alpha, branch: master, commit date: 2021-03-04 06:43, hash: rBef7efc375197.
This is an intentional change which was done as a part of solution to jumpy view when performing various operations while Lock-to-Selection is enabled. I don't think it should be an option to restore old behavior, as the old behavior should be achievable by pressing . after L.
@Sebastian Koenig (sebastian_k) : if you think this is something that does not need any further ironing, please feel free to close.
You are right, this is different than before. But this is not really bug, but rather a change in behavior. Lock to Selection now also works in Masking, where it locks the view to the selected markers, but not with the completely broken behavior as in 2.91 and before, but rather in a way that actually works. Part of this change is that the view follows the active selection, but without centering the view. That way it is less jumpy and less distracting.
From code perspective this is more of a feature request. From user perspective it can be seen as a design task (as in, description of how thing are expected to work from artists perspective).
Hi and thx for the report.
Thanks for the hint, this should be fixed now. Instead of always creating a new collection, it will rename the default collection to "foreground", if there really is only 1 collection in your scene.
Should the Backdrop in the node view be automatically turned on when using the Nodes checkbox? I don't ever use the Backdrop anymore, but if most people do, I guess it would make sense to leave on.
I still use it. I didn't touch that setting, would leave it for now.
Checking both Nodes and Shadow Catcher with in both cycles and eevee, there weren't any nodes added for shadows. I haven't used Eevee enough to know if that's necessary, but for Cycles, should there be some nodes? Also, should Indirect be turned on for the "shadow catcher" collection?
No, the cycles setup uses the Shadow Catcher option. You don't need any nodes for that, it works via Alpha Channel. Not really fancy and not that much controls, but it's an easy setup.
Thank you for the answer !
And yes, i was referring to the 2016 GSoC project:
@Sergey Sharybin (sergey) I'd vote against it, since I would rather put the solve panel in the header.
Solving is something that sometimes is being done over and over again, with varying settings, so it would be cumbersome to have it in the sidebar, because you ALSO have to have track and tracking settings accessible all the time. That's why I would rather put it into the header, as shown in this image https://dev-files.blender.org/file/data/myed7vsbwffz3zipu42b/PHID-FILE-pr7w637qcto5oxwcnlgc/mce_tracking.png from here: https://developer.blender.org/D10198 It's a similar button placement as the "run script" operator in the text editor.
It is surely an interesting project and is nice to see your interest!
From the movement towards tool system point of view think it makes sense. Not sure it's really good to do such incremental step before the tool system is in place. @Sebastian Koenig (sebastian_k), I'll trust your judgement here.
we shall!
I tried your patch and it works great.
but now I cannot pan when nothing is selected
I tried to find a solution to the handles_as_control_point thing, but it doesn't really work. I mean, behavior itself with lock to selection seems fine, but now I cannot pan when nothing is selected. I guess this is something for a real developer! :)
Nice to see you in the C world!
I am catching up with a several design docs, this is one of them.
@Sebastian Koenig (sebastian_k), unfortunately, I am not familiar with the tool system, so can not quickly give feedback. Maybe Julian or Campbell knows?
@Sergey Sharybin (sergey) Hey man! I am making a bit of progress in the toolification of the clip editor. But I am stuck at getting the add_marker tool to actually do something. The tool shows up, but when I click nothing happens. Could you give me a hint on how to get this to work?
Sean Kennedy (hype) what do you think about this?
ED_KEYMAP_TOOL was missing, and keymap name was wrong.
Now annotation and selection tools are working.
The tool settings are still missing though.
I don't think this is a good change. These things are separate because they are separate settings that do separate things.
The tracking settings operate during tracking. Only when you actually use the tool (as in, track forward or backwards), they have an effect.
The Track settings are properties of the track that affect solving and/or display. Let's keep it that way.
Unless it might be an idea to have the tool settings (former default tracking settings) also act as tracking settings, so to unify those. But I think that might violate the whole active tool design in Blender...
This is a bit on the feature request side.
What is the purpose of this? What does it solve or improve?
Setup Tracking Scene also makes the Film transparent, creates a foreground collection with a Cube and can setup a shadow catcher, if needed
Some changes unrelated to the active tool system were split into D10204 which now proceeds this revision