[Bug 666626] New: [dtmfsrc] Fixing source pad event handler

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=666626
  GStreamer | gst-plugins-bad | git

           Summary: [dtmfsrc] Fixing source pad event handler
    Classification: Platform
           Product: GStreamer
           Version: git
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
        AssignedTo: gstreamer-bugs at lists.freedesktop.org
        ReportedBy: tiagokatcipis at gmail.com
         QAContact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---


Created an attachment (id=204007)
 View: https://bugzilla.gnome.org/attachment.cgi?id=204007
 Review: https://bugzilla.gnome.org/review?bug=666626&attachment=204007

patch that fixes the source pad event handler

I had some problems using the dtmfsrc plugin on blackfin (uCLinux), taking a
look at the code, this seemed to be the problem:

gstbin.c(2375): gst_bin_do_latency_func (): /GstPipeline:pipeline3:
Failed to configure latency of 0:00:00.210000000 Internal GStreamer error:
clock problem. Please file a bug at
http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer.

Following up the cause of the error it seems that it is caused by the dtmfsrc
gst_dtmf_src_handle_event function that is always returning FALSE when the
event is not of type GST_EVENT_CUSTOM_UPSTREAM. Calling the GstBaseSrc event
function when the event is not of type GST_EVENT_CUSTOM_UPSTREAM resolved my
problem (when a latency message was received it was returning FALSE, causing
the error).

The only thing i don't understand is why it only happens on blackfin, but with
the attached patch it seems to work fine now, on blackfin and on x86.

Dont know if i handled this the right way, but at least is working now, i hope
the patch helps.

Best regards,
Tiago Katcipis

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.