improve usability of 2D stabilizator #49036

Closed
opened 2016-08-07 15:36:22 +02:00 by Hermann Voßeler · 15 comments

While Blenders video stabilizer, based on the great image feature tracking support, works well, is easy to use and fulfils all basic needs, its usability on more complex shots and extended real world footage is still somewhat lacking and might be improved...

  • adding more than two tracks does not improve the result in most cases and does not help to get the sometimes unpredictable bumpiness under control, even when adding carefully chosen tracking points, which in theory should improve the result.

  • the canvas does not adapt and expand on demand, which makes it near impossible to deal with sidewise tracking or panning shots

  • tracks with later onset and gaps cause hard to understand problems

  • rotation stabilisation works quite well in a “clean demo” setup, but is unusable when it’s needed most.

    • only a single track can be used to control rotation
    • this track doesn’t pick up the angular movements in a correct way
    • when the tracking marker moves towards the top or the bottom, above or below the other tracking points, unpredictable jumps can happen.
    • when some tracks start at differing positions, the rotation compensation flounders completely, flipping the frame upside down
  • while it is possible to animate (some) properties of 2D stabilization, it is not possible to open F-curve or dopesheet editors on such animation data beyond the scope of the main 3D scene.

  • sometimes it would be desirable to control the actual effective rotation centre (pivot point), which is not necessarily fixed to the image centre. There should be the option to anchor this either to the weight centre of the tracking points (default), the image cadre or the canvas.

  • controlling the effective camera movement is possible, yet laborious and often frustrating. In many cases, a simple lowpass damping would resolve most of the problems and leave only the fine adjustments to the user.

  • stabilzation creates "dancing black borders", forcing us to zoom in. Too much zoom decreases image quality and kills image composition. Often, it would be possible to fill those black border gaps with footage from adjacent frames, yet doing so manually is a tricky and laborious task

While Blenders video stabilizer, based on the great image feature tracking support, works well, is easy to use and fulfils all basic needs, its usability on more complex shots and extended real world footage is still somewhat lacking and might be improved... - adding more than two tracks *does not improve the result in most cases* and does not help to get the sometimes unpredictable bumpiness under control, even when adding carefully chosen tracking points, which *in theory should improve the result.* - the canvas does not adapt and expand on demand, which makes it near impossible to deal with sidewise tracking or panning shots - tracks with later onset and gaps cause hard to understand problems - rotation stabilisation works quite well in a “clean demo” setup, but is unusable when it’s needed most. - only a single track can be used to control rotation - this track doesn’t pick up the angular movements in a correct way - when the tracking marker moves towards the top or the bottom, above or below the other tracking points, unpredictable jumps can happen. - when some tracks start at differing positions, the rotation compensation flounders completely, flipping the frame upside down - while it is possible to animate (some) properties of 2D stabilization, it is not possible to open F-curve or dopesheet editors on such animation data beyond the scope of the main 3D scene. - sometimes it would be desirable to control the actual effective rotation centre (pivot point), which is not necessarily fixed to the image centre. There should be the option to anchor this either to the weight centre of the tracking points (default), the image cadre or the canvas. - controlling the effective camera movement is possible, yet laborious and often frustrating. In many cases, a simple lowpass damping would resolve most of the problems and leave only the fine adjustments to the user. - stabilzation creates "dancing black borders", forcing us to zoom in. Too much zoom decreases image quality and kills image composition. Often, it would be possible to fill those black border gaps with footage from adjacent frames, yet doing so manually is a tricky and laborious task
Hermann Voßeler self-assigned this 2016-08-07 15:36:22 +02:00

Changed status to: 'Open'

Changed status to: 'Open'

Added subscriber: @Ichthyostega

Added subscriber: @Ichthyostega
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

Added subscriber: @Sergey

Added subscriber: @Sergey

This issue was referenced by b1677201f9

This issue was referenced by b1677201f9af7a3e5f5254817179f12384fbdc44

This issue was referenced by 793900d46c

This issue was referenced by 793900d46c4caa695074bbaf9c467c0b0659f5cd

This issue was referenced by baaa2d6d39

This issue was referenced by baaa2d6d396ef8003cf2241ae0a6304d6aebb496

This issue was referenced by 9c3b9f6a83

This issue was referenced by 9c3b9f6a836ace08baf04cf4e716a73f9797f88d

after some testing, tweaking and further investigations, the version (baaa2 + 9c3b9) currently in master changed the pivot point to follow the weight centre of the location tracks, instead of attaching it to the image centre. The pivot point is the reference point to detect rotation and scale against, and thus this change improves the behaviour especially in very simple situations. For example, if you add only a single (location) track, this location also becomes the pivot point. If you then add just one other marker as rotation track, the stabiliser will keep the relation between those two points fixed, and scale/rotate the image accordingly to do so.

after some testing, tweaking and further investigations, the version (baaa2 + 9c3b9) currently in master changed the pivot point to follow the weight centre of the location tracks, instead of attaching it to the image centre. The pivot point is the reference point to detect rotation and scale against, and thus this change improves the behaviour especially in very simple situations. For example, if you add only a single (location) track, this location also becomes the pivot point. If you then add just one other marker as rotation track, the stabiliser will keep the relation between those two points fixed, and scale/rotate the image accordingly to do so.

Added subscriber: @Funkster-3

Added subscriber: @Funkster-3
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Member

AFAIK everything has now been committed and this can be closed.

AFAIK everything has now been committed and this can be closed.

Hello Aaron,

actually I created this task as an umbrella for that topic; I have still some things to improve and I intend to contribute more to that topic. Note especially the point with the "dancing black borders" is not solved. Also the handling of the pivot point can be bettered (and I know how). And, some people proposed different approaches to the same problem, like using a lowpass filter on the track data

Only the immediate Diff D583 is closed and released, which resolved the most pressing issues.

Indeed I am unsure how such an ongoing effort is managed in Blender. Someone recommended me to create such an umbrella task. But I do not mind if you close it, just lets's make it clear in the text then, that it is only closed for technical reasons, not really resolved. An I'll just create new diffs when I have something to contribute again.

Hello Aaron, actually I created this task as an umbrella for that topic; I have still some things to improve and I intend to contribute more to that topic. Note especially the point with the "dancing black borders" is not solved. Also the handling of the pivot point can be bettered (and I know how). And, some people proposed different approaches to the same problem, like using a lowpass filter on the track data Only the immediate Diff [D583](https://archive.blender.org/developer/D583) is closed and released, which resolved the most pressing issues. Indeed I am unsure how such an ongoing effort is managed in Blender. Someone recommended me to create such an umbrella task. But I do not mind if you close it, just lets's make it clear in the text then, that it is only closed for technical reasons, not really resolved. An I'll just create new diffs when I have something to contribute again.
Member

I will re-open then.

I will re-open then.

Added subscriber: @daveoelen

Added subscriber: @daveoelen
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
5 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#49036
No description provided.