Object Tracking markers are not scaled with the camera scale visually (but actually are scaled internally???) (With file and video) #74322
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#74322
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00
Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-02-12 16:20, hash:
77d23b0bd7
Worked: (optional)
Short description of error
Blender's motion tracker is not showing the locations of the object tracking markers correctly if the camera with the solve has a non-1 scale.
(Even using the orientation tools for the camera solve actually scales the camera in blender, scaling the tracking data independent from this value seems to be impossible right now. There are many cases where a camera track needs to be scaled, for example in order to match up with real world dimensions.)
Exact steps for others to reproduce the error
I explain my problem and my understanding of what might be happening (and what should be) in this video here:
https://youtu.be/tJG8B2gj2b0
(Please note the image sequence is attached for reference but completely arbitrary and not necessary to understand the problem.)
ExampleSequenceObjectTrack.zip ExampleObjectTrack.blend
Added subscriber: @manuell3d
Added subscriber: @SeanKennedy
Added subscriber: @EAW
Scaling_fixed0001-0100.mp4
ExampleObjectTrack1.blend
I think the way to do it is not to scale the camera in the 3D viewport, but to use the scaling in the movie clip editor.
I set the scaled camera back to 1.0. I then used the coffee table's legs to set and apply the scale to 1m.
I also adjusted the object's tracker scaling the same way, and set it to the 1.6 you approximately had for the camera. I also tinkered with setting and clearing the inverse several times.
I will try to come up with the exact order of steps to make it work as expected, as right now that isn’t quite clear even to me. I feel that I kind of lucked into the proper solution, made sure to save it immediately and made the video. This is so you can continue your work while I check the commit log and other reports to see if the module owner was working on this specific issue recently.
Thank you for the quick answer! :)
Even if that was the case, it shouldn't be. As far as I can tell though, it really practically makes absolutely no difference.
This definetly should not need any tinkering, it's as straight forward as can be in a scale of 1.
I feel pretty confident by now that what I explain in the video is more or less what is wrong here.
Really nice of you! Please note this exact scene is just an example because I can't share any of the material we're working on in the studio. So specifically we're trying to find a halfway feasible and reversible workaround for it. However it still definetly is NOT how this is supposed to work.
(For the workaround we're thinking about applying the object solve in a scale 1, then scale the camera. Honestly it's really a complete mess to dance around this flaw and it's really inviting human error...)
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscribers: @Sergey, @sebastian_k
@manuell3d
Of course!
I wasn't able to get specific steps of a workaround working in my limited time trying yesterday.
@Sergey and @sebastian_k any ideas about this one? I noticed @Sergey you were working on the tracking constraints a few weeks ago, not sure if this issue looks related.
Added subscriber: @KNAO
I am seeing the same problem. It worked properly in the 2.79 release, but has happened since the 2.80 release.
When the camera is scaled, the Object Solver is affected by the camera scale and does not maintain the correct position on the Solve.(Windows-10)
I reconfirmed. It seems that the object solver is not a problem and the object tracking marker displayed in the viewport overlay is not linked to the camera scale in the first place.
Therefore, even if you adjust the Object Scale of the clip editor by believing in overlay display, if the camera scale is included, the actual position on the display will be different from the actual position.
Yeah, that seems to be wrong indeed. Scaling the camera to match the scene is very common, obviously the object track should still work. Seems to be a bug indeed.
Added subscribers: @fclem, @Jeroen-Bakker
The drawing code explicitly uses normalized matrix for tracking object, which cancels out any scale.
@fclem, @Jeroen-Bakker any reason behind this? Or just legacy code which did weird thing? This seems to fix the problem P1301: #74322
Maybe @sebastian_k can test :)
Yep, that seems to fix it. :)
@Sergey LGTM I don't think this was on purpose.
@Sergey Ok to commit. Don't know either why it was that way.
This issue was referenced by
07d5b8b023
Changed status from 'Confirmed' to: 'Resolved'