From 9f6ed9ec72cfbbf525c2b89edfdcbb8917dfe5cf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sebastian=20Dr=C3=B6ge?= Date: Thu, 12 Dec 2019 18:53:00 +0200 Subject: [PATCH] splitmuxsink: Increment fragment_id even if no fragment location was provided Applications might handle locations and generally configuration of the sink by themselves instead of having splitmuxsink set the location on the sink. Nonetheless it makes sense to increment the fragment_id that is passed to the signal so that applications know which fragment is requested. --- gst/multifile/gstsplitmuxsink.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gst/multifile/gstsplitmuxsink.c b/gst/multifile/gstsplitmuxsink.c index c2f581aedb..373b671d7d 100644 --- a/gst/multifile/gstsplitmuxsink.c +++ b/gst/multifile/gstsplitmuxsink.c @@ -3175,9 +3175,9 @@ set_next_filename (GstSplitMuxSink * splitmux, MqStreamCtx * ctx) "location") != NULL) g_object_set (splitmux->sink, "location", fname, NULL); g_free (fname); - - splitmux->fragment_id++; } + + splitmux->fragment_id++; } /* called with GST_SPLITMUX_LOCK */