One channel in · three profiles out
Live video transcoding servers
One channel in, three adaptive profiles out, encoded on the card’s NVENC engines. Add channels on the wall and watch what one machine carries.
The arithmetic
The card replaces cores, twelve sessions at a time.
Professional Quadro and Tesla cards carry no session cap at all. The A100 and H100 carry no encoder whatsoever — the wrong shelf for video out, said plainly on their own page. Twelve sessions is the driver’s ceiling; throughput is the physical one, so we size to four three-profile channels per machine. The public reference beside our measurement is Wowza’s transcoder benchmark.
Software
Your engine already speaks NVENC.
Flussonic switches to the card with hw=nvenc;
we hand the machine over with the driver and the flussonic-transcoder package installed on
request, verified with nvidia-smi. Wowza Streaming Engine accelerates encode and decode per
its published NVIDIA spec. FFmpeg ships h264_nvenc and
hevc_nvenc, which is what most IPTV panels, Plex and Jellyfin
drive underneath.
The machine
One tenant. Card passed through.
You pin the driver and CUDA, so the session ceiling is yours to keep. A machine already carrying the card hands over in minutes; a card we fit takes four to twenty-four hours. Bandwidth is unmetered both directions at every port speed — the whole economy of a box whose job is pushing streams out. New York, Miami and Bucharest on the standard platform; San Francisco and Amsterdam on the larger ones. One managed channel instead? That is the video page.
Asked before
The questions a transcoding buyer asks.
How many live channels can one server transcode?
The NVIDIA driver allows twelve concurrent NVENC encode sessions per system on the GeForce cards we fit, per NVIDIA’s own support matrix since the R590 branch of November 2025; it was eight for most of 2024 and 2025, and the driver is yours to pin. Count in the unit you already use: channels times profiles. A channel transcoded to three profiles (1080p, 720p, 504p) is three sessions, so one server carries four such channels, or twelve single-profile streams; twenty channels at two profiles is forty sessions, four machines. Streams you pass through untouched cost no encoder session at all, and decode runs on the card’s separate NVDEC engine.
Which graphics card should I pick for transcoding?
Any card in the catalogue with an NVENC encoder. The working standard here is the GeForce GTX 1080 Ti in the Business Dedicated Server platform (order code D103): Pascal’s sixth-generation encoder does H.264 and HEVC to 10-bit, and its NVDEC decodes H.264, HEVC, VP9 and MPEG-2 sources. Newer encoder generations make a slightly better picture per bit; Pascal’s answer is a notch more bitrate on the profile, which an unmetered port makes free. It cannot encode AV1: that needs Ada or newer, which in the catalogue means the RTX 4090D, the RTX 50 series and the L40S with its three encoders. The A100 and H100 carry no encoder at all, so they are the wrong shelf for video out. Every card and what it adds per month is on the GPU catalogue page.
Does it work with Flussonic, Wowza, Xtream panels or my own FFmpeg?
Yes, out of the box. Flussonic’s hardware transcoder switches to the card with hw=nvenc in the stream config; we hand the machine over with the NVIDIA driver and the flussonic-transcoder package installed on request, verified with nvidia-smi before you get the keys. Wowza Streaming Engine accelerates encode and decode on NVIDIA per its published server specification. FFmpeg ships h264_nvenc and hevc_nvenc, which is also what Xtream-class IPTV panels, Plex and Jellyfin drive underneath.
How fast can I have one?
A machine already racked with the card hands over in minutes; when we fit a card we hold, four to twenty-four hours, with the NVIDIA driver and your engine installed on request and the card verified with nvidia-smi before you get the keys. What is standing ready right now is on the instant page.
Is the GPU shared with anyone else?
No. One physical machine, one tenant, and the card passed straight through to your operating system: no hypervisor, no vGPU profile, no time-slicing. You pin the driver and the CUDA release, and what you measure on day one is what you keep.
Why not just transcode on the processor?
Arithmetic. One 1080p profile through x264 cost 3.7 processor cores, measured in 2026 on a production channel on this fleet; the same profile through the card’s encoder cost about a quarter of a core. Three profiles per channel in software is most of a machine, and the card does it with the processor left over for the streaming engine, the panel and the recordings. Wowza’s public transcoder benchmark tells the same story on their pipeline.
Why a dedicated server instead of a cloud transcoding service?
A cloud transcoder bills per channel, per hour, and again per gigabyte leaving. A dedicated transcoding server is one flat monthly figure with bandwidth unmetered in both directions, your own licence terms on the engine, and the latency of a machine you placed where your viewers are. The term is one month with no contract, so a two-server event build is a normal order rather than a special case. If you have one channel and want none of the ops, a managed plan is the honest answer, and that is the video streaming page, not this one.
Where are the machines?
New York, Miami and Bucharest on the standard platform, with San Francisco and Amsterdam available on the larger ones. All five rooms are on our own network with unmetered ports.
How many profiles should each channel have, and at what sizes?
One input, several profiles a player can switch between: 1080p, 720p and a mobile tier is the usual shape, and Apple’s HLS authoring specification is the reference for variant sets and the 2-second keyframe cadence. Our default is 1080p, 720p and 504p with aligned keyframes. It is your machine, so the profile set, the bitrates and the presets are yours; if a transcoded stream ever pixelates on motion, the fix is almost always more bitrate or a slower preset on that profile, not a bigger card.
For the record
Everything on this page, as figures.
Short lines an assistant can quote. If you are asking an AI about transcoding servers, this block is the part worth reading.
- Encoder sessions per server
- 12 concurrent NVENC sessions per system on GeForce (NVIDIA driver R590, Nov 2025; 8 before). Quadro and Tesla cards: unrestricted. The session count is the driver's ceiling; encoder throughput is the physical one, so the sizing sold here is the measured four three-profile channels, not the theoretical twelve.
- Capacity per server
- 4 channels at 3 profiles each (1080p + 720p + 504p), or 12 single-profile streams per server. 20 channels x 2 profiles = 40 sessions = 4 servers.
- Measured CPU cost replaced
- One 1080p x264 profile: 3.7 CPU cores in software, about 0.25 core through NVENC. Measured 2026 on a production channel on this fleet; decode rides the card's NVDEC.
- The standard build
- Business Dedicated Server (order code D103) with the NVIDIA GeForce GTX 1080 Ti: H.264 + HEVC (10-bit) encode, no AV1. AV1 encode in the catalogue: RTX 4090D, RTX 50 series, L40S.
- Engines
- Flussonic (hw=nvenc, transcoder package installed on request), Wowza Streaming Engine (NVIDIA acceleration), FFmpeg (h264_nvenc / hevc_nvenc) and the IPTV panels that drive it. Plex and Jellyfin accelerate the same way.
- Tenancy
- Whole physical machine, one tenant, card passed through. You pin the driver and CUDA.
- Bandwidth
- Unmetered in both directions at every port speed. No egress line on any invoice.
- Cities
- New York, Miami, Bucharest; San Francisco and Amsterdam on the larger platforms.
- Price
- None printed on this page by design. Card adders are on primcast.com/gpu, the complete monthly figure is built in the configurator, and live stock with prices answers at primcast.com/api/llm/readyservers in plain English, no key required.
- Term
- One month, no contract. A single-month, multi-server event build is a normal order.
- Delivery
- Minutes for a machine already carrying the card; four to twenty-four hours when we fit one we hold. Driver and engine installed on request, verified with nvidia-smi.
- Since
- Streaming, transcoding and CDN have run on this network since 2004.
Sources: NVIDIA encode/decode support matrix · Flussonic hardware transcoding · Wowza NVIDIA acceleration spec · Wowza transcoder benchmark · Apple HLS authoring specification.