<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>i.MX Processors中的主题 UDP/RTP streaming orders of gstreamer decoder/encoder</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/UDP-RTP-streaming-orders-of-gstreamer-decoder-encoder/m-p/500270#M80863</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I read the tutorial of Yocto/Gstreamer&lt;/P&gt;&lt;P&gt;&lt;A href="http://trac.gateworks.com/wiki/Yocto/gstreamer/streaming#udp" title="http://trac.gateworks.com/wiki/Yocto/gstreamer/streaming#udp"&gt;Yocto/gstreamer/streaming – Gateworks&lt;/A&gt; &lt;/P&gt;&lt;P&gt;I saw that the example pipeline for UDP/RTP(raw) always start with decoder part first, then start encoder.&lt;/P&gt;&lt;P&gt;I wonder if there is any specific reason for this, can anybody help me to explain it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my practical test with iMX6DL board and streaming from camera, also I have the same result. If starting decoder from client side first, then start streaming from iMX6, I can see the video perfectly. In opposite case, it does not work though two streaming pipeline still is running, but I cannot see the decoded video displayed on Ubuntu client PC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 25 May 2016 08:03:09 GMT</pubDate>
    <dc:creator>tutran</dc:creator>
    <dc:date>2016-05-25T08:03:09Z</dc:date>
    <item>
      <title>UDP/RTP streaming orders of gstreamer decoder/encoder</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/UDP-RTP-streaming-orders-of-gstreamer-decoder-encoder/m-p/500270#M80863</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I read the tutorial of Yocto/Gstreamer&lt;/P&gt;&lt;P&gt;&lt;A href="http://trac.gateworks.com/wiki/Yocto/gstreamer/streaming#udp" title="http://trac.gateworks.com/wiki/Yocto/gstreamer/streaming#udp"&gt;Yocto/gstreamer/streaming – Gateworks&lt;/A&gt; &lt;/P&gt;&lt;P&gt;I saw that the example pipeline for UDP/RTP(raw) always start with decoder part first, then start encoder.&lt;/P&gt;&lt;P&gt;I wonder if there is any specific reason for this, can anybody help me to explain it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my practical test with iMX6DL board and streaming from camera, also I have the same result. If starting decoder from client side first, then start streaming from iMX6, I can see the video perfectly. In opposite case, it does not work though two streaming pipeline still is running, but I cannot see the decoded video displayed on Ubuntu client PC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 May 2016 08:03:09 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/UDP-RTP-streaming-orders-of-gstreamer-decoder-encoder/m-p/500270#M80863</guid>
      <dc:creator>tutran</dc:creator>
      <dc:date>2016-05-25T08:03:09Z</dc:date>
    </item>
    <item>
      <title>Re: UDP/RTP streaming orders of gstreamer decoder/encoder</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/UDP-RTP-streaming-orders-of-gstreamer-decoder-encoder/m-p/500271#M80864</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Of course, the receiving part should start first to wait for the incoming stream and then handle and decode the stream header correctly. In other case, the receiving part will not be able to synchronize with the stream.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Artur&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 30 May 2016 11:17:47 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/UDP-RTP-streaming-orders-of-gstreamer-decoder-encoder/m-p/500271#M80864</guid>
      <dc:creator>art</dc:creator>
      <dc:date>2016-05-30T11:17:47Z</dc:date>
    </item>
    <item>
      <title>Re: UDP/RTP streaming orders of gstreamer decoder/encoder</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/UDP-RTP-streaming-orders-of-gstreamer-decoder-encoder/m-p/500272#M80865</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Artur,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for your reply. I just ask because I saw some pipelines from gstreamer that guide us to start pipeline from server, then copy the caps properties to the client side. It also works&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jun 2016 11:50:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/UDP-RTP-streaming-orders-of-gstreamer-decoder-encoder/m-p/500272#M80865</guid>
      <dc:creator>tutran</dc:creator>
      <dc:date>2016-06-02T11:50:50Z</dc:date>
    </item>
  </channel>
</rss>

