Issue when joining offset markers #113523

New Issue

Open

opened 2023-10-11 02:06:50 +02:00 by Oliver Villar · 2 comments

Oliver Villar commented

2023-10-11 02:06:50 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13

Blender Version
Broken: version: 4.0.0 Beta, branch: blender-v4.0-release, commit date: 2023-09-28 00:03, hash: 751c9ef620a0
Worked: not sure this worked before.

Short description of error
When joining markers, if they have used offset, they'll ignore the actual center and bake the marker's offset position, creating a jump in the path.

Exact steps for others to reproduce the error

Create a tracker.
Create a second tracker in the same position, next frame.
Offset the second tracker pressing G twice or using the offset marker properties.
Select both trackers and join them with Ctrl+J.

Result: the offset of the second marker will be ignored. In the following image I show which point will be taken into account, instead of the "good" one:

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 Ti/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 537.13 **Blender Version** Broken: version: 4.0.0 Beta, branch: blender-v4.0-release, commit date: 2023-09-28 00:03, hash: `751c9ef620a0` Worked: not sure this worked before. **Short description of error** When joining markers, if they have used offset, they'll ignore the actual center and bake the marker's offset position, creating a jump in the path. **Exact steps for others to reproduce the error** 1. Create a tracker. 2. Create a second tracker in the same position, next frame. 3. Offset the second tracker pressing G twice or using the offset marker properties. 4. Select both trackers and join them with Ctrl+J. Result: the offset of the second marker will be ignored. In the following image I show which point will be taken into account, instead of the "good" one: ![image](/attachments/b6dab331-ddf7-4cd1-b95a-133b2fbcc2ac)

508 KiB

Oliver Villar added the

labels 2023-10-11 02:06:51 +02:00

Pratik Borhade commented

2023-10-11 06:21:28 +02:00

Member

I can confirm. Though I'm not sure if this is a bug or intended behavior. Need to check.

I can confirm. Though I'm not sure if this is a bug or intended behavior. Need to check.

Iliya Katushenock added the

Motion Tracking

label 2023-10-11 07:44:05 +02:00

Oliver Villar commented

2023-10-12 04:21:33 +02:00

Author

If it was done on purpose, I would wonder why, because it defeats the purpose of offset tracking. It's used precisely to keep the position of the center of a marker while tracking in a different place. If that's ignored, there is no point in using the offset. That's why I reported it; it seems to me like this is not the intended behavior.

It's also probably not something that many people might have encountered, I've been tracking probably over a hundred shots with Blender over the years, and this has been the first time I encountered the issue. Offset tracking is not that common, and that when it does get used it gets joined to a different marker reduces the chances of this happening often.

To top it off, in my experience, most people who use the motion tracker in Blender don't know that offset tracking is a thing :P

Anyway, if this was intended, I'd apreciate to know what the method behind it is, as I believe it is counterintuitive and it makes the offseting option useless when joining to another marker.

To add to my point:

As you can see in the image, the marker's path exists in the offset tracking point, not in the center of the pattern :) So it should follow that if two markers are joined, their original trajectories should be kept.

Hope this clarifies the issue! Thanks!

If it was done on purpose, I would wonder why, because it defeats the purpose of offset tracking. It's used precisely to keep the position of the center of a marker while tracking in a different place. If that's ignored, there is no point in using the offset. That's why I reported it; it seems to me like this is not the intended behavior. It's also probably not something that many people might have encountered, I've been tracking probably over a hundred shots with Blender over the years, and this has been the first time I encountered the issue. Offset tracking is not that common, and that when it does get used it gets joined to a different marker reduces the chances of this happening often. To top it off, in my experience, most people who use the motion tracker in Blender don't know that offset tracking is a thing :P Anyway, if this was intended, I'd apreciate to know what the method behind it is, as I believe it is counterintuitive and it makes the offseting option useless when joining to another marker. To add to my point: ![image](/attachments/d794853f-4b6b-4754-876b-8f19020364c5) As you can see in the image, the marker's path exists in the offset tracking point, not in the center of the pattern :) So it should follow that if two markers are joined, their original trajectories should be kept. Hope this clarifies the issue! Thanks!

82 KiB

Pratik Borhade added

and removed

labels 2023-10-16 06:27:00 +02:00

Sign in to join this conversation.

No Label

Animation & Rigging

Asset Browser Project Overview

Automated Testing

Blender Asset Bundle

Dependency Graph

Development Management

EEVEE & Viewport

Images & Movies

Motion Tracking

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Render Pipeline

Sculpt, Paint & Texture

Video Sequencer

Virtual Reality

Blender 2.8 Project

Milestone 1: Basic, Local Asset Browser

Good First Issue

Animation & Rigging

Development Management

EEVEE & Viewport

Nodes & Physics

Pipeline, Assets & IO

Platforms, Builds & Tests

Render & Cycles

Sculpt, Paint & Texture

Needs Info from Developers

Needs Information from User

No Milestone

No project

No Assignees

2 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#113523

No description provided.