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

Strange behaviour In H264 2.chain Mode on DM368

sujit mahapatro
Genius 3930 points

Hi,

i am observing some stange behaviour some time in chain mode.

right vertical half  picture has some pink lines. where as same is ok in one-shot mode.

 

  • 0
    TI__Mastermind 19985 points

    Hi,

    What do you mean by "strange behavior sometimes"? Have you tried increasing the blanking interval or reducing the pixel clock? Does it happen for all resolution capture? Can you please share the YUV data?

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Genius 3930 points

    Anshuman,

    you mean to to check resizer clock div.n and div.m ? what is blanking interval and how to increase it ?

    the capture data is fine because both mjpeg and one-shot mode output is fine.

    the error image you are viewing in my post is only in chain mode.if yuv data will be helpfull for analysis then i will send.

     

  • 0 in reply to sujit mahapatro
    TI__Mastermind 19985 points

    Sujit,

    In continuous mode, div.n and div.m is not valid. You have to play with your sensor settings to increase the blanking interval and allow more time for the resizer to dump data. But the same resolution is good in one-shot mode makes me feel that it might not be bandwidth. What do you mean by mjpeg is fine? Do you mean mjpeg in continuous mode is fine? YUV data output from capture port in continuous mode will surely help.

    Regards,

    anshuman

  • 0 in reply to Anshuman Saxena
    Genius 3930 points

    Thanks ansuman,

    i can send the yuv data tomorrow.

    MJPEG is working fine, i mean as you know in our camera multiple codec support is there, i just wanted to tell same time mjpeg ouput is ok. so there must not be any issues with captured data.

  • 0 in reply to sujit mahapatro
    TI__Mastermind 19985 points

    So your point is that the problem is with the H.264 encoded stream only? Now, i assume you are not changing parameters for the encoder between one shot mode and continuous mode, so encoder as such is eliminated. I am suspecting either there is problem with the buffer management and or you are not passing the right addresses to encoder when in continuous mode. Can you check these things? Also, can you dump the YUV data with the addresses that you are using as input to encoder?

    Regards,

    anshuman

  • 0 in reply to Anshuman Saxena
    Genius 3930 points

    Hi Anshuman,

    i have moved to the recent Platinum Codec version H264ENC.version.02.10.00.06.wizardversion.0.5.2 releses on Dec.

    this problem is not happening with the new version.

    thank you very much for your help.

    sorry for the delayed respose because of the holidays.

    we can close this thread.

  • 0 in reply to sujit mahapatro
    TI__Mastermind 19985 points

    Hi Sujit,

    Thanks for confirmation. So it seems like the possible problem was with the EDMA bug that is fixed in latest codec. Still not sure, how this could be impacting your application data flow and causing the failure.

    Anyways, marking this post as verified, as the issue has been resolved by moving to ver 2.10.00.06 of H.264 Encoder on DM36x.

    Regards,

    anshuman