Replies: 6 comments
-
This is a very good idea. And I think it's an essential feature in the real world. This will be required for both MPEG-2 TS and RTSP as well as RTMP. This will also be required for future WebRTC providers. So I think this feature should be implemented in MediaRouter. Already MediaRouter is parsing Bitstream to extract the correct media profile. (RTMP's meta is inaccurate.) Can you implement this related function in MediaRouter? We are now developing REST API, Recording, Thumbnail, RTMP Push, Signed URL. If you implement this feature we will be happy to merge it. |
Beta Was this translation helpful? Give feedback.
-
@getroot Now 0.10.9 has been released, I'll start work on this. |
Beta Was this translation helpful? Give feedback.
-
SingedPolicy has been developed, but features to limit video input quality have not been developed yet. It will fit into the SingedPolicy specification. |
Beta Was this translation helpful? Give feedback.
-
This is a very good idea, would likely be useful to many people 👍 |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
Wow! It are exactly what i wanted. And can limiting ingest Codec? I'm waiting feauture in soon |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
We utilise this in a production environment and for the majority of the time it's great, except when we have the occasional "cowboy" attempt to send us a very high bitrate/resolution because they can. Now on our busy days we're running 4/5+ concurrent streams so we limit only send out 640x360 @ 500Kbps as that is all that is needed, so all it's doing is wasting our transcode/ingest resources.
Describe the solution you'd like
Be able to limit the bitrate, resolution / framerate within the OME config, so let's say for example:
If any of these variables are above the defined limits on initial RTMP ingest handshake, then the request is denied.
Describe alternatives you've considered
We already have a pre-generated OBS profile that creates the streaming defaults, to those stated above however again as the inherit problem suggests, it's due to overzealous IT guys trying to send us 1080p/2k/4k video because they can.
Additional context
Let me know on timeframe, providing it's something you guys would be interested in implementing - If the timeframe is long, I'll take a look at implementing it myself on the latest release and give you guys the chance to re-merge it.
Beta Was this translation helpful? Give feedback.
All reactions