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

Regarding DEI Issue

Sudeep Hegde
Intellectual 660 points

Hi,

I am facing 2 issues while using DEI in progressive / Interlaced mode respectively.

EZSDK: 05_05_01_4. PG 2.0 Board

1. Performance Issue when used DEIH/DEIM in Progressive Mode

     hCap -> hDei (Bypass) -> hEnc (Progressive Mode)

     Here we are seeing lot of frame drops when compared to hCap -> hEnc directly

     We are using yuv 4:2:0 semi-planar input from hDei

2. Hang issue observed when hDei is configured in interlaced mode

     hCap(Interlaced) -> hDei -> hEnc (Progressive/Interlaced Mode)

     The strange observation is that if we don't connect hEnc to hDei, it will work properly

      Otherwise the encoder hangs after the 2nd frame.

Please let me know your inputs on it.

Regards,

Sudeep

  • 0
    TI__Mastermind 30480 points

    Hi Sudeep,

    Can you check capture_encode demo which comes with the EZSDK for 720p or 1080p input video source ?

    We are seeing only 3 frames getting initally and no more frameDrops.

    Thanks

    Ram

  • 0 in reply to Ramprasad
    Intellectual 660 points

    Thanks Ramprasad.

    We are able to resolve the performance issue while dei is in bypass mode for progressive content.

    But, we see that the encoder hangs for the 3rd emptyThisBuffer when Dei is enabled for interlace content.

    Is there is any correlation between encoder or dei path? as the output from dei is fine.

    Please let me know your input on this.

  • 0 in reply to Sudeep Hegde
    TI__Mastermind 30480 points

    Hi Sudeep,

    What is the sequence you are using? Capture_encode demo supports

    capture(1080i) ----> DEI------>Encode(1080P). Did you check this usecase?

    If you are trying to encode interlace contents, DEI is not required, you can directly feed capture input to encoder.

    Ram