libstagefright - Experimental hardware video decoding builds
(2013-02-22, 08:46)Herman.Chen Wrote: Hi all, I am libstagefright developer from rockchip. I am Chen Hengming mail: [email protected]

The rockchip OMX component output buffer normally is MOD16. That is correct. We do not use the published width/height of a stream.

But due to RK3066's GPU hardware limit, the RK3066 OMX component output buffer is 32 bytes align on width and 16 bytes align on height.
So sorry for inconvenience.
Please set output buffer to MOD32 and test whether it is fixed.

BTW the OMX component use memcpy to transmit picture which is not efficient. In Rockchip libstagefright we use zero copy from decoder to render which introduce some private interface which make it difficult to use libstagefright from native layer.

If you need more infomation about that feel free to contact me.
Hi Herman,

Thanks for joining the thread.

We are passing a native windows to OMXCodec::Create, so rendering is done entirely inside libstagefright and we don't have any way to correct the frame size.

Related to this, it looks like the frame size passed in the metadata after a read is not correct, I. E. Is not mod16/mod32 but the published one.

Could it be that solving the metadata bug would also solve the rendering bug?

Messages In This Thread
Re: RE: libstagefright - Experimental hardware video decoding builds - by Koying - 2013-02-23, 05:43
libstagefright - by mo123 - 2013-05-14, 14:29
RE: libstagefright - by Koying - 2013-05-14, 14:30
RE: libstagefright - by Maverick5269 - 2013-05-16, 23:04
RE: libstagefright - by matander - 2013-05-19, 18:26
RE: libstagefright - by FreeFrag - 2013-05-22, 13:02

Logout Mark Read Team Forum Stats Members Help
libstagefright - Experimental hardware video decoding builds10
This forum uses Lukasz Tkacz MyBB addons.