Skip to content

Limiting Ingest Variables (Bitrate, Resolution, Framerate etc) #201

@dbContext

Description

@dbContext

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:

<Providers>
	<RTMP>
		<RestrictIngest>
			<Width>640</Width>
			<Height>360</Height>
			<Framerate>30.0</Framerate>
			<Bitrate>500000</Bitrate>
		</RestrictIngest>
	</RTMP>
</Providers>

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions