Thank you Tim. That helped my find my next error and get much further! :-) I am still trying to really understand the details of how all of this comes together. One piece at a time! Chuck <div class="gmail_quote"> On Tue, Feb 5, 2013 at 4:25 PM, Tim-Philipp Müller <<a href="mailto:t.i.m@zen.co.uk" target="_blank">t.i.m@zen.co.uk</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On Tue, 2013-02-05 at 16:15 -0500, Chuck Crisler wrote: Hi, <div class="im"> > I am working to extend the v4l2src element to work with a Sensoray > hardware encoder. I now have the v4l2src element recognizing the H264 > capability of the card. The next problem is negotiating between the > v4l2src and rtph264pay or mpegtsmux (sorry, I am stuck with the > antiquated 0.10.xx code - which actually works quite well). If I > specify the command as: gst-launch v4l2src </div>This: > .. ! 'video/x-raw-yuv, format=(fourcc)H264' ! ... does not make sense. Either it's raw or it's H264. v4l2src should output video/x-h264 caps. If it doesn't, rtph264pay or h264parse etc. will not be able to accept it. FWIW, there's an uvch264src element in gst-plugins-bad in git in the 0.10 branch, which *might* help (I don't know if it does, I guess it depends on the driver). Cheers -Tim <div class="im"> > rtph264pay pt=96 ! ... it fails linking the v4l2src (actually the > capsfilter src pad) and rtph264pay. I think that this is a caps issue. > The rtp payloader wants video/x-h264 as input. How do I specify the > caps to make all of the elements link? </div>_______________________________________________ gstreamer-devel mailing list <a href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel" target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a> </blockquote></div>