Blender crashes when solving motion tracking with negative frame positions. #72009

New Issue

Malte S · 2019-11-28T13:23:52+01:00

Malte S commented

2019-11-28 13:23:52 +01:00

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28

Blender Version
Broken: version: 2.81
Broken: version: 2.82 (sub 2), branch: master, commit date: 2019-11-27 20:26, hash: 4659fa5471
Worked: (optional)

Short description of error
Blender crashes when solving motion tracking with negative frame positions.

Exact steps for others to reproduce the error
Just open the attached file and klick “Solve Camera Motion”DadoTracking.blend

I believe the problem starts with importing the images as Clip. When sort by Date is enabled it picks the first image for frame 1 (in my case image 23).

Then blender checks if the number from the second image is higher or smaller. (in my case 22, so smaller).
Now blender puts the second image at frame 0.
This results in, my footage Settings showing me a frame range from -21/1

To solve the tracking, I had to enter for Keyframe A -21 and for B 1. But as soon as I click “Solve Camera Motion” Blender crashes.

**System Information** Operating system: Windows-10-10.0.18362 64 Bits Graphics card: GeForce RTX 2080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 441.28 **Blender Version** Broken: version: 2.81 Broken: version: 2.82 (sub 2), branch: master, commit date: 2019-11-27 20:26, hash: `4659fa5471` Worked: (optional) **Short description of error** Blender crashes when solving motion tracking with negative frame positions. **Exact steps for others to reproduce the error** Just open the attached file and klick “Solve Camera Motion”[DadoTracking.blend](https://archive.blender.org/developer/F8174889/DadoTracking.blend) I believe the problem starts with importing the images as Clip. When sort by Date is enabled it picks the first image for frame 1 (in my case image 23). ![Open.png](https://archive.blender.org/developer/F8174891/Open.png) Then blender checks if the number from the second image is higher or smaller. (in my case 22, so smaller). Now blender puts the second image at frame 0. This results in, my footage Settings showing me a frame range from -21/1 ![Settings.png](https://archive.blender.org/developer/F8174893/Settings.png) To solve the tracking, I had to enter for Keyframe A -21 and for B 1. But as soon as I click “Solve Camera Motion” Blender crashes. ![Solve.png](https://archive.blender.org/developer/F8174897/Solve.png)

Malte S commented

2019-11-28 13:23:52 +01:00

Added subscriber: @pandrodor

Philipp Oeser commented

2019-11-29 11:26:29 +01:00

Added subscribers: @Sergey, @lichtwerk

Philipp Oeser commented

2019-11-29 11:26:29 +01:00

Can confirm.
Looks like both issues need to be solved [importing image sequences as well as the crash for negative frames...]

CC @Sergey

Can confirm. Looks like both issues need to be solved [importing image sequences as well as the crash for negative frames...] CC @Sergey

Sergey Sharybin self-assigned this 2019-12-02 12:01:52 +01:00

Sergey Sharybin was unassigned by Dalai Felinto

2019-12-23 13:42:01 +01:00

Sergey Sharybin self-assigned this 2020-05-13 15:39:28 +02:00

Sergey Sharybin commented

2020-05-15 15:07:57 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Sergey Sharybin closed this issue

2020-05-15 15:07:57 +02:00

Sergey Sharybin commented

2020-05-15 15:07:57 +02:00

The crash is fixed in 2b36cf3118.

The frame offset I think is working as expected: whatever frame you selected is supposed to be at scene frame 1. There is no logic in Blender which looks at the second frame, everything is done based on the file name you've selected. Also, if the frame offset is deducted wrong, you can adjust it in the Footage settings.

So thanks for the report. The crash is fixed, the frame offset seems actually behave the way it is designed to (and if automatic magic fails, you can always adjust it manually).

The crash is fixed in 2b36cf3118. The frame offset I think is working as expected: whatever frame you selected is supposed to be at scene frame 1. There is no logic in Blender which looks at the second frame, everything is done based on the file name you've selected. Also, if the frame offset is deducted wrong, you can adjust it in the Footage settings. So thanks for the report. The crash is fixed, the frame offset seems actually behave the way it is designed to (and if automatic magic fails, you can always adjust it manually).

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender crashes when solving motion tracking with negative frame positions. #72009