<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi Craig<br>
      <br>
      You'll need to specify the full set caps from the payloader, just
      the mimetype isn't enough. For example:<br>
      <br>
      <pre>gst-launch videotestsrc ! x264enc ! rtph264pay ! udpsink port=5000 -v

...
</pre>
      <pre>/GstPipeline:pipeline0/GstRtpH264Pay:rtph264pay0: seqnum = 33460</pre>
      <pre>/GstPipeline:pipeline0/GstUDPSink:udpsink0.GstPad:sink: caps = application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264, 
sprop-parameter-sets=(string)\"Z01AFeygoP2AiAAAAwALuaygAHixbLA\\=\\,aOvssg\\=\\=\", payload=(int)96, ssrc=(uint)2406338994, clock-base=(uint)156724985, seqnum-base=(uint)33460

...

</pre>
      The -v printed out the caps. <br>
      <br>
      I can successfully receive it by running:<br>
      <br>
      <pre>gst-launch udpsrc port=5000 ! "application/x-rtp, media=(string)video, clock-rate=(int)90000, encoding-name=(string)H264, 
sprop-parameter-sets=(string)\"Z01AFeygoP2AiAAAAwALuaygAHixbLA\\=\\,aOvssg\\=\\=\", payload=(int)96, ssrc=(uint)2406338994, 
clock-base=(uint)156724985, seqnum-base=(uint)33460" ! rtph264depay ! ffdec_h264 ! fpsdisplaysink sync=false</pre>
      And yes, this means that the receiver pipeline is fixed to the
      sender pipeline's resolution and characteristics. Changing
      something on the sender will require a new pipeline on the
      receiver. If this is a problem for you, you might want to try
      using mpegtsmux or a smarter protocol like RTSP.<br>
      <br>
      Michael<br>
      <br>
      <br>
      On 04/15/2014 01:36 PM, Chuck Crisler wrote:<br>
    </div>
    <blockquote
cite="mid:CALXOHKoGnB1xBKeva2SKLYN88DnttOcQoJJRt9H3MdLBeO90Vw@mail.gmail.com"
      type="cite">
      <div dir="ltr">To start debugging...simplify. Take out the jitter
        buffer. Specify the host in addition to the port for both
        pipelines. It might force IPv4 vs. IPv6 (there have been
        issues). Set higher logging levels and/or get a packet capture
        to see if the problem(s) is in the transmit or receive.<br>
      </div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Tue, Apr 15, 2014 at 3:19 PM, Craig
          Routledge <span dir="ltr"><<a moz-do-not-send="true"
              href="mailto:web@craigroutledge.com" target="_blank">web@craigroutledge.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello
            everyone,<br>
            <br>
            I'd like to send a video stream created by a Logitech HD
            ProWebcam C920<br>
            to another computer.  The camera generates its own H264
            stream.  There<br>
            have been similar posts on the mailing list before, but I
            couldn't find<br>
            anything that seemed to work.<br>
            <br>
            I started by testing gstreamer's ability to parse and
            display the stream.<br>
            <br>
              gst-launch-1.0 v4l2src ! video/x-h264,width=640,height=480,framerate=30/1<br>
                ! h264parse ! avdec_h264 ! xvimagesink sync=false<br>
            <br>
            which works fine.<br>
            <br>
            <br>
            I then tried to stream over a network using RTP, sending and
            receiving on<br>
            the same computer,<br>
            <br>
              gst-launch-1.0 v4l2src ! video/x-h264,width=640,height=480,framerate=30/1<br>
                ! rtph264pay ! udpsink port=8554<br>
            <br>
            and, in another terminal window,<br>
            <br>
              gst-launch-1.0 udpsrc port=8554 ! application/x-rtp !
            rtpjitterbuffer<br>
                ! rtph264depay ! h264parse ! avdec_h264 ! xvimagesink
            sync=false<br>
            <br>
            This doesn't generate any errors, but doesn't display
            anything either.<br>
            Here is the standard output for both commands,<br>
            <br>
                Setting pipeline to PAUSED ...<br>
                Pipeline is live and does not need PREROLL ...<br>
                Setting pipeline to PLAYING ...<br>
                New clock: GstSystemClock<br>
            <br>
            So, what am I doing wrong?<br>
            _______________________________________________<br>
            gstreamer-devel mailing list<br>
            <a moz-do-not-send="true"
              href="mailto:gstreamer-devel@lists.freedesktop.org"
              target="_blank">gstreamer-devel@lists.freedesktop.org</a><br>
            <a moz-do-not-send="true"
              href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel"
              target="_blank">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
gstreamer-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gstreamer-devel@lists.freedesktop.org">gstreamer-devel@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel">http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>