<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<br>
<div class="moz-cite-prefix">Le 2014-10-25 09:12, sithruk sana a
écrit :<br>
</div>
<blockquote
cite="mid:CA+oSK=ZGAtVfCscResFJbuicVyUv8_khyWtbgR+S8m+rY48VRg@mail.gmail.com"
type="cite">
<div><br>
</div>
<div>1) </div>
<div><br>
</div>
<div>I have used the below pipeline :</div>
<div>
<p class="">udpsrc port=5000 ! application/x-rtp,
clock-rate=90000, encoding-name=(string)H264, payload=96 !
rtph264depay ! vtdec ! autovideosink sync=true </p>
<p class=""><br>
</p>
<p class="">Building the pipeline for above is successful, but
received the below error .</p>
<p class=""><br>
</p>
<p class="">"Error received from element vtdec0: GStreamer
encountered a general resource error. </p>
<p class="">[ error_cb functions prints the above error log ]. <br>
</p>
</div>
</blockquote>
This error isn't very descriptive sadly. Are you aware you can get
more traces using GST_DEBUG environment ? (GST_DEBG=3 would be
warning level, GST_DEBUG="vtenc:6,3" should ebable vtenc trace at
level 6 and warning overall, and so on).<br>
<br>
My far guess (I have low confidence in that one though) would be
that h264 format might be a miss-match. This can be quickly checked
by trying ... ! rtph264depay ! h264parse ! vtdec ! ... <br>
<br>
<blockquote
cite="mid:CA+oSK=ZGAtVfCscResFJbuicVyUv8_khyWtbgR+S8m+rY48VRg@mail.gmail.com"
type="cite">
<div>
<p class=""><br>
</p>
<p class="">2) </p>
<p class=""><span class=""> </span><span class="">pipeline</span><span
class=""> = </span><span class="">gst_parse_launch</span><span
class="">(</span>"udpsrc port=5000 ! application/x-rtp,
clock-rate=90000, encoding-name=(string)H264, payload=96 !
rtph264depay ! decodebin! autovideosink sync=true "<span
class="">, &error);</span><br>
</p>
<p class="">Not, it is playing, but how can i confirm decodebin
uses Hardware decoder ?</p>
</div>
</blockquote>
You can most likely produce traces and inspect the traces. If using
gst-launch-1.0 method, you could add -v option, that would trace any
caps changes, hence as the side effect of showing elements being
used. You could also produce a dump (in graphviz) format of you
running pipeline at the point you reach paused of playing state. See
macro GST_DEBUG_BIN_TO_DOT_FILE().<br>
<br>
cheers,<br>
Nicolas<br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
</body>
</html>