From d955ce11706071cdc39bdaba27eb1cff177533f9 Mon Sep 17 00:00:00 2001 From: Sergey Sharybin Date: Mon, 22 Mar 2021 15:16:07 +0100 Subject: Fix T86591: Tracking backwards is slower The root of the issue was caused by the PredictMarkerPosition() always returning false when tracking backwards. This was making it so tracker always had to run brute initialization, which is an expensive operation. From own timing here: - Tracking forward takes 0.667637 seconds - Tracking backward used to take 2.591856 seconds - Tracking backward now takes 0.827724 seconds This is a very nice speedup, although the tracking backwards is still somewhat slower. Will be investigated further as part of a regular development. --- intern/libmv/libmv/autotrack/predict_tracks.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'intern') diff --git a/intern/libmv/libmv/autotrack/predict_tracks.cc b/intern/libmv/libmv/autotrack/predict_tracks.cc index f3411066a07..473be95ac2f 100644 --- a/intern/libmv/libmv/autotrack/predict_tracks.cc +++ b/intern/libmv/libmv/autotrack/predict_tracks.cc @@ -337,7 +337,7 @@ bool PredictMarkerPosition(const Tracks& tracks, previous_markers.push_back(boxed_markers[i]); } RunPrediction(previous_markers, marker); - return false; + return true; } } -- cgit v1.2.3