Motion Tracking - Reopening file leads to jitter of tracked markes. #44675
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
Interest: X11
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#44675
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
Windows 7
Blender Version
Broken: blender 2.74 (offical)
Worked: (optional)
Short description of error
Reopening file leads to jitter of tracker markes.
Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps
I was working the chapter 2 tutorial from the Track, Match, Blend DVD in Blender 2.74.
After reopening and rendering the file the tracked markers "jittered" around despite the fact,
that they were tracked correctly the first time around. First I thought I was doing someting wrong.
Checked everything, tried diffrent tracking options, but still the same issues after reopening the
files.
So I finally tried a file from the dvd and rendert a sequence from frame 80 to 150 -> jitter.
Also attached are two frames the fist frame shows how far appart the tracked points are.
Changed status to: 'Open'
Added subscriber: @MichaelParucha
Added subscriber: @mont29
This is pretty much likely due to the fact that ffmpeg fails to seek in the stream reliably, which we can not really control.. There only two things to try:
Does any of those option help?
Added subscriber: @Sergey
@sergey. Tested with the hints you provided.
This would mean, that the movie clip has to be converted to an image sequence, or a different video format? But it is, what the proxy basically does, right?
Rule of thumb: First build a proxy, than track?
But what about older scenes that have to be retracked, because they don't work any more in new versions of Blender?
Don't know if this a bug, but when the Display Stabilization check box is set (Display panel), I can't mute the footage.
Proxy is only reducing memory used by the display, tracker uses original footage and proxies does not really affect on the seek code. but using timecodes (even keeping proxies disabled) is indeed recommended thing when working with movies.
If old files used to work and now they don't even with timecode enabled -- that totally worth checking. But for that it also needed to check files with the same version of blender which was used to store the files. So the question here: do you have tracked files which were done with proper timecode thing and which are now off?
Display Stabilization seems to be a bug, so please report it in a separate task.
If I understand this correctly, selecting time code index works independent of the generating proxies, right?
I deactivated the proxies in my test file and then the time code index and I got a jitter in the tracked marker, I wrote above it seems to work. Activated the time code again (first option of five) and the marker was stable again. Tested this with a second marker and it worked.
So I assume that the updated rule of thumb should be: First activate the time code index, then track. After changing the time code I have to reload the footage file (or save, close, open the file).
I will test this further, because the two added tracker markers have a high average error (above 2.0) and the corresponding empty in the 3d view jitters...
Older files. I have tested this with the file from blendfiles\02_camera_tracking\05_compositing\composite.blend (Track, Match, Blend DVD), and it doesn't matter if the time code is active in this case, because the tracked marker jitter. So as I assumed this works only if the time code was set before the tracking begun.
In order to make time code used you need to do:
And it indeed seems changing timecode does not really invalidates the cache, this will be fixed soon.
As for older files and timecode -- yes, this is correct that timecode is actually needed to be used during tracking. Otherwise it's not really guaranteed timing wouldn't go off :(
Knowing which Blender version was used to create a file is very useful. Unfortunatly I have never seen this information in blender, i.e. when opening, linking or appending a .blend file. But this would be certainly a feature request, and I would never mention such thing in the bug tracker... :-)
Not really intuitive, but it is possible -- run blender from the ocmmand line and pass --debug argument. Blender will be printing versions of the file to the console then.
I have checked this file blendfiles\02_camera_tracking\05_compositing\composite.blend with blender 2.62 (official), 64bit Windows.
I get jitter.
I have checked other files from the dvd with Blender 2.72 and 2.62 (both official, 64bit Windows):
NO jitter.
Thanks a lot @sergey.
Changed status from 'Open' to: 'Archived'
Time to close then! :)
@mont29. I think that there were two open issues:
Quote: "And it indeed seems changing timecode does not really invalidates the cache, this will be fixed soon."
Quote: "Built Proxy (the button should actually tell "Build Proxy / Timecode")"
So please ask @Sergey if this can be closed for sure.
Yes, it's still on TODO list actually. Will try to address it prior to testbuild1.
EDIT: Those changes are now committed to Git.