• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 275 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.

changes to the omx encode example

rutuja patil
Prodigy 250 points


hello

What structure should be used for the omx encode example to access the the number of bytes generated per frame ?

Are the number of bytes allocated same to each frame while encoding using the omx example.I tried accessing the  structure field of IVDENC2_OutArg -bytesgenerated.Bbut it returns the same value each time is it right?

Thanks

  • 0
    TI__Mastermind 30480 points

    Hi,

    IVIDENC2_OutArg->bytesGenerated is the bytesGenerated for each frame and it will vary for each framebased on I/P/B frame and the bitRate used.

    Please check encode example which comes with ezsdk.

    Ram

  • 0 in reply to Ramprasad
    Prodigy 250 points

    hello ram

    We intend to encode according to the followinf frame structure.ie. IPPPPPPPPPPPPPPPIPPP.

    What chnages should be made to the encode example in ezsdk so that the encoder follows the above pattern mentioned.
    Also we are using constant bitrate of 1000000 while encoding.Are any changes to the code required to set this parameter?

    Thank you

  • 0 in reply to rutuja patil
    TI__Mastermind 30480 points

    Hi 

    In ilClient_utils.c of encode example, in function IL_ClientSetEncodeParams,

    Please set tDynParams.videoDynamicParams.h264EncDynamicParams.videnc2DynamicParams.intraFrameInterval = 15 instead of 90. This will configure your encoder for your GOP requirements.

    RatecontrolPreset is already set as LOW_DELAY(CBR) for constant bitrate encoding

    tStaticParam.videoStaticParams.h264EncStaticParams.videnc2Params.rateControlPreset = IVIDEO_LOW_DELAY;

    Ram