* ======== Engine Configuration ========
var Engine = xdc.useModule('ti.sdo.ce.Engine');
var myEngine = Engine.create("audio_copy", [
{name: "auddec_copy", mod: AUDDEC_COPY, local: false},
{name: "audenc_copy", mod: AUDENC_COPY, local: false}
]);
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
I use the Omap3530 dvsdk,I think that the codec engine is almostly same.
when I use Engine.createformsever,I can specify the sever packages in parameter.
but when I use Engine.create,I can't find which configuration speak the path of the codec sever all.x64p .
You are strongly encouraged to use Engine.createFromServer(). While it is possible to create/configure an Engine with Engine.create(), you'll have to explicitly add memory map configuration, list all the codecs that go into the Engine, etc... and keep it all in sync with the Server.
For example, if you add a codec to the Server, you'll have to add it _also_ to your Engine config; if you change the memory map in your Server, you'll _also_ have to change the map in your Engine config. Instead, if you use Engine.createFromServer(), you just have to re-run the ARM-side config script if your Server changes - you won't have to modify the ARM-side script. Is there a reason you can't use Engine.createFromServer()?
Also, I think the path to the server (e.g. "./all.x64P") is relative to the location of your ARM-side application.
Chris