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

Overcome jitter in video input frame-rate

ranchu
Guru 20755 points
Hello, I would like to ask how Netra should deal with jitter in frame rate of the input video. Our required input video frame-rate should be 30hz, but from past experience, we seen that there is jitter in the supplied frame-rate(+-5hz). Trying to overcome this with triple buffer also did not give better result, and resulted many times in overflow or underflow. I would like to ask if I can overcome this maybe with MCFW API, and links. I can for example change output frame-rate of capture device. Will that guarantee overcoming the jitter behavior ? Should I use larger buffer ? Best Regards, Ran
  • 0
    TI__Mastermind 20245 points

    Hi,

    If video input is Jittery Netra cant do anything. It doesnt have anything to control the jitter at input side itself. I am not getting exact definition of jitter here. Do you mean jittery means sometimes input devices will give 30FPs and sometimes it will give 25FPs.

    Regards,

    Hardik Shah

  • 0 in reply to HardikShah
    Guru 20755 points
    Hi Hardik, Yes, when I said jitter, I ment that the period between 2 frames is not constant. For the capture links there is frame-rate control only on output, but other links have frame-rate control also on input. What does it mean, frame-rate control on input (it is seen in the RDK tutorial for some other links) ? Are you familiar with methods to use with such jitter, maybe some kind of buffering ? Thank you very much, Ran
  • 0 in reply to ranchu
    TI__Mastermind 20245 points

    Hi,

    Framerate control in capture link is pure software implementation. It just drops the frames. It means if you are receiving 60FPs from output device, and if you want only 30 frames to be received, capture driver itself will drop the remaining frames. It doesnt do anything extra. This is not for jitter control. This is for overall bandwidth and use case requirement. If your input FPS is not stable capture will capture exactly as same rate as input is coming.  Nothing can be done to avoid that.

    Regards,

    Hardik Shah