Price the playback job as a complete deliverable
A media-server quotation depends on what the system must show and how the event will be operated. The same physical screens can require a simple prepared loop or a programme with many cues, live inputs, mapped content and late changes. Those projects may involve different hardware, software and preparation even when the event duration is identical.
Start with an output plan, representative content and a running order. Ask the supplier to distinguish the equipment allocation from programming, testing, rehearsal and event operation. A daily machine figure is useful only when the rest of the scope is clear.
Where the budget comes from
| Budget area | What influences the scope | What to ask for |
|---|---|---|
| Computers and output hardware | Independent pictures, resolution, simultaneous layers and live inputs | The proposed configuration and which outputs it provides |
| Software and licenses | Platform, enabled outputs, features and third-party content engines | Required entitlements included for the agreed show and dates |
| Content preparation | Conversions, file organisation, mapping and checking supplied assets | Deliverables and responsibility for unsuitable or late files |
| Show programming | Cues, transitions, control integration and alternative running orders | The programmed sequence and review process |
| On-site setup and rehearsal | Alignment, source testing, available venue time and rehearsal scope | Hours or sessions covered and the expected content readiness |
| Operation and fallback | Operator attendance, programme changes and prepared backup paths | Named responsibilities and the agreed recovery capability |
| Logistics | Transport, installation location, access and collection | What is included across the complete event schedule |
Not every project needs every item separately. The point is to make the deliverable visible. If the supplier bundles some work, ask for the boundary of that bundle rather than insist on an artificial line-by-line split.
Software scope can matter as much as hardware
Software licenses can affect the outputs and features available to a configured system. For example, Disguise's X Series documentation distinguishes output entitlements and states that Notch playback licensing is separate. This is a specific platform example, not a universal pricing model. Ask the supplier to verify the entitlements needed by the actual show, including any backup configuration.
Preparation may also include tasks beyond loading files. Disguise Designer describes mapping, timeline sequencing and control integration as parts of its workflow. If the brief needs those results, someone must build and test them. Clarify whether the creative agency supplies finished output-ready content or expects the playback team to adapt it.
Hypothetical example: the same three screens, two different shows
Imagine three displays with the same positions and image dimensions for two proposed events. Show A uses a fixed synchronised film that repeats throughout the opening period. Show B uses those displays for an opening sequence, speaker slides, several independently triggered films and live changes between presentation sections.
For Show A, the comparison focuses on the tested playback arrangement, content mapping, looping behaviour, start-up and recovery. Show B also needs a clear source plan, cue programming or switching workflow, rehearsal of transitions and an operator's role during the programme. The final design may distribute these functions across a server and other devices.
A useful request asks the supplier to price each show against its own defined scope. Do not take Show A's machine rental and assume the additional Show B work is included. Equally, do not require the same elaborate control workflow for a loop if it adds no value to the agreed audience experience.
Identify changes that create work
A replacement file with the same tested format and duration may be a different task from a replacement that changes timing, geometry, soundtrack or control behaviour. Adding a live camera introduces another source path to plan and rehearse. Changing a screen layout can affect both content preparation and outputs.
Agree who accepts revisions, the content delivery dates and how additional work is confirmed. Ask what the quotation assumes will already be finished when the operator arrives. A programme that is still being assembled during rehearsal may consume time intended for testing the final system.
Compare fallbacks by capability
“Backup included” can mean a spare file, another source device, a configured spare server or a more extensive failover arrangement. Ask what the audience can continue seeing after the specific failure you are planning for, and who performs the changeover. Compare proposals using that recovery requirement, rather than simply counting spare computers.
Also clarify what is handed over after the event: approved media, project files, a cue list or only the performed service. Do not assume editable projects or third-party licenses transfer to the client; agree the deliverables that are actually needed.
Before requesting a firm quotation
List every independent picture, live source and control action.
Supply a sample asset and a realistic running order.
State content deadlines, rehearsal access and event operating times.
Separate creative production, playback adaptation and show operation responsibilities.
Define the fallback and the final deliverables.
Bring that scope to technical support when planning control computers or a complete equipment rental. A comparable quotation describes the prepared, operated show you need.
Further reading
Disguise X Series licensing features and Designer workflow capabilities illustrate software and preparation scope. They do not establish local rental rates.