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.

Sign up for GitHub

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

Jump to bottom

fix: use a better estimate of frame rate for cases with very short first sample durations #838

Merged
merged 4 commits into from
Feb 28, 2024
Merged

fix: use a better estimate of frame rate for cases with very short first sample durations #838

merged 4 commits into from
Feb 28, 2024

Commits on Feb 28, 2024

  1. use second sample 

    Signed-off-by: Cosmin Stejerean <cstejerean@meta.com>
    @koln67 @cosmin
    koln67 authored and cosmin committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    307c709 View commit details
    Browse the repository at this point in the history

  2. use second sample duration only if we have more than one sample

    @cosmin
    cosmin committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    b314487 View commit details
    Browse the repository at this point in the history

  3. update integration tests

    @cosmin
    cosmin committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    068552e View commit details
    Browse the repository at this point in the history

  4. change sample_durations to int64_t, make ts_muxer.h consistent

    @cosmin
    cosmin committed Feb 28, 2024
    Configuration menu
    Copy the full SHA
    f9842be View commit details
    Browse the repository at this point in the history