Bug with tracking on movie files #37853

Closed
opened 2013-12-18 11:46:58 +01:00 by Petrone Flavius · 9 comments

System Information
OS X Mavericks 10.9, 3770K, 16 GB and 680 GTX

Blender Version
Broken: Stable OS X 64bit Blender 2.69 r60991 also latest build by the time of this report.

Short description of error
When loading a movie(mp4,mov,etc.) file as a source for tracking, while tracking it will skip and/or miss frames that are loaded. Also the cached frames are wrong too.
This makes some tracking points jumping around and continuing in the wrong order by 1 or 2 frames also the next frame ACCURACY is disrupted by this!

Exact steps for others to reproduce the error
Load a movie file into tracking, track some points and go with ALT+arrow while tracking. AFTER the first track, jump around the timeline so that frames load, then go back and look at the result by playing it back. Some frames will not be correctly loaded regarding the tracking data.

SEQUENCE FILES LIKE PNG,JPG,ETC.. ARE NOT AFFECTED !

**System Information** OS X Mavericks 10.9, 3770K, 16 GB and 680 GTX **Blender Version** Broken: Stable OS X 64bit Blender 2.69 r60991 also latest build by the time of this report. **Short description of error** When loading a movie(mp4,mov,etc.) file as a source for tracking, while tracking it will skip and/or miss frames that are loaded. Also the cached frames are wrong too. This makes some tracking points jumping around and continuing in the wrong order by 1 or 2 frames also the next frame ACCURACY is disrupted by this! **Exact steps for others to reproduce the error** Load a movie file into tracking, track some points and go with ALT+arrow while tracking. AFTER the first track, jump around the timeline so that frames load, then go back and look at the result by playing it back. Some frames will not be correctly loaded regarding the tracking data. SEQUENCE FILES LIKE PNG,JPG,ETC.. ARE NOT AFFECTED !

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @enilnacs

Added subscriber: @enilnacs
Sergey Sharybin was assigned by Brecht Van Lommel 2013-12-18 12:05:18 +01:00

Added subscriber: @brecht

Added subscriber: @brecht

I don't know how well this is intended to work, movie files generally do not support scrubbing so they can be problematic for scrubbing. Generally the advice is to use either image files or proxy/timecode I think, but Sergey is the expert so assigning to him.

This may also be a Quicktime problem since you mention mp4 and mov files.

I don't know how well this is intended to work, movie files generally do not support scrubbing so they can be problematic for scrubbing. Generally the advice is to use either image files or proxy/timecode I think, but Sergey is the expert so assigning to him. This may also be a Quicktime problem since you mention mp4 and mov files.

Although i understand that movie files should not be scrubbed, this is of course not practical especially for tracking. The main problem being that for each track a sequence file conversion is needed (bigger memory, lower speed, more work and depending on codec also quality degradation).

Quicktime should generally deliver frame accurate even in LongGOP codecs... but is Blender official using QT or an integrated ffmpeg for mp4/mov ?

Although i understand that movie files should not be scrubbed, this is of course not practical especially for tracking. The main problem being that for each track a sequence file conversion is needed (bigger memory, lower speed, more work and depending on codec also quality degradation). Quicktime should generally deliver frame accurate even in LongGOP codecs... but is Blender official using QT or an integrated ffmpeg for mp4/mov ?

As @brecht mentioned, we can not guarantee accuracy of seek in video files unless you're using timecode. Please generate it from the proxy/timecode panel before tracking. Use either Record Run or Free Run No Gaps timecodes and see whether it helps.

Not sure whetherwe're still using QT or we've switched to FFmpeg on OSX, but we don't have timecodes implemented to QT AFAIR. You might also try re-exporting the video in an external application making sure indices and so are correct.

As @brecht mentioned, we can not guarantee accuracy of seek in video files unless you're using timecode. Please generate it from the proxy/timecode panel before tracking. Use either Record Run or Free Run No Gaps timecodes and see whether it helps. Not sure whetherwe're still using QT or we've switched to FFmpeg on OSX, but we don't have timecodes implemented to QT AFAIR. You might also try re-exporting the video in an external application making sure indices and so are correct.

OK, Record Run WORKS by pressing generate proxy, even without generating the proxy JPGs !
Somehow could this be generated by default when you import movie files ? Would be great. Cause you still need to activate TC and set it.
May thanks for the solution.

OK, Record Run WORKS by pressing generate proxy, even without generating the proxy JPGs ! Somehow could this be generated by default when you import movie files ? Would be great. Cause you still need to activate TC and set it. May thanks for the solution.

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'

This is actually in my personal TODO. It's just not so much clear which exact TC to use by default. In different cases you might want different ones. Need some much further investigation..

Archiving the report since it's known limitation of video files without timecode. Thanks for it anyway!

This is actually in my personal TODO. It's just not so much clear which exact TC to use by default. In different cases you might want different ones. Need some much further investigation.. Archiving the report since it's known limitation of video files without timecode. Thanks for it anyway!
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#37853
No description provided.