Somehow strange to declare an obvious malfunction not as a bug... )-;
it's just not doing what it is supposed to do...

Talked to @Sergey Sharybin (sergey), this is not considered a bug for now, but might see improvement in the near future (in that it is appealing to handle plane track differently here in concert with mask handles).

Hm, OK so the reason this happens is that the handles are set to type Auto, and if these are set to Auto, well... they are recalculated even after the plane track matrix has been applied to them, see https://developer.blender.org/diffusion/B/browse/master/source/blender/blenkernel/intern/mask_evaluate.c$898

Ah, get it now, it snaps into place when such a handle is transformed.

I think there should be at least one mobile phone preset in the list. I used the iPhone preset for all my mobile phone cameras including OnePlus and it got the solves close enough. I don't think all models need to be listed, just a few example phones to give us the ballpark figures.

On a glance seems fine.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Update against current master branch.
Lets get this patch rolling and finished!

Sounds like T92287: "Setup Tracking scene" not alligned when using vertical Videos

Hi, thanks for the report
I can confirm. Will submit a patch quickly. (Definitely was introduced after python 3.10 switch)

Moving to next release since 3.1 is bug fixing only at this point.

Good to see this getting active again (sort of).
Since there is not much the #triaging team can do, I think it is up to Motion Tracking devs to decide on status here.

I tested the behavior on blender 2.70 (I'm happy to have forgotten those times) and it behaves differently:

• at the start of the second pair of tracks (second anchor) the movie has the same rotation as the end of the first track pair

The oldest blender version I have available right now is 2.81 and it shows the same behavior as the current versions. Seems to be an old bug.

Has this worked in a previous release? https://download.blender.org/release/

@Sergey Sharybin (sergey), After such a long time, I would like to continue what I started.

@Pratik Borhade (PratikPB2123) Current design is still not confirmed by module owners because we need to find the best solution from side of user experience. I wish one day I would see the same task status change authored by someone of them, but before it still should be discussed. Any way, the latest coommit you saw has no reviewer beacause first things first I need to summarize all previous discussion. I think the best way to do that is to implement it in my own local branch and than, a lot of hidden questions would be solved faster.

Will have to concentrate on triaging for a while (and step down).

On closer inspection, the image sequence is also not a bug. It is necessary to indicate in the created node that the dropped image is part of a sequence.

Thanks for the report I can confirm the image sequence problem. But I'm not sure about the other problem which is grabbing and dropping multiple images (not sequencing) at the same time. Has this been supported before?
Note, to properly track issues we need them to be reported separately.

Caused by rB7e66616b7e1.

I recall this being an issue before, and seem to vaguely recall it getting fixed. Best I can find is rB630cb1bb1de1: Clip Editor: Fix visualization of plane track image which has too vague of a commit message to confirm it is the possible previous fix I am thinking about. @Sergey Sharybin (sergey) does that commit seem familiar/relevant?