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.

diff --git a/gst/multifile/gstsplitmuxsink.c b/gst/multifile/gstsplitmuxsink.c
index c2f581aedb97e7e404fcffc038bab50527399018..373b671d7d300fe8c25b16d1d66a1900483e9fa8 100644 (file)
--- 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 */