live for streams and active for restreams, so a stream or restream that exists but is not counted never takes a slot. Both parameters are returned in the stream and restream objects of the REST API, while the default limits are listed in the tariffs and technical support raises them.
The two limits follow different parameters because of what Gcore can observe. A live stream is counted by activity, since Gcore Streaming controls the output. Restreams depend on the conditions of the external target platforms that receive the stream, so it is impossible to track them by activity, and the limit follows the active switch instead.
Live streams
The live stream limit counts only streams whoselive field is true, meaning the stream is receiving input right now. The active field is an on/off switch and is not part of the count, so an enabled stream without input takes no slot.
active to true is never refused because of this limit. A stream that Gcore pulls from a source counts like a pushed stream while its live field is true, and the slot is freed as soon as the stream stops being live.
Live stream counting example
The table shows 8 streams, limit 3. Only thelive column decides which streams take a slot, so 6 are enabled (active) but only 3 are live.
Three streams are live, so the limit is reached. When Stream 3 starts receiving input, Gcore refuses it, and once Stream 1 stops, Stream 3 can go live.
Live stream errors
At the limit, Gcore refuses the stream when it starts receiving input, and what the encoder sees depends on the ingest protocol.
A disabled stream returns the reason code 2004 before the limit is checked, which is one of the WHIP reason codes. To free a slot, stop the encoder that pushes into a live stream, or set
active to false on a stream that Gcore pulls.
Restreams
Unlike the live stream limit, the restream limit readsactive, not live. A restream takes a slot whenever active is true, even when it sends nothing, while the live field only reports whether the restream is sending to the destination right now.
active set to false is never limited, and disabling an active restream frees its slot at once. Renaming an active restream, or sending active: true for a restream that is already active, is accepted.
Restream counting example
The table shows 8 restreams, limit 3. Only theactive column decides which restreams take a slot, so Restream 3 holds a slot while it waits for its source.
Three restreams have
active set to true, so the limit is reached. Enabling Restream 4 is refused, as is creating another restream with active set to true. After Restream 3 is disabled, Restream 4 can be enabled.
Restream errors
Creating a restream withactive set to true and switching an inactive restream to active: true return the same response at the limit.
N/limit, where N is the number of active restreams the request would produce. On an account with a limit of 3 and three active restreams, the request would make the fourth, so the text reads 4/3.
Restream into another stream
A restream can push into another stream of the same account, which turns stream A into the source of stream B. This A to B setup takes two live stream slots and one restream slot while both streams are live.EXT-X-PROGRAM-DATE-TIME values are generated again from the moment the restream’s packets reach Gcore. They are not copied from stream A.
When no live stream slot is free for stream B, the restream is blocked without an error. It stays active: true with live: false, stream B stays offline, and neither the restream nor stream B returns an error message. The restream keeps retrying and starts by itself within seconds after a slot is freed. With a live stream limit of 3 and two other streams live, stream A takes the last free slot, so stream B cannot go live until another stream stops.