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

about audio & video playing issue on kernel 2.6.18

YHLShareware
Intellectual 830 points

All,

I just switched to the kernel 2.6.18 (dvsdk2.0), when I played audio using alsa framework while playing video using decode demo from dvsdk1_30_00_40, audio was stopped and found studdeding on video display.

Your much help is appreciated. thanks very much.

 

Best Regards,

Jeff

  • 0
    TI__Mastermind 37340 points

    Hi Jeff,

    dvsdk_1_20_00_40 was validated with MV Pro 4.0.1 kernel 2.6.10.  It is a big jump to go to 2.6.18 MV pro 5.0 kernel.  We normally recommend customers use software components from the same DVSDK release.

    Also, please note that DVSDK 2.0 is in EA (Early Adoptor) status, and some customers in this forum community have noted problems with it.  Unless you are willing to do some legwork to overcome issues you may encouter, I would recommend waiting on official DVSDK 2.0 release if you can.

  • 0 in reply to Juan Gonzales
    Intellectual 830 points

    Juan,

    Thanks for your reply. An another issue is that if 2.6.18 kernel have resolved the bug what Audio driver may get stuck after many hours while playing clips with audio & video? How to resolve it at the linux 2.6.10 kernel? Thanks very much.

    Jeff

  • 0 in reply to YHLShareware
    TI__Mastermind 37340 points

    I believe the audio driver is much different in 2.6.18 (based on ALSA standard) than on 2.6.10 (based on OSS standard).  Therefore, it would be difficult to pull in just the audio driver changes... If you have to have that fix now, you can move on to DVSDK 2.0 EA, I just wanted you to be aware that this is an AE release before you get to frusturated for going down this path.  If you can wait, I would wait for the official DVSDK 2.0 to become available.