[gstreamer-bugs] [Bug 490283] [multifilsrc] move to -good

[GStreamer (bugzilla.gnome.org) <bug...@bu...>]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=490283

  GStreamer | gst-plugins-bad | Ver: HEAD CVS

Tim-Philipp Müller changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |t....@ze...
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1




------- Comment #3 from Tim-Philipp Müller  2008-02-07 10:06 UTC -------
Random comments:

 - I wonder if it would make sense to use g_file_get_contents() for
   multifilesrc, it's likely to provide better error checking (this
   should be decided before the move, since it determines the filename
   encoding on win32).

 - same for multifilesink: use g_file_set_contents()?

 - would be nice if it was possible (in code, at least), to make
   multifilesrc read in a bunch of files that doesn't follow the rigid
   filename + index pattern. This could be done either by setting a
   fixed G_TYPE_STRV-type property which takes a list in advance, or
   by emitting some kind of "next" signal from the create function
   (I guess notify::index would do too, but it's not really particularly
   discoverable or intuitive), which the app could then hook up to and
   set a new filename. This stuff can always be added later of course.

 - same for multifilesink

 - multifilesink should probably error out, or at least send a warning
   message, if it receives more than one new-segment event.

 - seems to have some copy'n'paste leftovers (the lseek defines etc.)

Otherwise +1 for move.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=490283.