android h264 hardware encoding

[Ole Bromose]

On 10/12/2013 04:11 PM, Ole Bromose wrote:
> On 10/11/2013 05:46 PM, yoyosuper8 wrote:
>> The good thing is that we are only targeting one Android device and a
>> Pandaboard from TI.
>>
>> So, by applying the patch I'll be able to do hardware encoding and 
>> specify
>> the hardware available on my android device? If this is a faster and 
>> more
>> efficient method than OpenMax, then I'd rather go this way.
>>
>> Thanks
>> Andy
>
> Pandaboard is built around the OMAP4430 (or 4460) from Texas Instruments.
> Hardware acceleration is done by software (named Ducati) in one of the 
> two
> Cortex M3s in the OMAP SoC. Ducati is not open source, but you'll 
> probably
> not need the source for your purpose.
> However, you need to be sure that acceleration is enabled in Android. 
> This
> should be ok in case you are using Linaro's Android build for Pandaboard.
>
> Best regards
> Ole


I forgot to say that Ducati implements OpenMax IL 1.3 component, so I 
think this
is the way to go in case the patch mentioned by Sebastian doesn't work 
for you.

/Ole


>
>>
>>
>> -- 
>> View this message in context: 
>> http://gstreamer-devel.966125.n4.nabble.com/android-h264-hardware-encoding-tp4662522p4662547.html
>> Sent from the GStreamer-devel mailing list archive at Nabble.com.
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>
>
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>