Fix: User controlled pacing sync for st2110-20

A mechanism that allows the session to move
the pacing window if the current epoch is just
a little bit behind was applied to user controlled
pacing, which in turn made the scenarios where
big PTP updates or other small issues may cause
incremental delays, which is not really a problem
as long as we don't enable user controlled pacing.

Fix it by ignoring all discrepancies for user
controlled pacing scenarios (required_tai) and
just forcing the session to send the packets asap.

Author: DawidWesierski4

lib/src/st2110/st_tx_video_session.c

@@ -645,25 +645,26 @@ static int tv_sync_pacing(struct mtl_main_impl* impl, struct st_tx_video_session
         ", ptp_time %" PRIu64 "ms\n",
         __func__, idx, to_epoch, epochs, pacing->cur_epochs, ptp_time / 1000 / 1000);
     s->stat_epoch_troffset_mismatch++;
-    epochs++; /* assign to next */
-    start_time_ptp = pacing_start_time(pacing, epochs);
-    to_epoch = start_time_ptp - ptp_time;
-  }
 
-  if (to_epoch < 0) {
-    /* should never happen */
-    err("%s(%d), error to_epoch %f, ptp_time %" PRIu64 ", epochs %" PRIu64 " %" PRIu64
-        "\n",
-        __func__, idx, to_epoch, ptp_time, epochs, pacing->cur_epochs);
-    to_epoch = 0;
+    /* in case of user controlled pacing we need to send this even if late
+    as close to the user defiend time as possible*/
+    if (required_tai) {
+      to_epoch = 0;
+    } else {
+      to_epoch = start_time_ptp - ptp_time;
+      epochs++; /* assign to next */
+      start_time_ptp = pacing_start_time(pacing, epochs);
+    }
   }
 
   if (epochs > next_epochs) {
     dbg("%s(%d), epochs %" PRIu64 " next_epochs %" PRIu64 "\n", __func__, idx, epochs,
         next_epochs);
     s->stat_epoch_drop += (epochs - next_epochs);
   }
+
   if (epochs < next_epochs) s->stat_epoch_onward += (next_epochs - epochs);
+
   pacing->cur_epochs = epochs;
   pacing->cur_epoch_time = pacing_time(pacing, epochs);
   pacing->rtp_time_stamp = pacing_time_stamp(s, pacing, epochs);