After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 582451 - [multifilesink] Multiple buffers for file
[multifilesink] Multiple buffers for file
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
git master
Other All
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-13 10:35 UTC by Miguel Angel Cabrera Moya
Modified: 2011-05-23 08:30 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Miguel Angel Cabrera Moya 2009-05-13 10:35:46 UTC 
It would be nice to have a property in multifilesink to configure the number of buffers to write for file.

Also for the use case for writing a variable number of buffers to each file would be nice to have a signal that is launched for each new file created.

Would be nice to have this for the next incoming release.

Thanks.
Comment 1 David Schleef 2009-05-13 16:31:06 UTC 
multifilesink is for convenience in scripting, not for applications.  Applications can fully control how buffers are written out to files by using filesink or appsink.

Can you give an example of how you would use it in this way?
Comment 2 Miguel Angel Cabrera Moya 2009-05-13 19:37:10 UTC 
Yes, applications can control buffers written out, but i think that will be easier to just integrate that on multfilesink. It seems the best option to simplify control logic in applications and also it is a nice place to put that functionality.

Particularly i will use it to split big input streams in little chunks.
Comment 3 David Schleef 2009-09-14 03:06:34 UTC 
I just added a property to create a new file after each discontinuity in the stream.  It would be much easier to add a features like this now.
Comment 4 Sebastian Dröge (slomo) 2011-05-20 06:25:08 UTC 
Is this feature request still needed?
Comment 5 Miguel Angel Cabrera Moya 2011-05-21 12:24:38 UTC 
I don't need it anymore. This can be closed.