Broadcast file transcoder. GPU-accelerated.
Queue once, every format out together.
File Transcoder is Point Media Tech's broadcast file transcoder, batch-processing media with GPU hardware acceleration on a distributed architecture. Files arriving by watch folder or API, from IMF / MXF / ProRes to H.265 / AV1, go through one pipeline that outputs broadcast, OTT, and mobile formats in parallel.
100+Formats supported
×10Transcoding speed
GPUHardware accelerated
N×Linear scale-out
412 files queued,
and nobody is submitting them.
In the File Transcoder job queue, files arrive by watch folder or API and the scheduler places them across the GPU nodes. Small renditions finish long before the 4K one and are released as they complete, rather than waiting for the whole job.
From single-machine software encoding to distributed GPU clusters,
file transcoding becomes a scheduled, clustered job.
File Transcoder batch-converts high-resolution masters into playout, OTT, and mobile formats on a distributed GPU cluster. In the legacy workflow, producers drop masters into a shared folder, an operator queues each file into desktop transcoding software, and a one-hour show takes four hours to render. Every additional output target — broadcast MXF, OTT MP4, mobile H.265 — multiplies the wait. File Transcoder uses distributed scheduling, watch-folder triggers, and REST API integration with MAM and Inspector, so one enqueue produces every format in parallel. It fits archive digitisation, OTT delivery, and multi-platform distribution; real-time encoding of live signals is the job of the broadcast live encoder.
Single CPU, file-by-file, manual queueing
Transcoding software runs on an engineer's workstation; every output target is encoded again from scratch; queueing is manual; one bad job means another four-hour wait; overnight catch-up shifts are routine; throughput is capped by one machine.
GPU cluster, batch-driven, API-integrated
Distributed architecture with N-times linear scale-out; GPU hardware acceleration delivers 10x throughput; watch folders trigger jobs automatically; multi-target outputs run in parallel; REST API ties into MAM, Inspector, and Playout; overnight catch-up shifts disappear.
Today · One machine, one file at a time, in software
- Production drops files into a shared folder
- An engineer submits them one by one
- A one-hour programme takes four hours
- Multiple deliverables multiply that again
After · Batch transcoding on a distributed GPU cluster
- Watch folders trigger automatically
- Distributed scheduling, scaling linearly with nodes
- REST APIs connect MAM and Inspector
- Queue once, every format comes out together
Three layers, one continuous
batch transcoding pipeline.
Point Media Tech's File Transcoder has three capability layers: format coverage, GPU acceleration, and workflow automation. Each layer is independently sized, licensed by core count and concurrency, and extensible as you grow.
100+ format coverage · Format Coverage
Broadcast containers (IMF / MXF OP1a / OP-Atom / ProRes / DNxHD), web and mobile (MP4 / MOV / WebM), codecs (H.264 / H.265 / AV1 / VP9 / ProRes / DNxHR). Multiplexed audio tracks and subtitle channels are preserved end-to-end.
- IMF / MXF / ProRes / DNxHD
- H.264 / H.265 / AV1 / VP9
- Multi-track audio + subtitle channels
- HDR10 / Dolby Vision metadata
GPU cluster · Distributed GPU
NVIDIA NVENC / NVDEC hardware acceleration; multi-card parallelism; distributed job scheduling; automatic load balancing; node failure failover; N-times linear scale-out. From one card to a full GPU rack — the workflow stays the same.
- NVIDIA NVENC / NVDEC
- Multi-card parallelism · linear scale-out
- Distributed scheduling · load balancing
- Automatic node failover
Batch automation · Automation
Watch-folder triggers; REST API and webhooks; bidirectional integration with MAM / Video Inspector / Playout; batch priority controls; scheduled runs; one enqueue produces every output target in parallel and writes metadata back automatically.
- Watch-folder triggers
- REST API + webhooks
- MAM / Inspector / Playout integration
- Multi-target parallel output
Single machine, CPU
Single machine + GPU
GPU cluster (multi-node)
Node failure · picked up automatically
Transcoding is the bridge from post to playout —
one enqueue, every target, in parallel.
File Transcoder sits between post-production and playout, translating masters into every playout and distribution format. The process is automated, batch-driven, and fully auditable.
- SourceMAM / watch folder · high-res masters
- QueueDistributed scheduling · priority + concurrency
- GPUNVENC / NVDEC · 10x acceleration
- Multi-outBroadcast + OTT + mobile in parallel
- DeliverWrite back to MAM · push to Playout / CDN
Engineering specifications.
File Transcoder takes MXF, ProRes, DNxHD, and IMF masters and outputs broadcast, OTT (HLS / DASH), and mobile formats with NVIDIA NVENC / NVDEC acceleration. A full spec sheet and live engineering walkthrough are available on request, or download the technical whitepaper.
| Input formats | MXF (OP1a / OP-Atom) · ProRes · DNxHD / DNxHR · IMF · MP4 · MOV · MPEG-2 · H.264 / H.265 · AV1 |
|---|---|
| Output formats | Broadcast (MXF / IMF / ProRes) · OTT (HLS / DASH / MP4) · Mobile (H.265 / AV1 / WebM) · custom presets |
| Hardware acceleration | NVIDIA NVENC / NVDEC · multi-GPU parallelism · CUDA-accelerated filters · CPU fallback |
| Distributed architecture | Master-worker nodes · automatic load balancing · node failover · N-times linear scale-out (single host to cluster) |
| Automation & integration | Watch folders · REST API · webhooks · bidirectional MAM / Video Inspector / Playout |
| Audio & subtitles | Multi-channel (5.1 / 7.1 / Atmos pass-through) · CEA-608/708 · STL / SRT / TTML |
| Licensing | Licensed by transcoding cores and concurrent jobs; modular scaling; software license + annual maintenance |
Three steps, from evaluation to production.
Request a trial
Submit the contact form. Sales will respond within one business day to schedule a technical consultation.
Integration assessment
Our consultant reviews transcoding load, target formats, and integration with your existing MAM / Inspector / Playout to size the GPU cluster.
Deploy and go live
After GPU node deployment, preset configuration, and acceptance testing (including batch stress tests), we phase the rollout to keep your post-production running.
Frequently asked questions.
Which input and output formats does the File Transcoder broadcast file transcoder support?
File Transcoder takes IMF, MXF, ProRes, DNxHD, MP4, and MOV masters and outputs broadcast MXF, OTT HLS / DASH, and mobile H.265 / AV1. Codecs include H.264, H.265, AV1, and VP9; multi-channel audio and CEA-608/708 and TTML subtitle tracks are preserved, with 100+ formats supported overall.
How does File Transcoder shorten post-production turnaround compared with single-machine software transcoding?
File Transcoder replaces file-by-file transcoding on one machine with GPU acceleration and distributed scheduling, so every target format is queued once and output in parallel. Watch folders trigger jobs automatically, removing manual overnight catch-up; GPU-accelerated throughput is stated as more than 10x that of software-only transcoders.
Can File Transcoder integrate with our existing MAM and post-production workflow?
Yes. File Transcoder integrates bidirectionally with media asset management (MAM), Video Inspector automated file-based QC, and Playout through a REST API, webhooks, and watch folders. Finished jobs write metadata back to MAM and can be pushed to Playout or a CDN.
How is File Transcoder licensed?
File Transcoder is licensed by transcoding cores and concurrent jobs, with modular scaling. Licensing is software license plus annual maintenance; contact sales for a quote based on your batch transcoding requirements.
What hardware does File Transcoder need, and is a GPU required?
File Transcoder recommends NVIDIA GPUs (NVENC / NVDEC) for hardware acceleration, offers CPU fallback, and runs on Linux and Windows. Exact sizing depends on concurrent jobs and target formats, and a technical consultant will help size the GPU cluster.
What is the first step to evaluate File Transcoder?
The first step is to submit the contact form; sales responds within one business day to schedule a transcoding requirements review. Engineering teams can also download the File Transcoder technical whitepaper to evaluate on their own.
Ready to queue once
and get every format out together?
Book a demo to see a GPU cluster schedule your batch transcoding, or download the File Transcoder technical whitepaper for your engineering team.