aom: rtc: Set mv search_method to fast_diamond under high motion

From e96d878eb369515211598051b5bb2eb553f78eca Mon Sep 17 00:00:00 2001
From: Marco Paniconi <[EMAIL REDACTED]>
Date: Thu, 27 Jun 2024 15:09:59 -0700
Subject: [PATCH] rtc: Set mv search_method to fast_diamond under high motion

For speed >= 11, under high motion screen content flag, set
the mv_search_method to fast_diamond for all frames, otherwise
for temporal layers the TL0 frame was being set to diamond
(which is slower); the TL1/TL2 frames were already being set
to fast_diamond.

This only affects temporal layers.
Measured ~5% speedup with small pnsr loss (< 0.05dB), for
high motion screen content clip at speed 11 with 2TL.

Change-Id: I070470b276e489a89dd814fda0d050fde2963c2c
---
 av1/encoder/speed_features.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/av1/encoder/speed_features.c b/av1/encoder/speed_features.c
index 4b6ea16d7f..e0709b15ad 100644
--- a/av1/encoder/speed_features.c
+++ b/av1/encoder/speed_features.c
@@ -1616,6 +1616,7 @@ static void set_rt_speed_feature_framesize_dependent(const AV1_COMP *const cpi,
       sf->rt_sf.use_fast_fixed_part = 1;
       sf->rt_sf.increase_source_sad_thresh = 1;
       sf->rt_sf.selective_cdf_update = 1;
+      sf->mv_sf.search_method = FAST_DIAMOND;
     } else if (cpi->rc.max_block_source_sad > 20000 &&
                cpi->rc.frame_source_sad > 100 && speed >= 6 &&
                (cpi->rc.percent_blocks_with_motion > 1 ||