-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can --dvr-framerate be an optional parameter? #22
Comments
It could be that you fly with 120/60 but want the recording to be 60 or even 30 fps.. but I think it should be a solid default. |
--dvr-framerate does not change the frame rate of the video Correctly.
I think:
|
This FPS is calculated by literally counting the number of received frames: Line 309 in dbf3f88
And the way FPS you specify in commandline is used is quite interesting: for each frame it represents a duration of this frame and current DVR assumes that FPS is constant: Line 158 in dbf3f88
I think what we can do is to rely on Radxa's clock and just measure the time between frames and write it as frame duration to each individual frame? It's not 100% clear if it's ok to have non-fixed |
Why --dvr-framerate parameter must required? Can we just get the frame rate from the video stream?The FPS shows in OSD is the FPS I set in IPC.
The text was updated successfully, but these errors were encountered: