APPLICATION: HTTP API get the number of frames received or sent for FPS. #851

Activity

1. winlinvip

   added

   FeatureIt's a new feature.It's a new feature.

   on Apr 20, 2017
2. winlinvip

   added this to the srs 2.0 releaseThis milestone has been deleted milestone on Apr 20, 2017
3. portl4t commented on Apr 20, 2017

   

   portl4t

   on Apr 20, 2017

   More actions

   amazing
4. winlinvip commented on Apr 20, 2017

   

   winlinvip

   on Apr 20, 2017

   Last edited by winlinvip

   MemberAuthor

   More actions

   Generally, frame rate calculation requires calculating a certain time difference, such as 10-second fps, or 30-second fps, or 300-second fps, to reflect the sending and receiving situation of the stream.
   For example, data can be collected every 10 seconds (the minimum statistical interval):

   In the first 10 seconds, the number of frames obtained is 1000.
   In the second 10 seconds, the number of frames obtained is 1500.
   In the third 10 seconds, the number of frames obtained is 1700.
   

   So, for the first 10 seconds, the fps=(1500-1000)/10=50fps.
   For the second 10 seconds, the fps=(1700-1500)/10=20fps.
   For the first 30 seconds, the fps=(1700-1000)/30=23.33fps.

   If the stream itself is 25FPS (original frame rate), then for the first 10 seconds, it is possible that the gop cache sent a higher frame rate. For the second 10 seconds, there is actually stuttering and the frame rate is insufficient. From 30 seconds onwards, the frame rate is slightly lower.

   How to determine the original frame rate of the stream? The configuration on the encoder can be checked by accessing the encoder's interface or through the business system. The frame rate provided by SRS is the distributed frame rate.

   TRANS_BY_GPT3
5. Jeff885 commented on Apr 20, 2017

   

   Jeff885

   on Apr 20, 2017

   More actions

   Good
6. winlinvip commented on Apr 23, 2017

   

   winlinvip

   on Apr 23, 2017

   MemberAuthor

   More actions

   
7. winlinvip

   closed this as completedin ff87318on Apr 23, 2017
8. winlinvip

   added a commit that references this issue on Apr 23, 2017

   Merge SRS2 for #851

   c97f223
9. winlinvip commented on Apr 24, 2017

   

   winlinvip

   on Apr 24, 2017

   Last edited by winlinvip

   MemberAuthor

   More actions

   The time interval for updating Frames data is configured as follows:

           # the normal packet timeout in ms for encoder.
           # default: 5000
           normal_timeout      5000;
   

   The update can be done by setting the timeout for receiving packets. It should not be set too short, otherwise the encoder will be considered timed out, usually 3-5 seconds or more.

   The calculation of FPS itself is not real-time because when TCP sends packets, it is more like pulses and not sending one packet at a time, but rather in batches. Therefore, adjusting this time interval to 1 second does not make sense, and it will not affect the calculation of FPS even if it is set to 3-5 seconds or more.

   TRANS_BY_GPT3
10. Trojann commented on Jul 31, 2020

    

    Trojann

    on Jul 31, 2020

    Last edited by Trojann

    More actions

    Can I get duration of live from HTTP API, and what live_ms mean?
11. winlinvip

    self-assigned this

    on Sep 17, 2021
12. winlinvip

    added

    TransByAITranslated by AI/GPT.Translated by AI/GPT.

    on Jul 28, 2023
13. Endt4sk

    added a commit that references this issue on Mar 30, 2024

    Fix ossrs#851, HTTP API support number of video frames for FPS. 2.0.240

    This issue will close once commit ff87318 is merged into the '2.0release' branch.

    ff87318