Hello,<br>I had taken a look at the gstreamer-ti plugins some time back. One of the things that i noticed is threads being spawned from within the decoder plugins, which does not fit well with me. I also noticed quite a lot of bugs in the code, which kept me from using it or hacking on it. Besides i already have most of the functionality implemented and just need to tweak my code/design a bit, hence the mail.<br>
<br>Thanks and Regards<br>~Sameer<br><br><div class="gmail_quote">On Sun, Nov 22, 2009 at 9:27 PM, Brijesh Singh <span dir="ltr"><<a href="mailto:brijesh.ksingh@gmail.com">brijesh.ksingh@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br>
<br>
Have you looked at <a href="http://gstreamer.ti.com" target="_blank">gstreamer.ti.com</a> ? gst_ti has all the elements you<br>
need. It support wide varity of TI platforms. (DM6446, DM355, DM365,<br>
DM357, DM6467, OMAP3530 and more...).<br>
<br>
To understand design detail you can watch 25-min of video presentation.<br>
<br>
<a href="https://gstreamer.ti.com/gf/project/gstreamer_ti/wiki/?pagename=OverviewPresentation" target="_blank">https://gstreamer.ti.com/gf/project/gstreamer_ti/wiki/?pagename=OverviewPresentation</a><br>
<br>
We do not have pad-allocation method yet (may be you can contribute on<br>
project). We use hw accelerated framecopy to copy the data from video<br>
decoder -> sink element. Depending on the platform, this hw<br>
accelerator may be resizer/dma/vdce/sdma etc...<br>
<br>
<br>
Thanks<br>
Brijesh<br>
<div><div></div><div class="h5"><br>
On Sun, Nov 22, 2009 at 4:18 AM, Sameer Naik<br>
<<a href="mailto:sameer.subscriptions@damagehead.com">sameer.subscriptions@damagehead.com</a>> wrote:<br>
> Hi,<br>
> I am developing a multimedia application for an embedded system based on<br>
> TI's DM6446 platform. The decoding of the audio and video frames will be<br>
> done using the HW decoders. The platform also includes a hardware resizer,<br>
> that allows resizing of the video frames in hardware, thereby making the<br>
> resizing operations pretty quick.<br>
><br>
> I need some advice on the architecture that i should base by application on.<br>
> Following are the architectures that i have come up with<br>
><br>
> 1.<br>
> - audio decoder plugins<br>
> - video decoder plugins<br>
> - resizer plugin<br>
> - frame buffer output plugin<br>
> Here i can build a seperate plugin to do the resizing of video frames. This<br>
> would conform more with gstreamer's idea that "every element does one<br>
> thing", providing better reusability. To reduce to number of memcpy's, i<br>
> could equip the frame buffer plugin with pad allocation capabilities and<br>
> accordingly add pad_alloc calls in the resizer plugin. The only this is, in<br>
> this case the frames will always be resized, regardless of whether the frame<br>
> is going to be displayed or dropped. I am not really sure whether this is<br>
> that big of a problem considering that the number of frames that could be<br>
> dropped is very less.<br>
><br>
> 2.<br>
> - audio decoder plugins<br>
> - video decoder plugins<br>
> - frame buffer plugin with resizing capabilities using the hw resizer.<br>
> Here i can build the frame buffer plugin with the built in capability to<br>
> resize video frames. In this case i could resize the frame only if it is<br>
> going to be displayed (i.e. just before it would be displayed on screen).<br>
> Now in this case i loose the reusability advantage, which i can live with if<br>
> i am able to achieve smooth video playback with av sync. In this case, I am<br>
> not sure whether the last minute resizing of the frame would introduce a lot<br>
> of latency while displaying the frame. Given that it is a hardware resizer i<br>
> am assuming it would be quick.<br>
><br>
> P.S. I would be employing the pad allocation method in other parts of the<br>
> pipeline as well, so as to reduce the number of memcpy's going on in the<br>
> pipeline.<br>
><br>
> Please Advice.<br>
><br>
> Regards<br>
> ~Sameer<br>
><br>
><br>
</div></div>> ------------------------------------------------------------------------------<br>
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day<br>
> trial. Simplify your report design, integration and deployment - and focus<br>
> on<br>
> what you do best, core application coding. Discover what's new with<br>
> Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_blank">http://p.sf.net/sfu/bobj-july</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>
><br>
><br>
<br>
<br>
<br>
--<br>
Confusion is always the most honest response.<br>
<br>
------------------------------------------------------------------------------<br>
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day<br>
trial. Simplify your report design, integration and deployment - and focus on<br>
what you do best, core application coding. Discover what's new with<br>
Crystal Reports now. <a href="http://p.sf.net/sfu/bobj-july" target="_blank">http://p.sf.net/sfu/bobj-july</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>