<div>Hi, I asked some time ago as I had difficulties finding h264parse element after a gstreamer upgrade.... Looking for h264parse element, I thought h264parse plugin was the right plugin. It provides legacyh264parse, which turned out not working in my pipeline. On a another installation, I discovered that h264parse element was part of videoparsers plugin. Using that element is OK, and it works correctly now. Having both a plugin and an element with the same name but not working the same way is confusing ... </div><blockquote style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex" class="gmail_quote">This pipeline was fine before upgrading. h264parse has been replaced by legacyh264, so was the pipeline. Any idea ? # gst-launch filesrc location=input.raw ! legacyh264parse ! video/x-h264, framerate=15/1 ! avimux ! filesink location=ouput.avi Setting pipeline to PAUSED ... Pipeline is PREROLLING ... ERROR: from element /GstPipeline:pipeline0/GstFileSrc:filesrc0: Internal data flow error. Additional debug info: gstbasesrc.c(2625): gst_base_src_loop (): /GstPipeline:pipeline0/GstFileSrc:filesrc0: streaming task paused, reason not-negotiated (-4) ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... Freeing pipeline ... </blockquote>