Frame process skipping behaviour

In Progress

Comments

1 comment

  • Avatar
    Ichiro

    Hi Fujiwara Daichi,

    Thanks for your question, 

     

    1. A certain camera is detected 10 frames at a time, but the detection process takes 20 frames,

    This explanation is not very clear, and we are unable to fully understand your description at the moment. Could you please elaborate on the exact case? Providing images or further evidence would also be helpful.

     

    2. object detection takes time longer than frame update period.

    Which object detection feature or implementation are you referring to? Are you using a sample from the Nx GitHub repository, or is this related to your custom implementation?

     

    3. I want to detect object per 10 frames and display the result.

    This is achievable with the SDK, and there should be no issue implementing it.

     

    4. Even though it is displayed at 10 frame intervals, there is a delay of 10 frames than expected. (It will be displayed at least every 20 frames)

    This explanation is a bit unclear. Could you refine and rewrite this for better understanding?

     

    What is this warning in detail?

    The warning is straightforward—it indicates that the image queue is full because the frames are not being processed (digested) in time. As a result, frames in the queue are forcibly dropped to accommodate newly incoming frames. This behavior typically occurs when:

    •The analytics process is too slow to handle the incoming frames.
    •The FPS from the camera is unstable, sometimes higher or lower than expected.

     

    Thanks.

    0
    Comment actions Permalink

Please sign in to leave a comment.