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

Probleme of the demo decoder

Mingming Chen
Intellectual 310 points

I am the beginner of DM365_EVM, now I have established my software systeme, the DVSDK I use is DVSDK_3_10_00_19, the filesystem I use for DM365 is montavista linux(NFS filesysteme), now I can lance the linux in DM365, but when I try to use the demo encoderdecoder, there is an error 

Error: Failed to detect video standard, video input connected?
Error: Failed to create Ir Object
Error: Failed to create video decoder: mpeg4dec

And further more, when I used only the decoder, there is this error

Error: Failed to create Ir Object

My question is 1)what is Ir Objet, how can I solve this problem?
2)I think I have already add MT9D131(My camera) support when I compiled the kernel linux, but why it can not be detected.
3)Is there any document which I can refer to.
Thank you very much.
  • 0
    TI__Genius 9510 points

    I'm forwarding your question to experts in this area.

  • 0
    Intellectual 850 points

    Mingming,

    Did you get your questions answered?  If not, here are my suggestions:

    Error: Failed to detect video standard, video input connected?

    This error may indicate that you do not have a valid video source connected to the EVM; for example, the EVM default input is 720p on the component input.

    Error: Failed to create Ir Object

    I believe that the Ir Object is the remote control Infrared interface

    Error: Failed to create video decoder: mpeg4dec

    Within the demo applications, if the Venc1_create() function cannot identify the video input the codec cannot be created.

    If you haven't done so already, I suggest that you follow all of the procedures in the Software Developers Guide.

    Also, if you can do so, I recommend moving to DVSDK 4.xx as soon as possible - it is much more robust.

    I hope that this is helpful,

    -Chuck