Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-good gst-plugins-good
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 648
    • Issues 648
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 82
    • Merge requests 82
  • 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
  • gst-plugins-goodgst-plugins-good
  • Issues
  • #141

Closed
Open
Created Nov 11, 2014 by Bugzilla Migration User@bugzilla-migration

multifilesink: Add a property to disable writing streamheaders on new files

Submitted by clo..@..il.com

Link to original bug (#739979)

Description

Currently, the multifilesink will check its GstCaps for a "streamheader" value. If this value exists, it will then generate a header for each file.

However, there are several instances where being able to treat each file generated by the multifilesink as a continuation of the previous file.

In no particular order, and this is not an exhaustive list:

1 - splitfilesrc playback. This element treats a set of files as one large contiguous file. Unfortunately, headers mess up a variety of demuxers.
2 - moving files between file systems. For example, FAT32, common on SDCards, is limited to 4GB files. Being able to binary concatenate files together when transferred to a file system without such a limit would be very useful.

To solve this, I propose adding a "write-stream-headers" property, whose default is "true" (to preserve current behavior), but when set to "false" will not write "streamheader" information from GstCaps into the resulting files.

Version: 1.4.3

Assignee
Assign to
Time tracking