Clip random marker placement in track/mask - not working in 2.8 #57646

New Issue

Tzvi · 2018-11-06T08:09:10+01:00

Tzvi commented

2018-11-06 08:09:10 +01:00

System Information
Windows 10 x64 with nVidia 1080

Blender Version
Broken: 2.80, 2.83 @ be8879718e
Worked: 2.79 (because there was no collapsible floating redo panel)

It's impossible to add a mask (or tracking) using ctrl+left-click in the clip editor.

Exact steps for others to reproduce the error

#57646-clip-marker-placement.zip

Open the above blend file, or:
- Start Blender in factory settings.
- Add a VFX → Motion Tracking workspace.
- Load a video file into the clip editor.
{key Ctrl Click} in the clip editor to add a marker.
Open the redo panel.
{key Ctrl Click} in the clip editor to add a marker, and see that the marker appears at an offset.
{key Ctrl Click} again and see that the position is now correct.
Close the redo panel.
{key Ctrl Click} in the clip editor to add a marker, and see that the marker appears at an offset.
{key Ctrl Click} again and see that the position is now correct.

**System Information** Windows 10 x64 with nVidia 1080 **Blender Version** Broken: 2.80, 2.83 @ be8879718e24e417d299eb298b8a9d4d2ca324ee Worked: 2.79 (because there was no collapsible floating redo panel) It's impossible to add a mask (or tracking) using ctrl+left-click in the clip editor. **Exact steps for others to reproduce the error** [#57646-clip-marker-placement.zip](https://archive.blender.org/developer/F8334523/T57646-clip-marker-placement.zip) - Open the above blend file, or: - Start Blender in factory settings. - Add a VFX → Motion Tracking workspace. - Load a video file into the clip editor. - {key Ctrl Click} in the clip editor to add a marker. - Open the redo panel. - {key Ctrl Click} in the clip editor to add a marker, and see that the marker appears at an offset. - {key Ctrl Click} again and see that the position is now correct. - Close the redo panel. - {key Ctrl Click} in the clip editor to add a marker, and see that the marker appears at an offset. - {key Ctrl Click} again and see that the position is now correct.

Tzvi commented

2018-11-06 08:09:10 +01:00

Added subscriber: @zvi8

Philipp Oeser commented

2018-11-06 13:40:04 +01:00

Added subscriber: @lichtwerk

Philipp Oeser self-assigned this 2018-11-06 13:40:04 +01:00

Philipp Oeser commented

2018-11-06 13:40:04 +01:00

With current 2.8 I am not getting this with tracking markers (although the very first seemed to be off), but consistently with masking points.
Has to do with pixel size / UI scale [only happens when I change this in the User Preferences].

Think I can find a fix...

With current 2.8 I am not getting this with tracking markers (although the very first seemed to be off), but consistently with masking points. Has to do with pixel size / UI scale [only happens when I change this in the User Preferences]. Think I can find a fix...

Philipp Oeser removed their assignment 2018-11-14 16:01:09 +01:00

Campbell Barton was assigned by Philipp Oeser

2018-11-14 16:01:09 +01:00

Philipp Oeser commented

2018-11-14 16:01:09 +01:00

Added subscriber: @ideasman42

Philipp Oeser commented

2018-11-14 16:01:09 +01:00

Well, maybe I spoke too soon (regarding finding the fix).

I assume this is related to the HUD/redo thingie somewhat messing with the region size.
To recap: as of 4722003ca5 it is not as bad as in the video anymore.
What I am seeing now is that the first click goes fine, the second is off, third click and everything after is fine again.

And I can only trigger this if Display Scale in User Preferences is not 1 (1.02 is enough though to make the second click go way off...)

What can be observed is that (I checked in ED_space_clip_get_zoom()and whats returned in ED_clip_point_stable_pos()):

ar->v2d.cur values are different for two clicks in the same position (when UI Scale is 1.02)
ar->v2d.cur values are the same for two clicks in the same position (when UI Scale is 1.0)

// with UI Scale
ar->v2d.cur 0.029661 0.626059 0.234463 0.673258
ED_clip_point_stable_pos zoom 1.000000 1.000000
ar->v2d.cur 0.000000 1.126000 0.220861 0.686861
ED_clip_point_stable_pos zoom 0.529661 0.941619

// without UI Scale
ar->v2d.cur 0.021716 0.634004 0.233522 0.674200
ED_clip_point_stable_pos zoom 1.000000 1.000000
ar->v2d.cur 0.021716 0.634004 0.233522 0.674200
ED_clip_point_stable_pos zoom 1.000000 1.000000

note: CLIP_OT_add_marker_at_click is always OK (but thats probably because it has no redo and thus no HUD for redo)

@ideasman42 : you were active for the HUD (and I also remember commits regarding the action zones coming in the way - which might be related), could you have a look?

