[Bug 760550] parse-launch: improve possibly misleading error message when linking two elements with filter caps

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=760550

--- Comment #3 from Tim-Philipp Müller <t.i.m at zen.co.uk> ---
Created attachment 339668
  --> https://bugzilla.gnome.org/attachment.cgi?id=339668&action=edit
parse: better error message when linking two elements with capsfilter fails

First stab at this. Far from perfect, but does something.

$ gst-launch-1.0 audiotestsrc ! ximagesink
WARNING: could not link audiotestsrc0 to ximagesink0

$ gst-launch-1.0 audiotestsrc ! audio/x-raw ! ximagesink
WARNING: could not link audiotestsrc0 to ximagesink0, ximagesink0 can't handle
caps audio/x-raw

$ gst-launch-1.0 audiotestsrc ! audio/mpeg ! ximagesink
WARNING: could not link audiotestsrc0 to ximagesink0, neither element can
handle caps audio/mpeg

$ gst-launch-1.0 audiotestsrc ! video/x-raw ! ximagesink
WARNING: could not link audiotestsrc0 to ximagesink0, audiotestsrc0 can't
handle caps video/x-raw

$ gst-launch-1.0 audiotestsrc ! audio/x-raw,format=S16 ! fakesink
WARNING: could not link audiotestsrc0 to fakesink0, audiotestsrc0 can't handle
caps audio/x-raw, format=(string)S16


We might still/also want a more general
try_and_figure_out_why_two_elements_cant_link() function, so we can have a more
useful debug message in our debug logs when linking fails outside of parse
launch.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.