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

1080I display solid white

Ken Eppinett
Prodigy 210 points

I am working with a TI8148 rev 3.0 on a custom board using the 5.05.01.04  EZSDK.   

I am trying to get captured 1080I video to display without de-interlacing it.  The program follows the basic flow from the capture_encode example except that it is not turning on the deinterlacer, it passes fields instead of frames to the display component.  The display component is configured for 1080x540 input.

 If the window size is set to the size of a field 1920x540, it displays fine in the upper half of the screen as you would expect.  But if the window size is set to fill the screen 1920x1080, it just displays solid white.  I have also tried bypassing the dei component and going directly from capture to display with the same results. 

Is there something else that needs to be configured?  Could I possibly have some component disabled that is required for the display to stretch the video?  Or is this even the correct method to use?

Thanks

Ken

  • 0
    TI__Guru**** 497725 points

    Hi Ken,

     

    Why dont' you use V4L2 capture and display? Why i am asking is because ezSDK might be supporting field based capture, so only one field at a time is getting displayed. If you want to get complete frame, you either pass field through DEI and get complete frame, or use V4L2 where frame based capture is supported..

     

    Regards,

    Brijesh Jadav

  • 0 in reply to Brijesh Jadav
    Prodigy 210 points

    Hi Brijesh,

     

    Thank you for the response.  I didn't see any way to handle fields in OMX, so that was the conclusion that I came to also.  I am pretty far along with an overall OMX solution for my product, so I will probably go with deinterlacing instead of switching to v4l2 and trying to handle fields.

    Thanks

    Ken