Genvid Ingest

The Genvid Ingest shows you how to add an RTMP Ingest server in your project using gvencode, which allows you to work with an external A/V source.

Note that you can only add audio and video streams to the composition. The Ingest server can’t receive data streams or notifications, nor can it send commands or events.


Changing the video resolution while streaming is not supported.

For this example, we will start by setting up the Genvid Studio Service with an instance of the DirectX Cube sample. We will add the second instance with the Ingest server and a local instance of OBS Studio (version 20 or later) connected to it, providing us a second source for a webcam.

Configure the Cluster

  1. Follow the Genvid Studio Service instructions to start all the services.

  2. Verify everything works correctly.

  3. Click Stop All to stop all services.

  4. Load the Ingest configuration:

    py load
  5. Confirm the Ingest job is present on the Cluster UI.

  6. Click the Start All button to restart the services.

  7. Wait for the Ingest link to turn blue.

  8. Right click the Ingest link and select Copy link address.

    You’ll need the link address to configure OBS.

Configure OBS Studio

  1. Download and install OBS Studio.

  2. Configure it and select the scene you want to stream.

  3. Click File > Settings.

  4. Select Stream.

  5. Select “Custom” in the Service field.

  6. Paste the Ingest link in the Server field.

  7. Paste the Stream Key of your streaming service.

    It should start with rtmp://.


    If your browser added unsafe- to the address, delete it from the URL.

  8. Select the following (recommended) settings:

Output (Advanced) Video Bitrate 2000 to 6000 kbps Dependent on your stream quality (resolution and FPS).
Encoder x264 or h264
Rate Control CBR
Profile Baseline, Main, High
Audio Bitrate 128 to 320 Kbps
Audio Sample Rate 44.1khz or 48khz
Channels Mono or Stereo
Video Base (Canvas) Resolution Same as the game.
Output (Scaled) Resolution Same as the game.
Downscale Filter Lanczos (sharpened scaling, 32 samples).
Common FPS Values Same FPS as set in Genvid stack (framerate of the video stream = 30 or 60).
Advanced Renderer Direct3D 11
Color Format NV12 or I420
YUV Color Space 601 or 709
YUV Color Range Partial or Full

Now you can start streaming.


The Genvid stack is based on a “first come, first serve” principle when starting the jobs. To ensure that the OBS stream is received properly, it is recommended that you start the Ingest job before you start streaming from OBS.

Start Jobs in this order: #. Services #. Studio #. Ingest #. Web #. Open OBS #. Start the game job when you are ready to stream the game.


Don’t start the game until you see the OBS stream in Studio.

Compose the Stream

Go back to Cluster UI and click the Studio link. Your stream is now the second source. See the Studio website for information on working with your broadcast stream.

Streams Timing

This section covers the timing of audio / video streams when several sources are involved in a production.

The following diagram shows the deployment of a production with a first source that shows the game and a second source that contains the audio and video of a commentator. The second source can be used in PIP, voice-over, or as is. This diagram also shows that a director makes the realization of the broadcast with the Genvid Studio.

Game deployement diagram

Fig. 98 Diagram of a broadcast deployment with a video game and a commentator

Any processing on a stream results in a delay on the stream. This delay is mainly due to the encoding, decoding, and transmission of streams. The typical delay between the gamer and the director is about 15 frames or 0.5 seconds. The delay between the commentator and the director is about 3 seconds.

You can adjust the delay using the controls in the Sources section of the Studio website.

Source delay adjustment

Fig. 99 Source Delay adjustment control

Script Reference

Ingest sample script

usage: [-h] [--loglevel {DEBUG,INFO,WARNING,ERROR}] [--logformat LOGFORMAT] [-c CLUSTER_ID]
                 {env,load,unload} ...

Positional Arguments

command Possible choices: env, load, unload

Named Arguments


Possible choices: DEBUG, INFO, WARNING, ERROR

Set the script log level

--logformat Set the script log format
-c, --cluster_id

The cluster id. If not set with the command line, uses the environment variable GENVID_CLUSTER_ID if it exists. Otherwise defaults to ‘local’

Default: “local”



Print environment variables env [-h]


Load the specified target definition in the cloud load [-h]


Unload the specified target definition in the cloud unload [-h]