Skip to main content
Gcore Video Streaming accepts two types of video input and applies specific requirements to each. Both are transcoded to the output set by the transcoding options, so a source can exceed that output.
  • Live streams: an ongoing stream sent to Gcore by PUSH or pulled by Gcore from the source. Live input must stay stable because transcoding happens in real time.
  • VOD files: uploaded video files that Gcore processes after upload. VOD input can use many containers and codecs, but the source parameters should stay consistent through the file to avoid transcoding errors.
After ingest or upload, Gcore transcodes the source into ABR renditions and delivers them through CDN.

Input and output limits

The input limits are wider than the free output limits, because Gcore accepts 4K sources and 60 FPS frame rates. Free transcoding outputs H.264 up to Full HD 1080p at 30 FPS for live streams and VOD files, while premium encoding lifts those limits.

Live streams

Live input requires a master stream sent to Gcore with the correct parameters. Configure OBS, FFmpeg, a hardware encoder, or a custom encoding pipeline to push or expose the stream with the parameters below. Gcore receives this master stream and transcodes it for HLS and MPEG-DASH delivery.

Ingest protocols

Both PUSH and PULL methods are available where applicable.
HLS over HTTP PUT is not supported.
The master live stream should use these parameters. They keep the transcoding stable regardless of the selected output. The recommended video bitrate depends on the source resolution and frame rate. A source above 1080p is accepted, and free transcoding scales it down to 1080p.
Live stream parameters must remain stable during the broadcast. Mid-stream changes to codec, profile, resolution, frame rate, pixel format, color range, chroma format, or audio layout can interrupt ingest or transcoding.
Primary and backup ingest is configured separately, in the ingest and backup workflow.

Supported codecs for live

The source video of a live stream must use MPEG2, AVC, or HEVC with 8-bit color depth, up to 4K, and AVC (H.264) is the safest choice. A stream sent with another codec or bit depth can fail during transcoding, and RTMP has protocol limitations described in RTMP.

Live ad markers

SCTE-35 is a standard from the Society of Cable Telecommunications Engineers that uses markers to signal ad insertion opportunities in a live stream. Gcore does not support SCTE-35 during transcoding of live streams.

VOD files

For VOD, the customer manages the source file before upload: container, codec, audio tracks, subtitles, and source consistency. Gcore processes the uploaded source, including MXF files, and creates ABR renditions for playback. The recommended parameters for a VOD source file are listed below. For VOD and live-derived recordings, it is not enough that the source starts with supported parameters. These parameters must stay stable for the full duration — a source that changes from yuv420p to yuvj420p near the end can be accepted initially but fail later during transcoding. VOD upload options are described in upload via API.

Supported containers

The VOD container is identified by its file extension.
A source can also be identified by the MIME subtype quicktime, x-ms-wmv, mpeg-tts, or vnd.dlna.mpeg-tts. These correspond to the file extensions .mov (QuickTime), .wmv (Windows Media), and .ts or .mts (MPEG-TS variants).

Supported codecs for VOD

The source video of an uploaded file must use one of the codecs below. If a video is uploaded with an unsupported codec, transcoding can fail. These input codecs are validated during the initial processing stage before any adaptive bitrate renditions are created.

Custom input requirements

If the recommended parameters do not fit the workflow, contact support@gcore.com or the account manager. Gcore can review custom codecs, FPS values, Apple ProRes, High 4:4:4, and other advanced requirements.