-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Inaccurate keyframe interval, fps metrics when querying stream info over API #1445
Comments
This is the difference between the config value and the measured value. In the API, the origin responds with setting values, and the edge responds with actual measured values. |
That sounds like a reasonable solution, thank you 👍 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I added the following information to the GET Stream API: It has been committed to the master branch and will be available from the next release. bitrate_conf Sorry I'm so late! |
I updated this to this:
|
I was going to suggest not changing the old names, this is a good update thank you! |
@bchah I thought you said you needed this too, right? |
@getroot yes, thank you! I saw the commits and am excited to incorporate this in the next release. It gives users a way to see their "current" frame and bit rates. Great work and thank you very much :) |
Describe the bug
When querying a stream info (api endpoint:
v1/vhosts/default/apps/live/streams/<stream>
), the server reports strange values for keyframe interval and fps (fractional values)while querying the same stream but in the origin server returns correct FPS values, although the keyframe value reported is definitely different from the one set in OBS
OME origin/edge Config https://gist.github.com/hernanrz/87fb0ff693cbd91ff50c3f6be1436a58
Version: OvenMediaEngine v0.16.0 ((From archive)) running with docker image airensoft/ovenmediaengine@sha256:167de56e8b6600e0f459038780fff17659d7f835a3464834c20403b1e694564e
The text was updated successfully, but these errors were encountered: