How can I config the H264 encode codecParams.cfg for HPENC in transcode project?

Hi could you please let me know which transcoder project in mcsdk_video are you trying? CCS example?

thank you,

Paula

hi Paula,

I am sorry I am late for reply. I use the C:\ti\mcsdk_video_2_1_0_8\examples\transcode  project, project name is videoTranscode ,  which is imported from ccs. Yes, it 's ccs example.

Regards,

Si

Hi Si, please use latest MCSDK video release CCS transcoder example which includes H264HP encoder

http://software-dl.ti.com/sdoemb/sdoemb_public_sw/mcsdk_video/02_02_00_42/index_FDS.html

alternatevely you can change used encoder

videoTranscode->properties -> C6000 Compiler -> include Options -->  "${CODEC_ROOT}/C66x_h264hpvenc_01_00_02_00_ELF/packages"

You would need to download/install H264 HP encoder from http://software-dl.ti.com/dsps/dsps_public_sw/codecs/C6678/index.html

Finally, save changeds, clean project and  build project

Thank you,

Paula

hi Paula,

The  MCSDK video link "http://software-dl.ti.com/sdoemb/sdoemb_public_sw/mcsdk_video/02_02_00_42/index_FDS.html" is a post production release for the MCSDK 3.1.0 release, but my mcsdk version is mcsdk_2_01_02_06, so I will try the other way you said, and i have some questions.

Q1: you said change incude options path as "${CODEC_ROOT}/C66x_h264hpvenc_01_00_02_00_ELF/packages",

 and I think I have to also change the “C6000 Linker -> File Searc Path ” to link h264hpvenc_ti.le66 lib,not  h264venc_ti.le66 lib, is it right?

Q2:"C:\ti\Codecs\C66x_h264hpvenc_01_00_00_01_ELF\packages\ti\sdo\codecs\h264hpvenc\App\Client\Test\TestVecs\Config"  encoder.cfg file,  there is a config

"Profile               = 100 # Encoding profile 100 => HP, 77 => MP, 66 => BP.  " , but for “C:\ti\mcsdk_video_2_1_0_8\examples\transcode\testVecs\config” codecParams.cfg, it 's default config is

"ch1_static_param11  = 66           # profileIdc“, it is BP encoder, so for transcode project ,after I change Q1 path, need I config the codecParams.cfg? If it 's, how?

Regards,

Si

hi Paula,

I download mcsdk_video/02_02_00_42 and find what you said"CCS transcoder example which includes H264HP encoder", then I build it, but there is some wrong, below is the error:

"../linker.cmd", line 164: error #10099-D: program will not fit into available memory. run placement with alignment fails for section ".shared_mem_SL2_uncached" size 0x1f008 . Available memory ranges:
MSMC size: 0x3fff00 unused: 0x1f638 max hole: 0xff00
error #10010: errors encountered during linking; "videoTranscode.out" not built

it likes that the MSMC memroy is almost full, there is not enough memory for shared_mem_SL2_uncached section. can you help me solve the problem?

Regards,

Si

Hi Si,

You are right, example CCS was not test it on drop42 and it is not fitting.. I will report the issue so it gets resolve on a next drop.

