[gstreamer-bugs] [Bug 564482] New: [appsrc] semantics of push-buffer signal awkward for bindings

[GStreamer (bugzilla.gnome.org)]

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=564482

  GStreamer | gst-plugins-bad | Ver: HEAD CVS
           Summary: [appsrc] semantics of push-buffer signal awkward for
                    bindings
           Product: GStreamer
           Version: HEAD CVS
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: t.i.m at zen.co.uk
         QAContact: gstreamer-bugs at lists.sourceforge.net
OtherBugsDependingO 564421
             nThis:
     GNOME version: Unspecified
   GNOME milestone: Unspecified


The 'push-buffer' signal takes ownership of the buffer argument when doing

  g_signal_emit_by_name (appsrc, 'push-buffer', buf);

This is unintuitive (no other g* api behaves that way afaik), and also broken
for bindings, which usually don't provide API to do an explicit
gst_buffer_ref() on the C buffer, which they'd need to use this signal, so
(AFAICT) it's pretty much impossible to do an appsrc.signal_emit_by_name
('push', buf) in gst-python.

I think we should change the behaviour here.

Arguably, eventually libgstapp* would be in -base and bound and apps would just
use that, but I still think it's worth fixing.


-- 
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=564482.