Hi Mikko,<br><br><div class="gmail_quote">On Fri, Nov 19, 2010 at 10:33 AM, Mikko Hurskainen <span dir="ltr"><<a href="mailto:mikko.hurskainen@notava.com">mikko.hurskainen@notava.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> Hi,<br> <br> There seems to different behaviour with different parsers what comes to<br> the resolutions etc. E.g. for H.263 stream quicktime parser gives<br> resolution and rtph263depay gives only stream type.</blockquote><div><br>The h263 depayloader covers the functionalities as specified in rfc2190 (<a href="http://www.faqs.org/rfcs/rfc2190.html">http://www.faqs.org/rfcs/rfc2190.html</a>) which afaik are not requiring to extract information about the frame size. This information is usually extracted from the decoder itself or carried within the container format / signalling protocols.<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">My codec requires these settings.</blockquote><div><br>If you're using the decoder for an RTSP/VoIP session it's likely you got the codec-data (aka sprop-parameters-set) during the signalling phase. If you're getting them in-band you don't likely need a parser (and maybe you're dealing with an under-performing decoder). I'm not 100% sure h263 carries codec-data in band though :\ (note for me: read again ITU-T h263 specs).<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">So the question is, should the parsing functionality be<br> implemented by the codec or by parser in general ? Is there somewhere a<br> description what is expected from a codec ?<br></blockquote><div><br>Usually, the best place to process encoded data is within a decoder. Processing it twice (e.g. first into a parser, then into a decoder) is, at best, less efficient.<br> <br>My personal opinion is that wherever you need a parser for a decoder to work either you're working with a raw stream or with a broken decoder. In the first case, it's better if either you payloaded or multipex your data, in the second it's good if you get a better decoder ;).<br> <br>Regards<br> </div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <br> -- Mikko<br> <br> <br> ------------------------------------------------------------------------------<br> Beautiful is writing same markup. Internet Explorer 9 supports<br> standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.<br> Spend less time writing and rewriting code and more time creating great<br> experiences on the web. Be a part of the beta today<br> <a href="http://p.sf.net/sfu/msIE9-sfdev2dev" target="_blank">http://p.sf.net/sfu/msIE9-sfdev2dev</a><br> _______________________________________________<br> gstreamer-devel mailing list<br> <a href="mailto:gstreamer-devel@lists.sourceforge.net">gstreamer-devel@lists.sourceforge.net</a><br> <a href="https://lists.sourceforge.net/lists/listinfo/gstreamer-devel" target="_blank">https://lists.sourceforge.net/lists/listinfo/gstreamer-devel</a><br> </blockquote></div><br>