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

Motion detection problem on dm368 appro 2.6

Gordon Gao
Prodigy 195 points

Hi all,

Now, we are  testing motion detection on Dm368 appro 2.6 .

and we find the motion detection is not stable.

it seems it could be the memory leak problem and have be fixed  on appro 3.0

now  we have got the appro 3.0,and I want to know which files or settings we should modify if I still want to use motion detection on appro 2.6.

Thanks

  • 0
    TI__Genius 11000 points

    Gordon,

    Can you tell us the issue with logs that you are facing, you can look at alg_motiondetect.c for details on motion detect implementation

    ALso, avserver.c and avservermain.c will have all the allocation done. You can look at alg_videnc.c where the buffer for motion vector and SAD values from codec are allocated.

    Please give us more details so that we can help solve this

    Regards,

    Raghu

  • 0 in reply to Raghu Kudva
    Prodigy 40 points

    Hello All,

    I have the same problem with motion detector on DM368 IPNC ver.3.0.

    When motion detector enabled, H264 streams hangs after some minutes of work.

    Without motion detector work perfectly.

    Best regards, Andrey