<div style="font-family:garamond,new york,times,serif;font-size:12pt"><div style="font-family: garamond,new york,times,serif; font-size: 12pt;">Thanks Marco. I think you were very clear on the previous mail too but I dint understand you well. <br><br>The problem is: The h264 file that I am using is not encoded by one of the gstreamer elements. I encode the yuv file using another encoder which I want to evaluate. Then, I stream the file with gstreamer using the pipe from my post, receive it over udpsrc and want to store it in the x-264 format in a .264 file without any multiplexing (raw h264 stream) so I can decode and process it later. I have an h264 stream from the h264 reference encoder so it must be h264 compatible. I have made sure it does have SEI messages in it. However, it doesnt have SPS/PPS messages since it needs to be compatible with the baseline profile of h264.
I thought (from your earlier mail) that setting the property "config-interval" should solve my problem but it hasnt. Obviously! Since I HAVE no SPS/PPS in my stream. <br><br>Also, I need a raw .264 file at the output to evaluate and decode using another decoder element, not part of gstreamer. That's why I dont care about muxing it into a file format like mp4 and avi. Yet, I tried that. I see that there is no muxer for h264 files (ffmux_ipod also tries to mux the stream as an mpegts stream if I am right). Still, I tried using avimux/mp4mux to mux the stream into avi/mp4 container. I get this error:<br><br>ERROR: from element /GstPipeline:pipeline0/GstUDPSrc:udpsrc0: Internal data flow error.<br>Additional debug info:<br>gstbasesrc.c(2543): gst_base_src_loop (): /GstPipeline:pipeline0/GstUDPSrc:udpsrc0:<br>streaming task paused, reason not-negotiated (-4)<br>Execution ended after 3772400353 ns.<br><br>I think this is because the incoming stream from
udpsrc does not have mp4 hint information or other SPS/PPS information it is supposed to have. Of that, I cant seem to find a solution.<br><br>I think the crux of my problem is that I am using an external encoder. That is why 'h264parse' gives me no "codec-data" field in caps as expected from the sender side. Only this:<br><br>/GstPipeline:pipeline0/GstH264Parse:h264parse0.GstPad:src: caps = video/x-h264, stream-format=(string)byte-stream<br><br>As a result, I dont have a suitable value to set in the "codec-data" field in the receiver capsfilter I put between depayloader and filesink. You think I understand it right? There is something that can be done to solve this?<br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Marco Ballesio [via GStreamer-devel] <<a href="/user/SendEmail.jtp?type=node&node=2252445&i=0" target="_top" rel="nofollow">[hidden email]</a>><br><b><span
style="font-weight: bold;">To:</span></b> Farah <<a href="/user/SendEmail.jtp?type=node&node=2252445&i=1" target="_top" rel="nofollow">[hidden email]</a>><br><b><span style="font-weight: bold;">Sent:</span></b> Sat, June 12, 2010 1:00:28 AM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: Using gstreamer to transmit H264 file over RTP<br></font><br>
Hi,
<br><br>as I pointed out in the previous mail (I'm sorry if I've not been
<br>clear enough) you need to explicitly set the codec_data parameter in
<br>the receiving side caps.
<br><br>I also suggest you to mux the depayloaded h264 (even if you're using
<br>annex B it's not a container format, only a codec). The easiest way is
<br>to put the muxer between the h264 depayloader and the filesink.
<br><br>Regards
<br><br>On Sun, Jun 6, 2010 at 6:56 AM, Farah <<a rel="nofollow" target="_top" link="external">[hidden email]</a>> wrote:
<div class="shrinkable-quote"><div class='shrinkable-quote'><br>>
<br>>
<br>> Another update, just so you know!
<br>>
<br>> I even updated my system to the latest gstreamer releases 0.10.29 from this
<br>> ppa:
<br>>
<br>> <a rel="nofollow" target="_blank" href="https://launchpad.net/%7Egstreamer-developers/+archive/ppa" link="external">https://launchpad.net/~gstreamer-developers/+archive/ppa</a><br>>
<br>> That hasnt changed the situation much and that worries me more. This means
<br>> that it may not actually be a gstreamer bug. Please help!
<br>>
<br>> Thanks.
<br>>
<br>> Farah Akhtar.
<br>> --
</div><span>> View this message in context: <a target="_blank" href="http://gstreamer-devel.966125.n4.nabble.com/Using-gstreamer-to-transmit-H264-file-over-RTP-tp2236364p2244738.html?by-user=t&by-user=t" rel="nofollow" link="external">http://gstreamer-devel.966125.n4.nabble.com/Using-gstreamer-to-transmit-H264-file-over-RTP-tp2236364p2244738.html?by-user=t</a></span><br>> Sent from the GStreamer-devel mailing list archive at <a target="_blank" href="http://Nabble.com?by-user=t" rel="nofollow" link="external">Nabble.com</a>.
<br>>
<br>> ------------------------------------------------------------------------------
<br>> ThinkGeek and WIRED's GeekDad team up for the Ultimate
<br>> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
<br>> lucky parental unit. See the prize list and enter to win:
<br><span>> <a target="_blank" href="http://p.sf.net/sfu/thinkgeek-promo" rel="nofollow" link="external">http://p.sf.net/sfu/thinkgeek-promo</a></span><br>> _______________________________________________
<br>> gstreamer-devel mailing list
<br>> <a rel="nofollow" target="_top" link="external">[hidden email]</a>
<br>> <a rel="nofollow" target="_blank" href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" link="external">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a><br>>
</div><br>------------------------------------------------------------------------------
<br>ThinkGeek and WIRED's GeekDad team up for the Ultimate
<br>GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
<br>lucky parental unit. See the prize list and enter to win:
<br><a rel="nofollow" target="_blank" href="http://p.sf.net/sfu/thinkgeek-promo" link="external">http://p.sf.net/sfu/thinkgeek-promo</a><br>_______________________________________________
<br>gstreamer-devel mailing list
<br><a rel="nofollow" target="_top" link="external">[hidden email]</a>
<br><a rel="nofollow" target="_blank" href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" link="external">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a><br>
<br><br>
<hr color="#cccccc" noshade="noshade" size="1">
<div style="color: rgb(102, 102, 102); font: 11px tahoma,geneva,helvetica,arial,sans-serif;"><span>
View message @ <a target="_blank" href="http://gstreamer-devel.966125.n4.nabble.com/Using-gstreamer-to-transmit-H264-file-over-RTP-tp2236364p2252222.html?by-user=t" rel="nofollow" link="external">http://gstreamer-devel.966125.n4.nabble.com/Using-gstreamer-to-transmit-H264-file-over-RTP-tp2236364p2252222.html</a>
</span><br>To unsubscribe from Re: Using gstreamer to transmit H264 file over RTP, <a rel="nofollow" target="_blank" link="external">click here</a>.
</div>
<br>
</div></div>
</div><br>
<br><hr align="left" width="300">
View this message in context: <a href="http://gstreamer-devel.966125.n4.nabble.com/Using-gstreamer-to-transmit-H264-file-over-RTP-tp2236364p2252445.html">Re: Using gstreamer to transmit H264 file over RTP</a><br>
Sent from the <a href="http://gstreamer-devel.966125.n4.nabble.com/">GStreamer-devel mailing list archive</a> at Nabble.com.<br>