Intel Quick Sync encoding server: drivers, FFmpeg qsv encoders and checks

An Intel Quick Sync encoding server hands H.264 work to the media engine in the processor's graphics, driven by FFmpeg's h264_qsv encoder through Intel's VA-API driver and media runtime. On a Xeon E3 with Iris Pro graphics that means several layers to install and one listing to read before you trust it on air. Below: each layer, a test encode, a live relay, and what to check when the encoder will not open.

Steps
9
Reviewed
Runs on
Dedicated
Written by
Get Stream Hosting

By the Get Stream Hosting team

Every step was checked against the software's official documentation by independent reviewers before publishing. Last reviewed .

Pre-flight check

What the graphics block will and will not encode

Quick Sync is the fixed-function media engine inside Intel processor graphics, and what it encodes depends on the generation. Xeon E3 chips with Iris Pro graphics span three generations: Haswell (the E3-1284L v3), Broadwell and Skylake. Intel's media driver and Media SDK runtime start at Broadwell, so this guide covers those two, and Intel's media driver documentation lists them separately. If lscpu reports an E3-1284L v3, the iHD driver will not load on it.

CodecBroadwellSkylake
H.264 decodeYesYes
H.264 encodeYes, full-feature driver onlyYes
HEVC 8-bit decodeNoYes
HEVC 8-bit encodeNoYes, full-feature driver only
HEVC 10-bitNoNo
VP9 or AV1 encodeNoNo
Largest encoded frame4096 x 40964096 x 4096

For a channel that plays H.264 over HLS, either generation does the job.

Do not guess the generation from a product name. Read it off the machine: lscpu prints the model, and Intel's specification page for that model gives the code name. The vainfo listing below is the final word on what your driver actually exposes.

The software stack, layer by layer

FFmpeg never talks to the chip directly; a missing layer shows up as an encoder that refuses to initialise.

LayerUbuntu 24.04 packageIts job
Kernel driveri915, in the kernelPresents the graphics as a render node under /dev/dri/
VA-API driverintel-media-va-driver-non-freeIntel's iHD driver, full-feature build; the plain intel-media-va-driver is the free-kernel build with fewer encode paths
Media runtimelibmfx1The Intel Media SDK runtime, which is what Broadwell and Skylake use
Dispatcherlibvpl2Pulled in by FFmpeg; finds and loads the runtime
FFmpegffmpegProvides h264_qsv and hevc_qsv

The runtime is the trap. Intel's newer oneVPL GPU runtime begins at Tiger Lake, so on these Xeons the encoding is done by the older Media SDK runtime. Intel archived the Media SDK project in May 2023, so it is frozen. Ubuntu 24.04 builds FFmpeg against the newer dispatcher, and Intel documents that dispatcher as able to load the legacy library, libmfxhw64.so.1, which libmfx1 installs.

Install the layers and read the listing

On a fresh Ubuntu 24.04 install, from an account that can use sudo:

sudo apt update && sudo apt install -y ffmpeg vainfo intel-media-va-driver-non-free libmfx1
ls -l /dev/dri
LIBVA_DRIVER_NAME=iHD vainfo
ffmpeg -hide_banner -encoders | grep qsv

The non-free driver sits in Ubuntu's multiverse component and the others in universe. If apt cannot find a package, enable it with sudo add-apt-repository multiverse and run the install line again. Then work down this list:

  • ls -l /dev/dri shows a renderD node. No node means the operating system cannot see the graphics, and nothing higher up will work.
  • vainfo names the Intel iHD driver and pairs VAProfileH264Main and VAProfileH264High with VAEntrypointEncSlice (or VAEntrypointEncSliceLP). Lines ending in VAEntrypointVLD alone are decode only.
  • ffmpeg -encoders lists h264_qsv and hevc_qsv. That proves the build has them, not that the chip will run them; the test in the next section does that.
  • Running FFmpeg as a non-root account? Note the group that owns the render node in the ls -l output, add the account to it, and log in again.

A test encode, then a live relay

Prove the hardware path with a synthetic picture and no output file:

ffmpeg -hide_banner -v verbose -f lavfi -i testsrc2=size=1920x1080:rate=30 -t 30 \
  -vf format=nv12 -c:v h264_qsv -preset medium \
  -b:v 4M -maxrate 4M -bufsize 8M -g 60 -f null -

What to expect: the progress line shows speed= above 1x and a frame count that climbs without stalls. With -v verbose the encoder prints the rate-control method the runtime really chose. FFmpeg's documentation warns that it can differ from the one you requested, so read it rather than assume.

For live work, pull, transcode, push keeps the machine closed: FFmpeg reads your source, scales on the processor, encodes on the graphics and sends RTMP onward. Your own live video channel with us can be that target; PRO and Platinum take a 5 Mbps ingest at 1080p.

ffmpeg -hide_banner -i "SOURCE_URL" \
  -vf scale=-2:720,format=nv12 \
  -c:v h264_qsv -preset medium -b:v 3M -maxrate 3M -bufsize 6M -g 60 \
  -c:a aac -b:a 128k -ar 48000 \
  -f flv "rtmp://INGEST_HOST/APP/STREAM_KEY"

