• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 101 subscribers
  • Views 439 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.

there is sawtooth while playing captured composite signal

Huai Hellen
Expert 1030 points
Other Parts Discussed in Thread: OMAP3530

Hi, Jatin

when play captured composite signal, there is sawtooth, when stopped, the sawtooth disappears.

In software, I have enabled ENABLE_DEINTERLANCED macro

  • 0
    TI__Genius 14405 points

    What device and OS are you using?

    Please also elaborate on the application you are running.

  • 0 in reply to Paul.Yin
    Expert 1030 points

    My device is based on omap3530 and bsp version is 6.14.01, OS is Wince 6.0 R3.

    In fact, the bsp version makes little difference, I tested 6.14.01, 6.15.00 and latest bsp Arm_A8_00, the results are the same.

    My application is ported from the MOSQUITO application which is rooted in path:  _winceroot\public\\DIRECTX\SDK\SAMPLES\DDRAW\SRC\MOSQUITO, which can capture Aux vedio input such as DVD, camera sensor,etc.

  • 0 in reply to Paul.Yin
    TI__Prodigy 280 points

    Do we support software de-interlacing processing on ARM side? I think that we don't have hardware de-interlacing. pls correct me if wrong. thanks.

  • 0 in reply to Justin Hua
    TI__Genius 9185 points

    Can you capture and post a picture of the issue. I want to make sure we are talking about a deinterlacing issue and not something else.

    We do not have sw deinterlacer integrated/tested in the WinCE releases. (there is a deinterlacer as part of the Linux DVSDK  release for Omap3530 but there is currently no plan to integrate that in the WinCE release).

  • 0 in reply to Jatin Jain
    Expert 1030 points

    As Jatin said, could I think current bsp for wince could not support hw deinterlacer on arm side just as Justin Hua reffered?

    I could not capture the picture with sawtooth because when captured, there was no sawtooth, just play, there was sawtooth.

    As you say, there is currently no plan to integrate that in the WinCE release, could you provide the corresponding source code in Linux DVSDK or the download page link for Linux DVSDK for us to reffer?

  • 0 in reply to Huai Hellen
    TI__Genius 9185 points

    You can find the latest Linux DVSDK release for Omap3530 here 

    http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/dvsdk/DVSDK_4_00/latest/index_FDS.html

    If you search in the forums you should find some threads on the deinterlacer for Omap3530 like the one below.

    http://e2e.ti.com/support/dsp/omap_applications_processors/f/447/p/43634/153357.aspx#153357

    Please note that the deinterlacer is in the DSP. If you have more questions on this, post in the Linux forum http://e2e.ti.com/support/embedded/f/354.aspx

  • 0 in reply to Jatin Jain
    Expert 1030 points

    Thanks, Jatin.

    Could I think when integrated sw deinterlacer in Wince Release, it can solve the sawtooth issue effectively?

  • 0 in reply to Huai Hellen
    TI__Genius 9185 points

    I cannot be sure about it since I have really not seen the issue. 

    One thing you could do is to load the Linux demo images (refer to the Linux documentation) and try out a capture and see if you observe the same issue or not. Ideally you would also want to try the same capture app using an older version (when deinterlacer was not available) to be sure. If before the deinterlacer the problem looked similar to the one you are seeing now then it can be safely assumed that deinterlacer should solve your problem. Please note that no one on the WinCE forum list has expertise on the specific Linux release and you will have to post any specific questions to the Linux forum.

     

     

  • 0 in reply to Jatin Jain
    Expert 1030 points

    Below is source code in current BSP, and I define the macro 'ENABLE_DEINTERLANCED'.

    I do not know what the sw deinterlacer you said reffer?

     

    #ifdef ENABLE_DEINTERLANCED    //There is no field pin connected to OMAP3 from tvp5416, so only for BT656.
        //de-interlance
        ConfigOutlineOffset(NUM_BYTES_LINE, EVENEVEN, 1);
        ConfigOutlineOffset(NUM_BYTES_LINE, ODDEVEN, 1);
        ConfigOutlineOffset(NUM_BYTES_LINE, EVENODD, 1);
        ConfigOutlineOffset(NUM_BYTES_LINE, ODDODD, 1);  
    #endif //ENABLE_DEINTERLANCED

  • 0 in reply to Huai Hellen
    TI__Genius 9185 points

    There is some terminology confusion. What that piece of code does is to allow you to capture the odd and even fields and store them in different ways (separate fields or interleaved etc) but it does not do any processing on those fields to get a smooth image. So playing with those registers is not going to get you a smooth image. The settings allow the storage of the fields such that any code that processes these frames can access them in the most efficient way. 

    So what you really need is a deinterlacer that takes the odd and even fields and combines them into a single frame with some processing that will smooth out the offsets between the two fields (which is most pronounced when there is lot of motion). The hw does not have this feature. The DSP code includes the deinterlacer but it is not integrated into the WinCE direct show framework. 

    I hope this clarifies.