Re: [Gstreamer-openmax] Gstreamer Pipeline Optimisations ?

[Nitin P. <nit...@gm...>]

Hi Rob,

I see that there are variables like share_input_buffer,share_output_buffer
which avoid copying within the gst-openmax wrapper.

My question was for the entire gstreamer stack. Considering an application
that uses Phonon over Gstreamer (over may be openmax). Are there any
optimizations possbile there?
Running QT over Phonon, Gstreamer on Embedded devices can kill the cpu for
D1 resolutions.


Thanks,
Nitin

On Fri, Apr 9, 2010 at 1:29 PM, Rob Clark <ro...@ti...> wrote:

> On 04/09/2010 01:52 AM, Nitin PAI wrote:
>
>>
>> Hi,
>>
>> Currently, a typical gstreamer pipeline looks like
>>
>> >gst-launch  filesrc location=XYZ ! demuxer !  decodebin !
>> ffmpegcolorspace ! videobalance ! videoscale ! ximagesink.
>>
>> The movement of data accross is enormous for a D1 or HD resolution as the
>> pipeline passes YUV/RGB data which is very huge.
>>
>> Is there any optimization possible or used which uses *pointers* to pass
>> rather than the huge mem-copies involved?
>>
>
>
> Hi Nitin,
>
> search for share_buffer
>
> For this to work, it depends on your OpenMAX implementation to support
> 'non-pre-announced' buffers (which was a recent proposal from Nokia to
> Khronos standards group)
>
> BR,
> -R
>
>


-- 
“Karmanya vadhikaraste ma phaleshu kadachana Ma karma-phala-hetur bhu ma te
sango stav karmani”           -  Krishna