Pixop Prime overview

Pixop Prime is a GPU appliance for real-time video enhancement over SRT. You receive a pre-built image — an AWS Marketplace AMI or a KVM QCOW2 — that already contains Amazon Linux 2023, the NVIDIA driver, Docker, TSDuck, and the Pixop LIVE container. You do not compile software on the appliance.

What the appliance does

SRT input (UDP 5000)
    → TSDuck ingress
    → Pixop LIVE (GPU enhancement / encode)
    → TSDuck egress
    → SRT output (UDP 5001)

Multicast hand-off between stages stays on the host (239.0.0.1). You only connect senders and receivers to the SRT listeners.

Deployment options

Path	You get	Licensing
AWS Marketplace quickstart	EC2 instance from the published AMI	Activated on first boot via AWS License Manager
KVM quickstart	QCOW2 on your hypervisor with GPU passthrough	JWT file you supply at install or while running (deployment guide, commissioning sheet)

Both paths run the same pipeline and the same operator tools under /opt/pixop/bin.

Version you are running

Check on the appliance:

pixop-version

Identifier	Where to read it	Use
Marketplace product version	AWS listing / subscription delivery details	Procurement and support tickets
AMI recipe	`pixop-version` on the guest (`AMI_VERSION`)	Feature surface, CLI helpers, transport class

Do not assume documentation describes your installed recipe. KVM and Marketplace deliveries can differ. Use pixop-version and your procurement record.

Operator surfaces

Surface	Purpose
SSH (`ec2-user`)	CLI tools, logs, commissioning
HTTP `:8080`	Pixop control UI and REST metrics
UDP `5000` / `5001`	Primary SRT ingest and egress listeners

After first boot, the usual commissioning path is:

pixop-version
pixop-license doctor          # AWS Marketplace only
pixop-preflight
pixop-stack status
tsduckctl credentials
connect SRT source
tsduckctl check main
pixop-flow --secs 5
pixopctl health
# When feed is stable and your build supports them (confirm with tsduckctl --help):
tsduckctl detect-video-pid main --secs 10   # report only
tsduckctl tune-latency main                 # report only; --apply only after review + change window
connect SRT receiver
tsduckctl check egress-main

Details: Connect your first SRT stream.

What is not on the appliance

No automatic docker pull on service start — images are digest-pinned at bake time.
No in-place OS or NVIDIA driver upgrades — those require a new qualified AMI or QCOW2 generation.
Digest-pinned container updates are supported via pixop-image-update when Pixop publishes a new image reference for your release line.