In Drop39 transcoder example CCS was checked (http://software-dl.ti.com/sdoemb/sdoemb_public_sw/mcsdk_video/02_02_00_39/index_FDS.html) so you can use this drop better.

This drop uses below codecs versions:

C66x_h264hpvdec_01_01_02_07_ELF
C66x_h264hpvenc_01_00_01_04_ELF

thank you,

Paula

Hi Paula,

I download the mcsdk_video_02_02_00_39, and build the transcode project, and I can build and run it successfully.

The project just uses one core  for transcoding, but I want to use core0~core1 decoder and then core2~core7

encoder for one channel, what should I do? If I want to achieve multi channels,  what should I do?

Regards,

Si

Hi Si, you can check MCSDK video PCIe demos for a multicore multichannel implementation of H.264

thank you,

Paula

Hi Paula,

PCIe demos has no source code , and  it 's not a ccs project, I want to have a ccs project base on a multicore multichannel implementation of H.264, how can I achieve it?

Regards,

Si

Hi Si, TFTP framework demos can be configured in multicore

C:\TI\mcsdk_video_2_2_0_39\dsp\siu\vct\testVecs

please check H.264HP encoder/decoder

In codec params you can set number of cores and core teams

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

nCores = 2 # Number of Cores involved in the decode/encode operation

coreTeamMapping = 0 1 -1 # Core IDs (0-based) involved in the

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

thank you,

Paula

Paula,

Yes,I find it,  but it 's not a ccs project, I need a ccs project example which can run encode and decode on different core,and the demo can not run transcode on different cores of one chip, just encode or decode.

So what I want to achieve is  a ccs project which includes source code, and also which can run  multicore transcode.

Can you help me to achieve it?

Best Regards,

Si

Hi Paula,

when I use the C66x_h264hpvenc_01_00_02_00_ELF and C66x_h264hpvdec_01_01_02_07_ELF project,in  the codecParams.cfg  file ,  I want to run encode fron core1 to core7, because core0 will run other program. I modify the config, is it right?

codecName = H264HPENC     # Name of the codec (must be listed in siuVctsupportedCodecs.c)
nCores = 7       # Number of Cores involved in the decode/encode operation
coreTeamMapping =  1 2 3 4 5 6 7 -1 # Core IDs (0-based) involved in the decode/encode operation

Regards,

Si

Hi Si, yes your changes in the configuration file are OK. Addicionally you need to change ownerProcID from "0" to "1" inside h264hpvenc.cfg:

SharedRegion.setEntryMeta(0,

    { base: Program.global.shmSL2Base,

      len: Program.global.shmSL2Size,

      ownerProcId: 1,

      isValid: true,

      cacheEnable: true,    

      cacheLineSize: 64,

      name: "ipc_internal_shared_mem",

    });

Thank you,

Paula

hi Paula,

I have a try following you said, I load the .out file to core1~core7,it can run because   ipcAttachOwner(ncores),  So I load the out file to core0~core7, it can run over the    ipcAttachOwner(ncores),but also faild to encode, here is the output info:

[C66xx_1] ---------------------------------------------------------
[C66xx_2] ---------------------------------------------------------
[C66xx_3] ---------------------------------------------------------
[C66xx_4] ---------------------------------------------------------
[C66xx_5] ---------------------------------------------------------
[C66xx_7] ---------------------------------------------------------
[C66xx_1] Test Case Number : 1
[C66xx_2] Test Case Number : 1
[C66xx_3] Test Case Number : 1
[C66xx_4] Test Case Number : 1
[C66xx_5] Test Case Number : 1
[C66xx_7] Test Case Number : 1
[C66xx_1] ---------------------------------------------------------
[C66xx_2] ---------------------------------------------------------
[C66xx_3] ---------------------------------------------------------
[C66xx_4] ---------------------------------------------------------
[C66xx_5] ---------------------------------------------------------
[C66xx_7] ---------------------------------------------------------
[C66xx_6]
---------------------------------------------------------
Test Case Number : 1
---------------------------------------------------------
[C66xx_0]
[C66xx_1]
[C66xx_2]
[C66xx_3]
[C66xx_4]
[C66xx_5]
[C66xx_7]
[C66xx_0] ---------------------------------------------------------
[C66xx_1] ---------------------------------------------------------
[C66xx_2] ---------------------------------------------------------
[C66xx_3] ---------------------------------------------------------
[C66xx_4] ---------------------------------------------------------
[C66xx_5] ---------------------------------------------------------
[C66xx_7] ---------------------------------------------------------
[C66xx_0] Test Case Number : 1
[C66xx_1] Test Case Number : 1
[C66xx_2] Test Case Number : 1
[C66xx_3] Test Case Number : 1
[C66xx_4] Test Case Number : 1
[C66xx_5] Test Case Number : 1
[C66xx_7] Test Case Number : 1
[C66xx_0] ---------------------------------------------------------
[C66xx_1] ---------------------------------------------------------
[C66xx_2] ---------------------------------------------------------
[C66xx_3] ---------------------------------------------------------
[C66xx_4] ---------------------------------------------------------
[C66xx_5] ---------------------------------------------------------
[C66xx_7] ---------------------------------------------------------
[C66xx_0] ShmemTab initialized on Core 0
[C66xx_2] ShmemTab initialized on Core 2
[C66xx_4] ShmemTab initialized on Core 4
[C66xx_3] ShmemTab initialized on Core 3
[C66xx_1] Config File : ..\..\..\Test\TestVecs\Config\encoder.cfg
[C66xx_5] ShmemTab initialized on Core 5
[C66xx_1] Input YUV : ..\..\..\Test\TestVecs\Input\airshow_p352x288.yuv
Output Stream : ..\..\..\Test\TestVecs\Output\airshow_p352x288.264

[C66xx_6] ShmemTab initialized on Core 6
[C66xx_1] ShmemTab initialized on Core 1

Algorithm Instance Creation for the Module DEV.H264HP.E.C6678.01.00.01.04 Done...
[C66xx_0]
[C66xx_2]
[C66xx_3]
[C66xx_4]
[C66xx_5]
[C66xx_6]
[C66xx_0] Algorithm Instance Creation for the Module DEV.H264HP.E.C6678.01.00.01.04 Done...
[C66xx_2] Algorithm Instance Creation for the Module DEV.H264HP.E.C6678.01.00.01.04 Done...
[C66xx_3] Algorithm Instance Creation for the Module DEV.H264HP.E.C6678.01.00.01.04 Done...
[C66xx_4] Algorithm Instance Creation for the Module DEV.H264HP.E.C6678.01.00.01.04 Done...
[C66xx_5] Algorithm Instance Creation for the Module DEV.H264HP.E.C6678.01.00.01.04 Done...
[C66xx_6] Algorithm Instance Creation for the Module DEV.H264HP.E.C6678.01.00.01.04 Done...
[C66xx_0]
Control Failed.
Failed in control call (XDM_SETPARAMS).
[C66xx_1]

******** Request to END H264 Encoder ********
[C66xx_0]
[C66xx_2]
[C66xx_3]
[C66xx_4]
[C66xx_5]
[C66xx_6]
[C66xx_0]
[C66xx_2]
[C66xx_3]
[C66xx_4]
[C66xx_5]
[C66xx_6]
[C66xx_0]
[C66xx_2]
[C66xx_3]
[C66xx_4]
[C66xx_5]
[C66xx_6]
[C66xx_0] ******** Request to END H264 Encoder ********
[C66xx_2] ******** Request to END H264 Encoder ********
[C66xx_3] ******** Request to END H264 Encoder ********
[C66xx_4] ******** Request to END H264 Encoder ********
[C66xx_5] ******** Request to END H264 Encoder ********
[C66xx_6] ******** Request to END H264 Encoder ********

I want to use 7 core to encode, so core1~core7 load encode out file, and core0 will run management out file, Can you help me to achieve it?

Regards,

Si

Hi Paula,

Thank you very much, I can run it well.

Si