Well, maybe I spoke too soon (regarding finding the fix). I assume this is related to the HUD/redo thingie somewhat messing with the region size. To recap: as of 4722003ca5 it is not as bad as in the video anymore. What I am seeing now is that the first click goes fine, the second is off, third click and everything after is fine again. And I can only trigger this if Display Scale in User Preferences is not 1 (1.02 is enough though to make the second click go way off...) What can be observed is that (I checked in `ED_space_clip_get_zoom()`and whats returned in `ED_clip_point_stable_pos()`): - ar->v2d.cur values are different for two clicks in the same position (when UI Scale is 1.02) - ar->v2d.cur values are the same for two clicks in the same position (when UI Scale is 1.0) ``` // with UI Scale ar->v2d.cur 0.029661 0.626059 0.234463 0.673258 ED_clip_point_stable_pos zoom 1.000000 1.000000 ar->v2d.cur 0.000000 1.126000 0.220861 0.686861 ED_clip_point_stable_pos zoom 0.529661 0.941619 // without UI Scale ar->v2d.cur 0.021716 0.634004 0.233522 0.674200 ED_clip_point_stable_pos zoom 1.000000 1.000000 ar->v2d.cur 0.021716 0.634004 0.233522 0.674200 ED_clip_point_stable_pos zoom 1.000000 1.000000 ``` note: CLIP_OT_add_marker_at_click is always OK (but thats probably because it has no redo and thus no HUD for redo) @ideasman42 : you were active for the HUD (and I also remember commits regarding the action zones coming in the way - which might be related), could you have a look?

Tzvi commented

2018-11-15 08:46:09 +01:00

What I noticed is that if the mouse cursor is near the left side of the clip window (the pane itself, not the video clip, you can zoom out and have a really small video clip in the pane to exaggerate this) then the markers are placed at the left side of the video clip. This tends to drift away as you move the mouse cursor to the right.
I would guess that the placement is based on the pane's boundaries (and has some scale factor) and not the actual clip's boundaries.

What I noticed is that if the mouse cursor is near the left side of the clip window (the pane itself, not the video clip, you can zoom out and have a really small video clip in the pane to exaggerate this) then the markers are placed at the left side of the video clip. This tends to drift away as you move the mouse cursor to the right. I would guess that the placement is based on the pane's boundaries (and has some scale factor) and not the actual clip's boundaries.

Tzvi commented

2018-11-16 22:16:21 +01:00

I've been playing a bit (with the latest build) and I noticed that the problem tends to go away whenever you fold the contextual "Add Marker and Slide" overlay, and returns whenever you unfold it back.
To clarify what I'm talking about I took a short video:
https://drive.google.com/open?id=1rNMx47oucsqujLZSm_NL4CzCVy7WMx4x

I've been playing a bit (with the latest build) and I noticed that the problem tends to go away whenever you fold the contextual "Add Marker and Slide" overlay, and returns whenever you unfold it back. To clarify what I'm talking about I took a short video: https://drive.google.com/open?id=1rNMx47oucsqujLZSm_NL4CzCVy7WMx4x

Tzvi commented

2018-11-28 08:48:36 +01:00

Hi, it's my understanding that the community is gearing up towards a 2.8 beta release and I was wondering if there is any insight regarding this issue?
I'm asking because without tracking or masking, the video editing module has a very limited usability. I did notice (in my recent video above) that the problem goes away whenever you fold the contextual window, and returns whenever you unfold it - so it's probably related to it somehow.
Video showing how the problem disappears and reappears

Hi, it's my understanding that the community is gearing up towards a 2.8 beta release and I was wondering if there is any insight regarding this issue? I'm asking because without tracking or masking, the video editing module has a very limited usability. I did notice (in my recent video above) that the problem goes away whenever you fold the contextual window, and returns whenever you unfold it - so it's probably related to it somehow. [Video showing how the problem disappears and reappears ](https://drive.google.com/open?id=1rNMx47oucsqujLZSm_NL4CzCVy7WMx4x)

Sebastian Koenig commented

2018-11-28 09:02:48 +01:00

Added subscriber: @sebastian_k

Sebastian Koenig commented

2018-11-28 09:02:48 +01:00

I tried it with several configurations, but couldn't reproduce it. Toolshelf and Sidebar expanded or collapsed, floating panel expaneded or collapsed, fullscreen or not - I could not reproduce this bug in any case. I am on Linux though. Might be a Windows bug?

Philipp Oeser commented

2018-11-28 09:23:53 +01:00

@sebastian_k: You should be able to reproduce with User Preferences > Interface > Display Scale other than 1.0?

@sebastian_k: You should be able to reproduce with `User Preferences` > `Interface` > `Display Scale` other than 1.0?

Sebastian Koenig commented

2018-11-28 10:50:31 +01:00

Ah indeed. Can only reproduce with mask points though as well, not with tracking markers.

Tzvi commented

2018-11-28 20:18:34 +01:00

