• State
  • Locked Locked
  • Replies 8 replies
  • Subscribers 98 subscribers
  • Views 809 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Change Video Codec error

hb chen
Expert 2640 points

Dear Experts,

We are using DVR_RDK 3.5.

We are trying to change codec from REL.500.V.H264AVC.E.IVAHD.02.00.04.01 to REL.500.V.H264AVC.E.IVAHD.02.00.08.00 due to "inserted I frame after changing rate change" isses ( http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/716/p/359841/1263742.aspx#1263742 ).

But we meet problems.

Attached file is log file.
2502.CodecChange_SettingsError_log_20140822112525.txt


When we start McFW, error occurs.

Here is the method to change codec:

Add codec Lib  trunk\ti_tools\codecs\REL.500.V.H264AVC.E.IVAHD.02.00.08.00

Modify trunk\dvr_rdk\Rules.make : 56

h264enc_DIR      := $(TI_SW_ROOT)/codecs/REL.500.V.H264AVC.E.IVAHD.02.00.08.00

This log has:

 Aug 22 11:17:53 - user.notice dsp: [   14.910][m3video] 11517:!ERROR!:ENCLINK::links_m3video/iva_enc/encLink_h264.c:[233]::INTERNAL ERROR:-1

Aug 22 11:17:53 - user.notice dsp: [   14.910][m3video] ALGCONTROL FAILED:CMD:1

Aug 22 11:17:53 - user.notice dsp: [   14.910][m3video] ERROR: IH264ENC_LEVEL_INCOMPLAINT_PARAMETER , 0,

Aug 22 11:17:53 - user.notice dsp: [   14.910][m3video] ERROR: IH264ENC_PROFILE_INCOMPLAINT_FMO_SETTING = 2,

Aug 22 11:17:53 - user.notice dsp: [   14.910][m3video] ERROR: IH264ENC_PROFILE_INCOMPLAINT_INTERFRAMEINTERVAL = 4,

Aug 22 11:17:53 - user.notice dsp: [   14.910][m3video] ERROR: XDM_UNSUPPORTEDPARAM = 14,

Aug 22 11:17:53 - user.notice dsp: [   14.910][m3video] ERROR: XDM_FATALERROR = 15

Could you plz provide suggestion to resolve this bug?

thx ~


HB

  • 0
    TI__Guru 59700 points

    Make sure you don't try to add the new libraries into old codec release.Makes rue you extract the release into separate folder and ensure you correctly update Rules.make

    To rebuild:

    Do

    rm -rf build

    make clean

    make dvr_rdk.

  • 0 in reply to Badri Narayanan
    Expert 2640 points

    Dear Badri,

    > Make sure you don't try to add the new libraries into old codec release.

    > Makes rue you extract the release into separate folder and ensure you

    > correctly update Rules.make

     

    Yes.

    I made different folder, the name is REL.500.V.H264AVC.E.IVAHD.02.00.08.00.

     

    I modified encoder folder setting.

    >   trunk\dvr_rdk\Rules.make : 56

    > h264enc_DIR      := $(TI_SW_ROOT)/codecs/REL.500.V.H264AVC.E.IVAHD.02.00.08.00

     

    Is this a correct?

     

    > To rebuild:

    > Do

    > rm -rf build

    > make clean

    > make dvr_rdk.

     

    Yes.

    I deleted build folder and make clean , make dvr_rdk.

     

    But still has problem.

    HB

  • 0 in reply to hb chen
    TI__Guru 59700 points

    Pls contact your TI FAE. We will share entire encLink folder whch you can compare and merge to your codebase. We migrated recently to latest encoder version and did not face any issue.You may be using very old dvrrdk version

  • 0 in reply to Badri Narayanan
    Expert 2640 points

    Dear Badri,

    Our dvrrdk version is 3.5 (DVR Reference Design version GA-03.50.00.05 in release note).

    Do you mean that we need to use latest dvrrdk version? (We cannot use latest dvrrdk version due to product reason)

    or just need to use latest codec version?

    thx ~

    HB

  • 0 in reply to hb chen
    TI__Guru 59700 points

    You don't need to migrate DVRRDK version. You only have to migrate codec version to resolve this issue.We migrated to latest encoder version and didn't face any issue in dvrrdk.

    Since you are not able to get it working , there may changes required in encLink_h264.c apart from codec version change which you are missing. To get the required changes you will have to selectively manually merge encLink_h264.c file from latest DVRRDK codebase

  • 0 in reply to Badri Narayanan
    Expert 2640 points

    Dear Badri,

    Is there any difference between REL. 500.V.H264AVC.E.IVAHD.02.00.08.00 and REL. 500.V.H264AVC.E.IVAHD.02.00.08.01?

    What version should we use? 00 or 01? (But when we compile 01 version, there are some compile errors)

    thx ~

    HB

  • 0 in reply to hb chen
    TI__Guru 59700 points

    You should use REL. 500.V.H264AVC.E.IVAHD.02.00.08.00 version .As explained in the release notes the .01 version is for use with codegen tools 5.x and is incompatible if rest of the modules are compiled with codegen tools 4.x

  • 0 in reply to Badri Narayanan
    Expert 2640 points

    Dear Badri,

    I contact with local FAE, here is his reply:

    ---------------------------------------------------

    We checked H264 v2.00.08.00 with TMS470 cgt 4.9.5 in DVRRDK v4.1 and it compiled and worked well. So we think cgt4.9.5 is fine.

    I think the left parts is the back port encLink_h264.c from RDK v4.1 to v3.5. May I suggest you to attach encLink_h264.c and encLink_h264_35.c to below e2e to get Badri’s comments? Because he does not like to receive any DVRRDK questions emails, but he still very aggressive answering any DVRRDK questions at e2e forum.

    ----------------------------------------------------

    Attached file is encLink_h264.c.

    encLink_h264.c is for RDK v4.1. 1884.encLink_h264.c

    encLink_h264_35.c is for RDK V3.5 that modify by our side.4048.encLink_h264_35.c

    plz help ~

    thx ~

    HB