Does voxl-jpeg-turbo use any HW accelleration?
Ed Sutter last edited by
If yes great!
If not, are there any options that support hw acceleration for JPEG encoding?
@Ed-Sutter voxl-jpeg-turbo is just a wrapper for this code: https://github.com/libjpeg-turbo/libjpeg-turbo. So it is all SW. There is HW support for JPEG encoding on the device but we have not yet enabled it.
@Eric-Katzfey we would like to use HW support for jpeg encoding right away. Is there a way or a workaround to access it? Otherwise, we are running into overheating issues on the VOXL (both VOXL-Cam and FlightDeck).
@prasanth You should be able to use OpenMAX (OMX) for this but we have not yet tried it.
Dong Liu last edited by Dong Liu
@Eric-Katzfey Hi Eric. I tried use openMAX based on this code https://github.com/tjormola/rpi-openmax-demos/blob/master/rpi-encode-yuv.c
It compiled correctly. But which openMAX component to use? That code is for rPI, so the component is "OMX.broadcom.image_encode". I changed to "OMX.qcom.image_encode" but I got no such component error.
Could you tell me which omx component to use for the jpeg encoding?
@Dong-Liu We have not tried this yet so I don't know. But I would imagine you could locate it in a header file.
Dong Liu last edited by
@Eric-Katzfey I tried grep OMX.qcom from header files, could not find any.
But, string libOmxCore.so only displayed video and audio codec. There is no image codec.
voxl:/usr/include$ strings /usr/lib/libOmxCore.so |grep OMX.qcom