I'm working on DM816x EVM and using EZSDK 5.05.01.04.
I want to use H.264 encoder not by OMX but by Codec Engine.
In document "component-sources/omx_05_02_00_30/src/ti/omx/docs/H264_Encoder_HDVICP2_UserGuide.pdf",H.264 encoder is implemented based on XDAIS/XDM.
Definitions related XDM (VIDENC2) can be found in "component-sources/omx_05_02_00_30/src/ti/omx/interfaces/openMaxv11/ih264enc.h".
But I cannot find released packages (ti.sdo.codecs.h264enc, ti.sdo.codecs.h264enc.ce) related to this codec.
In the prebuilt HDVICP2 firmware binary, I can find strings like "CERuntime_Init", "Engine_open", "VIDENC2_process", ...So I guess that the distributed HDVICP2 firmware is accessed by Codec Engine.
Can I make Codec Engine in my application without packages like ti.sdo.codecs.h264enc, ti.sdo.codecs.h264enc.ce?
Some of my config is like below.
var osalGlobal = xdc.useModule('ti.sdo.ce.osal.Global');osalGlobal.runtimeEnv = osalGlobal.DSPLINK_LINUX;var Engine = xdc.useModule('ti.sdo.ce.Engine');xdc.useModule('ti.sdo.ce.video2.IVIDENC2');
And during initialzation, try to open Engine like this way.
.. engErr = Engine_addStubFxns("VIDENC2_STUBS", (IALG_Fxns*)&VIDENC2_STUBS); Engine_initDesc(&engDesc); engDesc.name = ENGINENAME; engDesc.memMap = NULL; engDesc.useExtLoader = FALSE; engDesc.remoteName = "dm816x_hdvicp.xem3"; engErr = Engine_add(&engDesc); Engine_initAttrs(&engAttrs); engAttrs.procId = "VIDEO-M3"; hCE = Engine_open(ENGINENAME, &engAttrs, &engErr);...
The function Engine_open() returns NULL with error code 3 (EDSPLOAD).
No memory map is changed, and the firmware and application is in the same directory.
1. Can I get the H.264 Encoder packages (with or without source)?
2. Modules in the prebuilt firmware can be accessed by Codec Engine?
3. If possible, how the configuration and code should be changed?
HDVICP2 firmware/M3 multimedia is given as a binary only. You need to use the OMX APIs on the host processor to use it. Direct use of codec engine is not possible. What is the reason for using CE directly rather than the OMX interface which is given to you ?
In reply to Yashwant Dutt:
I want use the "Region of Interest Encoding" feature of H.264 Encoder 2.0.
I can set the "enableROI" field of IH264ENC_DynamicParams to 1 by OMX API OMX_SetParameter() in the initialzation stage.But I cannot find the way how to set fileds of IH264ENC_RoiInput of IH264ENC_InArgs by OMX API.
I thought that the IH264ENC_InArgs can be accessed by codec engine, since it is defined as a extension of IVIDENC2_InArgs.
How can I pass the IH264ENC_RoiInput to HDVICP2 using OMX?
In reply to Juho Ha:
ROI feature is not integrated in SDK, you may not be able to use it..
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.