Replace SOURCE_URL and the RTMP address with your own. -g 60 puts a keyframe every two seconds for a 30 fps source; set it to twice your frame rate. Confirm on the receiving end: the picture plays from the channel's HLS link.

The stream key rides on the command line, so anyone with a shell on the machine can read it in the ps listing; keep other accounts off the box. Load it from an environment file (mode 600) in your systemd unit rather than pasting it at a prompt; that keeps it out of history files and out of the unit itself.

Settings to copy

FFmpeg chooses the QSV rate-control mode from the combination of options you pass, not from one switch. Per its encoder documentation:

You passModeGood for
-b:v and an equal -maxrateCBRLive ingest that expects a steady rate
-b:v and a higher -maxrateVBRRecordings and on-demand files
-b:v with -look_ahead 1 (H.264)VBR with lookaheadMore quality per bit, with added delay
-global_quality from 1 to 51, 1 bestICQFiles whose size may vary
None of theseCQPRarely what a live job wants
  • -preset runs from veryfast to veryslow. Start at medium and move one step at a time while you watch speed=.
  • -g sets the distance between keyframes; -bf sets the number of B-frames.
  • -async_depth raises throughput at the cost of latency: more frames in flight before FFmpeg syncs.
  • -low_power selects the low-power encode path. Intel's tables give Broadwell none, so leave it off unless vainfo shows VAEntrypointEncSliceLP.

Which of our machines fits

Quick Sync needs physical Intel graphics, so this is work for a whole machine rather than a slice of one. Our dedicated servers in New York include two video encoder builds on Xeon E3 processors with Iris Pro graphics: the standard build, and a four-bay build with more memory, four drives and a 10 Gbps port. The box is single-tenant, with full root access and your choice of Linux distribution or Windows, ready in about 30 minutes. The port is unmetered: a relay running all day brings no per-gigabyte bill.

Take the four-bay build when recording or a library shares the machine. For one camera feed in front of viewers you may need no encoder server: one of our live video channels accepts an RTMP push from OBS, vMix or Wirecast, then serves it to browsers as HLS. Our cloud servers list vCPU, memory and SSD with no graphics engine, so keep Quick Sync on the encoder builds.

Keeping it on air

  • Run the relay under systemd with Restart=on-failure; systemctl enable --now launches it immediately and again at every boot.
  • Leave SSH as the only open inbound port. With ufw, allow SSH first (sudo ufw allow OpenSSH), check that /etc/default/ufw holds IPV6=yes so the IPv6 side gets the same rules, then sudo ufw enable.
  • After any kernel, driver or FFmpeg update, rerun vainfo and the null test before the next broadcast.
  • Watch speed= in the journal: under 1x means the relay is falling behind real time.

When it goes wrong

  • No node under /dev/dri. The graphics are invisible to the operating system and no FFmpeg flag will help. Open a support ticket with the output of lspci and ls -l /dev/dri.
  • vainfo loads the wrong driver or cannot start. Run LIBVA_DRIVER_NAME=iHD vainfo. If that works, set the same variable in your service's environment.
  • vainfo lists decode only. The free-kernel driver is in place; install intel-media-va-driver-non-free.
  • h264_qsv will not open while vainfo looks right. The runtime is the usual gap: confirm libmfx1 is installed.
  • hevc_qsv refuses on Broadwell. Expected: that generation has no HEVC encoder. Use h264_qsv.
  • Frames do not stay on the graphics. -hwaccel qsv keeps them there only when decoder and encoder are both QSV and no filters run; a scaling relay decodes in software.

Honest limits

  • 4096 x 4096 is the largest frame these generations encode in Intel's tables.
  • No HEVC 10-bit, VP9 or AV1 encode. If a destination demands AV1, this is the wrong chip.
  • The Media SDK runtime is archived. New Intel media features land in the oneVPL GPU runtime, which starts at Tiger Lake.
  • For an archive where file size matters more than speed, compare against a software encoder on your own footage first.

Questions people ask

Do I need a separate graphics card to use Quick Sync?

No. Quick Sync is part of the graphics built into the Intel processor, so there is no card to add. The video encoder builds transcode on the processor's own Iris Pro graphics; you only need the driver and runtime described above.

Can I use VA-API encoders instead of the qsv ones?

Yes. FFmpeg also ships h264_vaapi, which drives the same iHD driver through VA-API with no Media SDK runtime in between. It is a sensible fallback if the runtime gives trouble.

How many live streams can one machine encode?

There is no fixed number: it depends on resolution, frame rate, preset and the scaling and audio work on the processor. Measure it: add relays one at a time and stop when speed= on any of them nears 1x.

Does this work on Windows as well as Linux?

FFmpeg supports QSV on Windows through a D3D11 or DXVA2 child device, while on Linux it uses VA-API. When you order a dedicated machine you can pick Windows instead of a Linux distribution. Check that Intel's Windows graphics driver supports your exact processor before you choose that route.

Can I try the receiving side before ordering a server?

Yes. Live video has a free plan, so you can open a channel and push to it from FFmpeg on any machine you already have. When the picture and settings are right, move the same command to an encoder server.

Dedicated

Put your encoder on air

Pick a video encoder build, choose Ubuntu 24.04, and run the vainfo and null-output checks the moment it is ready.