Regression: Compositor Track Position node outputs incorrect Y values for Relative Start & Relative Frame #108492

New Issue

WhazzItToYa · 2023-06-01T06:55:04+02:00

WhazzItToYa commented

2023-06-01 06:55:04 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03

Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3
Worked: at least 3.2.2. Have not tried any newer versions other than 3.5.1

Caused by e0c5ff87b7

Short description of error
The Track Position node in the compositor returns the wrong value for Y, when in Relative Start and Relative Frame mode. It appears to offsetting the Y position by the positive Y value of the marker frame, instead of subtracting.

Probably due to this line, which looks like a copy & paste error from processing the X axis: 63f2114759/source/blender/compositor/nodes/COM_TrackPositionNode.cc (L77)

Exact steps for others to reproduce the error

In video editing, make a motion tracking marker at frame 1, whose initial position is not 0,0
In compositor node graph, add an Image -> Translate -> Alpha Over (with appropriate background image) -> Viewer pipeline.
Create a Track Position node with Position=Relative Start, and feed X,Y into Translate node.
Move playhead to frame 1

RESULT: Image will be translated by (0, Marker.Y), not the expected (0, 0)

The attached .blend (and supporting .mkv) contains a clip of an ellipse moving from the lower-left to upper-right, and a marker tracking it.
The green crosshair is positioned to be approximately centered on the first frame of the marker's x,y. The red is positioned at the same location, but with a translation of the tracker's relative start applied to it. On the first frame, it is expected to be where the green crosshair is, but instead, it is shifted up.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 532.03 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` Worked: at least 3.2.2. Have not tried any newer versions other than 3.5.1 Caused by e0c5ff87b702 **Short description of error** The Track Position node in the compositor returns the wrong value for Y, when in Relative Start and Relative Frame mode. It appears to offsetting the Y position by the positive Y value of the marker frame, instead of subtracting. Probably due to this line, which looks like a copy & paste error from processing the X axis: https://projects.blender.org/blender/blender/src/commit/63f211475950895632c826969daf4c9894554d8a/source/blender/compositor/nodes/COM_TrackPositionNode.cc#L77 **Exact steps for others to reproduce the error** 1) In video editing, make a motion tracking marker at frame 1, whose initial position is not 0,0 2) In compositor node graph, add an Image -> Translate -> Alpha Over (with appropriate background image) -> Viewer pipeline. 3) Create a Track Position node with Position=Relative Start, and feed X,Y into Translate node. 4) Move playhead to frame 1 RESULT: Image will be translated by (0, Marker.Y), not the expected (0, 0) The attached .blend (and supporting .mkv) contains a clip of an ellipse moving from the lower-left to upper-right, and a marker tracking it. The green crosshair is positioned to be approximately centered on the first frame of the marker's x,y. The red is positioned at the same location, but with a translation of the tracker's relative start applied to it. On the first frame, it is expected to be where the green crosshair is, but instead, it is shifted up.

relative-y-offset-tracker-bug.blend

1.0 MiB

motion.mp40001-0108.mkv

47 KiB

WhazzItToYa added the

labels 2023-06-01 06:55:04 +02:00

WhazzItToYa commented

2023-06-01 07:05:55 +02:00

Forgot to say, this was working as expected at least as late as 3.2.2. I noticed the problem when I loaded a project that I had created in 3.2.2 using motion tracked compositing, into 3.5.1. Elements in the compositor were positioned higher than they were in 3.2's compositor.

Iliya Katushenock added the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Regression: Compositor Track Position node outputs incorrect Y values for Relative Start & Relative Frame #108492