GNOME Bugzilla – Bug 544003
[parse] Links to wrong pad if no padtemplate name is given
Last modified: 2008-12-09 16:12:04 UTC
Steps To Reproduce: gst-launch-0.10 videotestsrc ! video/x-raw-yuv, width=720, height=576,format=(fourcc)I420 ! videoscale ! video/x-raw-yuv, width=400, height=300 ! textoverlay text="hello" ! fakesink Actual Results: WARNING: erroneous pipeline: could not link videoscale0 to textoverlay0 Expected Results: Link ok. Additional Information: <__tim> cap: it tries to link to textoverlay's text sink pad and when that fails it doesn't try the video pad __tim> cap: sth like this should work though: gst-launch-0.10 videotestsrc ! video/x-raw-yuv, width=720, height=576,format=\(fourcc\)I420 ! videoscale ! video/x-raw-yuv, width=400, height=300 ! overlay.video_sink textoverlay name=overlay text="hello" ! fakesink
Ok so the problem is more, that gst_parse_launch and friends take a pad template at random if no name is given, try to link and explode if it fails. Instead it should try all possible pad templates until one works.
Hi, Note that gst_element_link_filtered (videoscale, textoverlay, caps) failed. And gst_element_link_pads_filtered(videoscale, "src", textoverlay, "video_sink", caps) works. J.
gst-launch is only a debug tool, closing. Please reopen if a patch is supplied.
? It comes from code too (comment #2)
ah, infamous gstutils functions that try to be too clever...
*** Bug 563728 has been marked as a duplicate of this bug. ***
Switching this bug over to 'enhancement'. While gst-launch is only a debug tool I think that expecting consistent behaviour of our muxers and demuxers when used through it is not to much to ask and different from asking for further features from gst-launch.
2008-12-09 Sebastian Dröge <sebastian.droege@collabora.co.uk> * gst/gstutils.c: (gst_element_get_compatible_pad): Check if the caps of the pads are compatible before returning a pad and claiming it is compatible. This, among other things, fixes a bug with gst-launch where an incompatible pad is chosen and linking fails. Fixes bug #544003.
FYI Bug 563728 is actually no duplicate of this bug