Well, I'm using the Windows x64 build of Blender 2.8 (running on windows 10 x64). This behavior perfectly reproducible (as my videos show) - but it does not happen with the 2.7.
It occurs with both masks and tracking markers in my case. Also checked my "Display Scale" - it is set to 1.00
Are there any useful logs I can enable and provide to debug this?

On a hunch, I decided to test one more thing!
I use a dual monitor desktop, my primary is a 4K display and my secondary is a 1080p display.
This problem manifests itself on the 4K display but when I drag Blender into the secondary display and set it to full screen, everything works as expected. Dragging back to the 4K display it goes awry again.

I know that Windows has internally some "scale" factor, because when I drag applications from primary to secondary they rescale themselves accordingly. (otherwise the fonts would appear too large/small)
Can this be responsible to the coordinates drift?

Well, I'm using the Windows x64 build of Blender 2.8 (running on windows 10 x64). This behavior perfectly reproducible (as my videos show) - but it does not happen with the 2.7. It occurs with both masks and tracking markers in my case. Also checked my "Display Scale" - it is set to 1.00 Are there any useful logs I can enable and provide to debug this? On a hunch, I decided to test one more thing! I use a dual monitor desktop, my primary is a 4K display and my secondary is a 1080p display. This problem manifests itself on the 4K display but when I drag Blender into the secondary display and set it to full screen, everything works as expected. Dragging back to the 4K display it goes awry again. I know that Windows has internally some "scale" factor, because when I drag applications from primary to secondary they rescale themselves accordingly. (otherwise the fonts would appear too large/small) Can this be responsible to the coordinates drift?

Tzvi commented

2018-12-23 13:03:34 +01:00

Hi Sebastian. I understand you were able to reproduce the issue as well, have you found the cause for the tracking markers not working?
Mind you, I have "Display Scale" set to 1.0 - however it's possible that since I have dual 4K + FHD monitors that Windows presents its own scaling factor?

I have created a new video showing exactly how it behaves strangely on mu dual monitor Windows machine.
Video demonstrating the issues

Also attached a screenshot showing the Blender and Windows scaling factors.

Hi Sebastian. I understand you were able to reproduce the issue as well, have you found the cause for the tracking markers not working? Mind you, I have "Display Scale" set to 1.0 - however it's possible that since I have dual 4K + FHD monitors that Windows presents its own scaling factor? I have created a new video showing exactly how it behaves strangely on mu dual monitor Windows machine. [Video demonstrating the issues](https://drive.google.com/open?id=1H21xIgYNu95BV-H8HwI9iGH1yvAXxWJ8) Also attached a screenshot showing the Blender and Windows scaling factors. ![scaling-factors.jpg](https://archive.blender.org/developer/F6044490/scaling-factors.jpg)

Philipp Oeser commented

2018-12-28 11:24:04 +01:00

Changed status from 'Open' to: 'Resolved'

Philipp Oeser closed this issue

2018-12-28 11:24:04 +01:00

Philipp Oeser commented

2018-12-28 11:24:04 +01:00

I believe this was fixed by e5e885d0ec?
As of today (fdc726eb61) I am not able to reproduce this anymore...

Marking as resolved, please everyone, feel free to comment again or reopen if issues persist...

I believe this was fixed by e5e885d0ec? As of today (fdc726eb61) I am not able to reproduce this anymore... Marking as resolved, please everyone, feel free to comment again or reopen if issues persist...

Tzvi commented

2018-12-29 07:01:19 +01:00

Changed status from 'Resolved' to: 'Open'

Tzvi reopened this issue

2018-12-29 07:01:19 +01:00

Tzvi commented

2018-12-29 07:01:19 +01:00

Hi, excellent work! It seems that this commit fixes it almost entirely!
However, there's still one case where this behavior persists. Whenever the floating panel is collapsed, the first click afterwards still places a marker at an offset. All the following markers are placed correctly.
This indicates that there is still an issue lurking in there.
Here's a quick video demonstrating it.

Hi, excellent work! It seems that this commit fixes it almost entirely! However, there's still one case where this behavior persists. Whenever the floating panel is **collapsed**, the **first click** afterwards still places a marker at an offset. All the following markers are placed correctly. This indicates that there is still an issue lurking in there. Here's a [quick video demonstrating](https://drive.google.com/open?id=1wW8QOkhBoIs9cjk7_tk0tm9o5lOJZD3C) it.

Campbell Barton was unassigned by Dalai Felinto

2019-12-23 16:35:52 +01:00

Sybren A. Stüvel commented

2020-02-11 11:32:29 +01:00

Added subscriber: @dr.sybren

Sybren A. Stüvel commented

2020-02-11 11:32:29 +01:00

I can confirm this still happens on current master (be8879718e). Whenever the redo panel is opened or closed, the first {key Ctrl Click} will be in the wrong position.

I can confirm this still happens on current master (be8879718e). Whenever the redo panel is opened or closed, the first {key Ctrl Click} will be in the wrong position.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Clip random marker placement in track/mask - not working in 2.8 #57646