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

IVAHD h264enc: What's the plan to support CBR with interlaced input?

Chris Meng
Mastermind 37736 points

Hi,

In IVAHD h264enc user guide, we found the with interlaced input, the code is not supporting CBR. But my customer wants to keep the bit rate and video quality and accepts frame drop. It seems that CBR meets the request.

Does TI has plan to support CBR with interlaced input?

  • 0
    TI__Genius 14000 points

    There is no plan of interlaced to be supported with CBR. In fact most of the CBR properties (excluding frame skip) can be achieved by VBR with proper RC settings.

    so this constraint should not impact anyone - what is the use case which demands interlaced + CBR ? and What are the issues to use VBR with smaller HRDBufferSize?

    With Regards,

    Pramod

  • 0 in reply to Pramod Kumar Swami
    TI__Mastermind 37736 points

    Pramod,

    Thanks for quick reply.

    As I mentioned in the post, when there is heavy moving, customer requests the bit rate without big change and the video quality can't drop a lot. With CBR, it can keep the video quality with frame drop.

    Can smaller HRDBufferSize meet customer's requirement?

  • 0 in reply to Chris Meng
    TI__Expert 4725 points

    Chris,

    If you want to maintain the quality, with some amount of fluctuations then larger HRD buffer size can help. Also as pramod said most of the use case can be achieved with VBR itself. 

    To stop degradation of quality, max qp value can be reduced. Quality mainly degrades because user allow qp to go to very high value. If you restrict Qp value appropriately then a constant quality can be expected with VBR.

    if problem still persists then you can share the configuration parameter and generated stream then we can have look into that.

    Regards

    Deepak Poddar