Skip to content
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

Added option --force-fps #678

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

dronus
Copy link

@dronus dronus commented Jan 8, 2019

A new option --force-fps creates synthetic timestamps to force playback at the given rate, overriding original media timestamps.

@popcornmix
Copy link
Owner

Can you explain what the use case is for this?

@dronus
Copy link
Author

dronus commented Jan 8, 2019

This allows for playing videos with a varying framerate at fixed speed (eg. screen refresh rate for example), play videos sporting bad timestamps with a fixed rate as fallback and so on.
For example I had one case where the RaspberryPi's raspivid tool stores DTS or PTS according to 25fps always even if not running at this rate. Those videos can then be played at different, desired speeds by omxplayer.

@dronus
Copy link
Author

dronus commented Jan 8, 2019

I also just wondered why omxplayer's --fps option wasn't working in many cases until I found out that it only applies to streams sporting no timestamps by itself.

@wallneradam
Copy link

Thank you very much for this PR! I have a raw H264 stream which don't have valid timestamp. Without this patch it plays as fast as it can, but now it is smooth.
It should be the default behaviour of "--fps" in case of wrong timestamps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants