Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gstreamer gstreamer
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 669
    • Issues 669
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 346
    • Merge requests 346
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gstreamergstreamer
  • Issues
  • #955

Closed
Open
Created Jan 13, 2022 by Dan Ulery@dan.ulery

Filesink overwrite option

It would be helpful if filesink could have an option to use mode rb+. Perhaps an overwrite property in addition to append.

The use case in mind is when using splitmuxsink running 24x7 to record security camera video. The current implementation will start writing new files. When max-files is reached, it will then start overwriting the oldest existing file. The problem is that it causes disk fragmentation.

The hope is that we can pre-allocate files large enough for the largest possible splitmuxsink output, defragment the disk, and then specify to the filesink that we want rb+ in order to keep fragmentation from happening during recording.

Assignee
Assign to
Time tracking