GPU video processing on NVIDIA — SolusTV V2

01 — nvidia

Built for NVIDIA, and only NVIDIA

We support NVIDIA cards and nothing else. That is a deliberate choice, not a gap: supporting one vendor properly means we can encode on CUDA, tune against real NVIDIA behaviour, and tell you exactly what a given card will carry — instead of shipping a lowest-common-denominator path across three vendors and hoping.

nvidia only cuda tuned, not generic
See what's included →
// supported
vendor   nvidia
compute  cuda

// not supported
others   by design

one vendor, done properly

02 — capacity

Unlimited GPU servers

There is no licence limit on how many GPU servers you run, and no per-card surcharge waiting for you at the point you start growing. Adding encoding capacity is a hardware decision and nothing else — buy the card, attach the machine, and the panel picks it up.

unlimited gpu servers no per-card fee add as you grow
See what's included →
// gpu servers on your licence Unlimited no cap, no per-card charge

scaling  attach a machine, it joins

03 — encoding

One input, every resolution at once

A single incoming channel is encoded into several resolutions simultaneously on the card. The viewer on a phone over mobile data and the viewer on fibre are both served properly from the same source, without you running the same channel several times over.

one input multiple resolutions simultaneous
How it's set up →
// one incoming source
input   1

// encoded at the same time
high    fibre
medium  most viewers
low     mobile data

on      cuda

04 — installation

Drivers and DKMS installed for you

The part that costs operators a weekend is never the encoding — it's getting the driver and DKMS onto the machine and keeping them there through a kernel update. SolusTV sets both up automatically when you add a GPU server. You attach the hardware; you don't become the person who maintains its driver stack.

driver auto setup dkms handled survives kernel updates
What else is automatic →
// adding a gpu server
driver   installed automatically
dkms     configured automatically
kernel   rebuilt on update

// what you do
you      attach the machine

05 — driver versions

Any driver version, old card or new

We work against any NVIDIA driver version rather than pinning you to one. That matters more than it sounds: it means an older card you already own doesn't become unusable, and a card you buy next year doesn't have to wait for us to catch up before you can put it to work.

any driver version older cards keep working new cards work now
Ask about your cards →
// driver support
version  any
pinned   no

old card  still usable
new card  no waiting on us

06 — presets and branding

Configure it once, reuse it everywhere

Save the qualities, the logo overlay and the access rules for a type of channel as a preset. A new channel becomes picking from a list rather than filling in a form — and you can put your own logo on any channel, or take an existing one off a source you brought in.

reusable presets add your logo remove a source logo access rules
See presets →
// one preset, many channels
qualities  ladder
logo      yours, overlaid
source    existing logo removed
access    who can reach it

applied to every channel of that type
01 / 06
Several qualities at once

Stop losing the viewer with the worst connection

If a channel exists in one quality only, you're choosing between viewers who can't play it and viewers who deserve better. Converting a source into several qualities at the same time removes that choice — every viewer is served the one that suits the connection they actually have.

Ask how it's set up

// one incoming source
source  →

// several outputs, at the same time
best quality  fast connection
standard     most viewers
lower        slow or mobile

// each one carrying
logo    yours
preset  reused across channels
Branding

Your name on the picture, not theirs

Two small controls that change how the service looks to a customer. You can add your own logo to any channel, and you can remove one that arrived on a source you brought in.

  • Add your logo to any channel, so your brand is on the screen rather than in the app menu.
  • Remove an existing logo from a source, so nothing you didn't choose ends up in front of your customers.
  • Applied through presets, so it's a decision you make once and reuse.
  • Part of the picture — it doesn't depend on what the customer's player supports.
Processing preset reusable
quality ladder logo overlay source logo removed access rules
Graphics hardware in use
load58%
memory44%
channels71%

Illustrative. Live figures come from your own servers.

Presets

A new channel takes seconds, not an afternoon

The settings that decide how a channel is processed are saved and reused. That's the difference between adding a channel and configuring one.

01 Set it up once

Decide the qualities, the logo and the access rules for a type of channel.

02 Save it as a preset

Those decisions become something you can pick from a list.

03 Apply it

Every new channel of that type gets the same treatment, without repeating the work.

04 Change it later

Adjust the preset when your requirements move, rather than editing channels one by one.

Questions

What owners ask about it

Why does processing on graphics hardware matter to me?
Because it decides your costs. Converting video is the heaviest work the platform does, and doing it on graphics hardware is far faster and cheaper than doing it on a general processor. In practice that means more channels per machine, and fewer machines for the same line-up.
Do I have to convert every channel?
No. Processing is applied per channel, through the presets you choose. Channels you're happy to pass through untouched can stay that way.
Can I control who gets the processed version?
Yes. You decide which viewers and which resellers can reach a processed channel, so it stays inside the packages you intended.
What hardware do I need?
That depends on your line-up and how much of it you convert. Tell us what you're running today and we'll talk it through properly rather than publishing a number that won't match your situation.

Work out what your line-up would need

The useful conversation here is about your channels and your hardware, not a specification sheet. Tell us what you run and we'll go through it with you.