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.

Is it possible to run 720P encoding on 216M DM365?

Hi, 

  I'm working on DM365 216MHZ platform. It can run an D1 encoding. but when I set the encoding size to 720P, it will failed with below error,

@0x063b40a8:[T:0x4001f080] ti.sdo.dmai - [Venc1] VIDENC1_process() ret -1 inId 0 outID 0 generated 2285188 bytes
@0x063b463e:[T:0x4001f080] ti.sdo.dmai - [Venc1] VIDENC1_process() failed with error (-1 ext: 0x800b)

  I knew the 216MHZ can only support D1 encoding, but  does it support 720P at 10fps or less framerate?

  • Hi

    Please migrate to latest version decoder(02.00.00.13) from TI site http://software-dl.ti.com/dsps/dsps_public_sw/codecs/DM36x/index_FDS.html It will resolve the issue.

    You can decode upto 1080p at lower fps.

    Thanks,

    Veeranna

  • Veeranna, 

      Thanks, but does the newest encoder support 720P encode at lower fps? 

  • YES latest version encoder / decoder  supports upto4kx4k resolution of encoding and 1080p of  decoding on DM365 of any board. In older version of codecs we have device check which limits encoding/decoding of higher resolution on DM365 216MHz board, later we removed this check.

  • Thanks. But I download the latest eoncder to my board, I got encoder error. 

    @0x0025c8bc:[T:0x4001f080] ti.sdo.dmai - [Venc1] Creating encoder h264enc for max 1280x720 bitrate 4194304 ratectrl 5

    @0x002e5d9a:[T:0x4001f080] ti.sdo.dmai - [Venc1] Failed to open video encode algorithm: h264enc (0x0)

    I did the upgrade with below steps, 

    1)download and unpack the dm365_h264enc_02_30_00_04_production

    2)copy the directory of 

    dm365_h264enc_02_30_00_04_production\packages\ti\sdo\codecs\h264enc  

    to 

    ~/dvsdk_3_10_00_19/dm365_codecs_03_10_00_07/packages/ti/sdo/codecs/

    3)make dmai_clean & make dmai

    4)make all

    Am I right to do the h264 encoder upgrade?

  • Hi,

    Previously which version you are using? There were some interface(static and dynamic param struct) changes

    Please refer below migration guides:

    http://processors.wiki.ti.com/index.php/H.264_DM36x_Ver_2.1_Codec

    http://processors.wiki.ti.com/index.php/Migration_Guide_for_DM36x_H.264_version_2.2_codecs

    http://processors.wiki.ti.com/index.php/Migration_Guide_for_DM36x_H.264_version_2.3_codecs

  • Hi ,

      Thanks! I also find this page,http://processors.wiki.ti.com/index.php/Migration/Integration_Guide_for_DM36x_H.264_version_2.x_codecs,

    and I'm working on it, I'll told you the result later.

      DVSDK 3.10.00.19

      h264enc 1.10.00.05 

  • Hi, 

      I've question on migration the codecs.

    1) the document says, 

    • Update below mentioned software components to the version no. specified along side
    Framework Component: Version No.framework_components_2_24_01 (FC_INSTALL_DIR)
    Linux Utils : Version No. linuxutils_2_24_03 (LINUXUTILS_INSTALL_DIR)

    If my dvsdk is 3.10.00.19 , and I see the release note, it's 

    framework_components_2_25_02_06

    linuxutils_2_25_04_10

    does it mean that I do not need to upgrade thoes tools?

    2) it says,

    • check if the cfg file has the MEMTCM module defined –
    var MEMTCM = xdc.useModule('ti.sdo.fc.ires.memtcm.MEMTCM');
    MEMTCM.cmemBlockId = 1;
     
    var EDMA3 = xdc.useModule('ti.sdo.fc.edma3.Settings');
    EDMA3.maxRequests = 128;

    My question is which cfg file it refer? 

    3) What does the RTSC packet refer to in below  describe? 

    "In case application is using only base class for encode and decode operation, they can just replace the existing codec RTSC package with the new ver 2.0 codec RTSC package and rebuild the application."

    Thanks for the help!



  • yixin wang said:

    If my dvsdk is 3.10.00.19 , and I see the release note, it's 

    framework_components_2_25_02_06

    linuxutils_2_25_04_10

    does it mean that I do not need to upgrade thoes tools?

    which migration  doc you r referring? please use fc_2_25_02_06 or later

    yixin wang said:
    My question is which cfg file it refer? 

    There will be one configuraton file (.cfg) in your application folder  which will have config params for RMAN interface.  for ex:  encoder test app has cfg file "h264venc_ti_dm365testapp_linux.cfg" in "dm365_h264enc_02_30_00_04_production\packages\ti\sdo\codecs\h264enc\apps\client\build\arm926" folder.

    yixin wang said:
    3) What does the RTSC packet refer to in below  describe? 

    after executing codec installer(*.exe) you get zip file.. this zip we refer as RTSC package, which will have  all necessary components to integrate in app or with other codec.

  • Hi, 

      Thanks for your patient.  For the first question,  I don't need to upgrade the framework and linuxutils if I've already in 2_25_02_06. 

    I'm referring http://processors.wiki.ti.com/index.php/Migration/Integration_Guide_for_DM36x_H.264_version_2.x_codecs

    The second question, I don't understand how to replace the old RTSC package of the old encoder.There're two folders in the new h264 encoder's zip file, one is package, the other is packages. how to replace them in dvsdk? I just replace the dvsdk_3_10_00_19/dvsdk_3_10_00_19/dm365_codecs_03_10_00_07/packages/ti/sdo/codecs/h264enc with the /dm365_h264enc_02_30_00_04_production/dm365_h264enc_02_30_00_04_production/packages. Am I right? 

  • sorry, I've made a mistake. I should referring the below section of the docs.

    Below instructions are for DVSDK 3.10.00.19.

    • Update below mentioned software components to the version no. specified along side.
    Framework Component: Ver. No. framework_components_2_25_02_06 (FC_INSTALL_DIR)
    Linux Utils : Ver No. linuxutils_2_25_04_10 (LINUXUTILS_INSTALL_DIR)
    XDAIS = Ver No. xdais_6_25_02_11(XDAIS_INSTALL_DIR)

    One may have to recompile the KOs using the new linuxUtils version. Please refer to

  • Hi

    regarding tool chain version you please refer 2.3 migration guide. I think default tool chain present 3.1 dvsdk will be fine.

    And for codec replacement you are doing right thing replacing " h264enc"  directory inside /packages/ti/sdo/codecs is correct one.

    You have to be careful about static and dynamic param struct. as you migrating from 1.1 to 2.3 you can see lot of new member and their good features. please refer test app and userguide provided with release package while setting values for new members.