Conform · Localisation · Hand-off
We take a completed programme and turn it into the exact set of files a regional distributor is contractually able to accept — then hand it over to whichever delivery network that distributor already pays for.
Almost nobody has a problem making the programme. The problem starts the moment the same programme has to exist in nine slightly different versions.
A regional broadcaster wants a hard-subtitled version at one bitrate ladder. A streaming partner wants the same picture with separate subtitle sidecars, a different loudness target and a different naming convention. A third party wants a trimmed edit because two minutes of the programme cannot be shown in their market. Each of those is a small job. Twenty of them a week, scattered across three edit suites and a shared drive, is not a small job — it is a permanent background tax on people who were hired to make television.
The tax is usually invisible until a delivery is rejected. By then the deadline is tomorrow, the person who built the last package has left, and nobody can say with certainty which of the four files on the drive was the one that passed.
Masters arrive once, in whatever the production house produced. We conform picture and audio to the house reference, log the frame-accurate edit points, and register the programme so every later version is traceable to that single source.
Subtitle and caption assets, dub tracks, audio description, market trims and compliance edits are produced against the registered master — never against a previous export. Nothing is derived from a derivative.
Each recipient specification is a stored profile: container, ladder, loudness target, subtitle format, naming, sidecar metadata. Packaging is mechanical; QC is not. Both automated checks and an operator sign-off run before anything is released.
We are a preparation house, not a distributor and not a network operator. When a package is signed off, it is pushed to the storage or origin the customer nominates — their own object storage, their CDN provider's ingest, or a regional endpoint we operate on their behalf as a staging area. Everything downstream of that hand-off stays with the customer and their existing contracts.
This boundary is deliberate. Customers change delivery vendors regularly, for reasons that have nothing to do with the material. Keeping preparation independent of delivery means that switch is a configuration change on their side, not a re-encode on ours.
Where a customer has no suitable origin of their own, we operate plain
HTTP staging hosts close to the receiving side. They hold signed-off packages for the agreed
retention window and serve them to the customer's nominated delivery network. They are not
public catalogues and carry no consumer-facing service — ru-media.miramarta.com
is one such endpoint.
| Per-title preparation | Single programme or short run. Priced per finished minute against a named recipient specification. Suits pilots and one-off acquisitions. |
|---|---|
| Catalogue programme | Continuing preparation for a library. Monthly volume commitment, stored specification profiles, named operator, four-hour response during business hours. |
| Specification custody | We maintain the recipient specifications themselves — tracking changes announced by the receiving side and re-validating affected packages before they are rejected rather than after. |
Contracts run for twelve months with a ninety-day exit. Prepared material and the registered masters remain the customer's property throughout and are exported on request in the original form, without conversion fees.