"Setup Tracking scene" not alligned when using vertical Videos #92287

New Issue

vprime · 2021-10-17T12:21:40+02:00

vprime commented

2021-10-17 12:21:40 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-29 22:05, hash: 84dcf12ceb
Worked: not sure
Short description of error
Noticed that all vertical videos(horizontal video with frames extracted with -90 offset) I tracked using the smartphone and dslr source were not alligned with the tracking marker empties when "Setup Tracking scene" was done

when used horizontally it works perfect but difficult to interact with blender sideways

rendered video rotated on export: https://twitter.com/v6_prime/status/1447977113303220226?s=20

Exact steps for others to reproduce the error

Use any vertical video
track and solve
do " setup tracking scene"
the tracking empties should be misaligned with the video in the 3d scene

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1650/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-09-29 22:05, hash: `84dcf12ceb` Worked: not sure **Short description of error** Noticed that all vertical videos(horizontal video with frames extracted with -90 offset) I tracked using the smartphone and dslr source were not alligned with the tracking marker empties when "Setup Tracking scene" was done ![rotated.jpg](https://archive.blender.org/developer/F11204497/rotated.jpg) when used horizontally it works perfect but difficult to interact with blender sideways ![FB37gZOVUAcR7uW.jpg](https://archive.blender.org/developer/F11204504/FB37gZOVUAcR7uW.jpg) rendered video rotated on export: https://twitter.com/v6_prime/status/1447977113303220226?s=20 **Exact steps for others to reproduce the error** - Use any vertical video - track and solve - do " setup tracking scene" - the tracking empties should be misaligned with the video in the 3d scene

vprime commented

2021-10-17 12:21:40 +02:00

Added subscriber: @V-prime

Philipp Oeser commented

2021-10-19 12:26:54 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-10-19 12:26:54 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Philipp Oeser commented

2021-10-19 12:26:54 +02:00

Hi and thx for the report.
To speed things up, please attach the (already rotated) source movie and the corresponding .blend file (with tracking, prior to setup tracking scene).

Hi and thx for the report. To speed things up, please attach the (already rotated) source movie and the corresponding .blend file (with tracking, prior to `setup tracking scene`).

vprime commented

2021-10-19 12:49:03 +02:00

the frame sizes were too high so i just put 12 frames + the original blend file with 'setup tracking scene' ready to be pressed
track test 12 frames.zip

SourceVideo15sec.zip

the frame sizes were too high so i just put 12 frames + the original blend file with 'setup tracking scene' ready to be pressed [track test 12 frames.zip](https://archive.blender.org/developer/F11281466/track_test_12_frames.zip) [SourceVideo15sec.zip](https://archive.blender.org/developer/F11281572/SourceVideo15sec.zip)

Philipp Oeser commented

2021-10-19 12:54:55 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Philipp Oeser commented

2021-10-19 15:02:49 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2021-10-19 15:02:49 +02:00

Hm, not totally sure if this is a bug (but I also cannot make it work).
No expert in tracking here, so afraid I'll have to pass this on to someone else with more knowledge.
I've tried different camera presets (since camera sensor of course makes a difference), but pretty sure this is not the source of the problem.
Just dropping the ffmpeg info on the file (it contains the rotate property), but pretty sure this is not the source of the problem either.

Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/T92287/SourceVideo15sec/SourceVideo.mp4':
  Metadata:
    major_brand     : mp42
    minor_version   : 0
    compatible_brands: isommp42
    creation_time   : 2021-10-16T08:00:42.000000Z
    location        : +15.6265+073.7982/
    location-eng    : +15.6265+073.7982/
    com.android.version: 11
    com.android.capture.fps: 30.000000
  Duration: 00:00:15.51, start: 0.000000, bitrate: 20359 kb/s
  Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080, 20006 kb/s, SAR 1:1 DAR 16:9, 29.89 fps, 29.92 tbr, 90k tbn, 180k tbc (default)
    Metadata:
      rotate          : 90
      creation_time   : 2021-10-16T08:00:42.000000Z
      handler_name    : VideoHandle
      vendor_id       : [0][0][0][0]
    Side data:
      displaymatrix: rotation of -90.00 degrees

Could it be that basing the focal length on the width (always) is not correct?
https://developer.blender.org/diffusion/B/browse/master/source/blender/blenkernel/intern/movieclip.c$1014
(but this is also a stab in the dark without checking further)

Hm, not totally sure if this is a bug (but I also cannot make it work). No expert in tracking here, so afraid I'll have to pass this on to someone else with more knowledge. I've tried different camera presets (since camera sensor of course makes a difference), but pretty sure this is not the source of the problem. Just dropping the ffmpeg info on the file (it contains the `rotate` property), but pretty sure this is not the source of the problem either. ``` Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/T92287/SourceVideo15sec/SourceVideo.mp4': Metadata: major_brand : mp42 minor_version : 0 compatible_brands: isommp42 creation_time : 2021-10-16T08:00:42.000000Z location : +15.6265+073.7982/ location-eng : +15.6265+073.7982/ com.android.version: 11 com.android.capture.fps: 30.000000 Duration: 00:00:15.51, start: 0.000000, bitrate: 20359 kb/s Stream #0:0(eng): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 1920x1080, 20006 kb/s, SAR 1:1 DAR 16:9, 29.89 fps, 29.92 tbr, 90k tbn, 180k tbc (default) Metadata: rotate : 90 creation_time : 2021-10-16T08:00:42.000000Z handler_name : VideoHandle vendor_id : [0][0][0][0] Side data: displaymatrix: rotation of -90.00 degrees ``` Could it be that basing the focal length on the width (always) is not correct? https://developer.blender.org/diffusion/B/browse/master/source/blender/blenkernel/intern/movieclip.c$1014 (but this is also a stab in the dark without checking further)

K.nao commented

2022-08-22 22:46:58 +02:00

Added subscriber: @KNAO

K.nao commented

2022-08-22 22:46:58 +02:00

This problem occurs because the "Sensor Fit" of the camera property in the 3D scene is switched to "Auto" when the "Solve Camera Mostion" is executed.
In the case of Vertical Videos, the Movie clip editor specifies the short edge value as the Sensor Width, but when the "Solve Camera Mostion" is executed, the "Sensor Fit” is set to "Auto," and the height of the long side is set to the value specified in the movie clip editor based on the aspect ratio of the image.
As a result, the sensor values of the camera sensors in the 3D scene are not correct and the result will not be reflected correctly.
Currently, the problem can be solved by switching "Sensor Fit" to "Horizontal". However, when "Solve Camera Mostion" is executed, it will switch to "Auto" again.
Ideally, when the "Solve Camera Motion" is executed, the "Sensor Fit" of the 3D scene camera is switched to "Horizontal", and the "Height" value is automatically calculated from the image resolution ratio.
If the height value is automatically calculated, troubles are less likely to occur when exporting to external software.

This problem occurs because the "Sensor Fit" of the camera property in the 3D scene is switched to "Auto" when the "Solve Camera Mostion" is executed. In the case of Vertical Videos, the Movie clip editor specifies the short edge value as the Sensor Width, but when the "Solve Camera Mostion" is executed, the "Sensor Fit” is set to "Auto," and the height of the long side is set to the value specified in the movie clip editor based on the aspect ratio of the image. As a result, the sensor values of the camera sensors in the 3D scene are not correct and the result will not be reflected correctly. Currently, the problem can be solved by switching "Sensor Fit" to "Horizontal". However, when "Solve Camera Mostion" is executed, it will switch to "Auto" again. Ideally, when the "Solve Camera Motion" is executed, the "Sensor Fit" of the 3D scene camera is switched to "Horizontal", and the "Height" value is automatically calculated from the image resolution ratio. If the height value is automatically calculated, troubles are less likely to occur when exporting to external software. ![image.png](https://archive.blender.org/developer/F13411856/image.png)

Peter Goodman commented

2022-12-29 16:09:30 +01:00

Added subscriber: @badbunny_uk

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

"Setup Tracking scene" not alligned when using vertical Videos #92287