GNOME Bugzilla – Bug 773506
splitmuxsink: add support for monotonic file index increment
Last modified: 2018-11-03 15:13:11 UTC
Splitmuxsink currently rotates the file index i.e., 0, 1 , 2, 3, 0, 1, 2, 3... and so on rather than incrementing monotonically. This can be added as a property
it does?
No rolls over once max file is reached and rolls back to index 0
Interesting. I wonder if that's intentional or a bug. I would have expected it to simply delete old files but continue with the numbering. Jan?
Is it by design because splitmuxsink will not have capability to delete files from sinks such as curlftpsink/curlhttpsink, hence rotate the same files?
Correct, splitmuxsink has no knowledge of the actual storage - it just sets a location on a sink element. There's no API by which it could request file deletion.
Understandable. It would be a good feature enhancement if it can be done, provided file deletion API is supported in future
FWIW, you can use the format-location signal to manually set any pattern / sequence of filename you like, and the splitmuxsink-fragment-opened and splitmuxsink-fragment-closed bus messages to know when it starts/stops using a particular file.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/312.