PLAYBACK WORKFLOW · 5 MIN READ
HAP encoding: what to check before the show.
The file encoded successfully. That is the beginning of the playback test—not the end.
By ezav · Published 19 October 2026
For AV playback, the useful question is not simply “How do I convert to HAP?” It is “Will these files play together, on this machine, at the required frame rate?” Choose the delivery format with the playback operator, then test a representative section before converting the full package.
1. Choose the variant the player supports.
HAP prioritises a lower data rate. HAP Q improves image quality at a larger size. HAP Alpha carries transparency; HAP Q Alpha combines transparency with the higher-quality colour approach. HAP R is a newer option, but confirm encoder and player support before choosing it. The HAP format guide explains the variants.
Current ezav encoder supports HAP, HAP Q and HAP Alpha. It does not encode HAP R or HAP Q Alpha. A format appearing in a calculator does not mean every encoder or media server supports it.
2. Estimate the load, then measure a real encode.
Use resolution, frame rate and the number of different files playing at once. Two projectors showing the same server output do not necessarily mean two files must be decoded. A single large canvas should be entered at its complete pixel dimensions.
As a texture-payload baseline, 3840 × 2160 at 60 fps is about 248.8 MB/s for HAP and 497.7 MB/s for HAP Q, before secondary compression, audio and container overhead. Ten minutes at the latter baseline is approximately 298.6 GB in decimal units. These are calculated baselines, not predicted final MOV sizes.
Snappy compression changes the disk payload according to the content. Encode a busy representative section and measure it; do not assume a fixed saving for every clip. The HAP bitrate calculator separates the texture baseline from compression assumptions.
3. Keep frame rate and transparency deliberate.
Confirm the intended frame rate before export. 60 and 59.94 are different rates. Test motion and timing in the actual show configuration rather than relying on the file opening in a desktop player.
For transparent content, inspect the result over both light and dark backgrounds. Check edges as well as fully transparent areas. A source that has already lost its alpha channel cannot regain the original transparency by choosing HAP Alpha.
4. Test the full playback workload.
HAP moves texture data toward the graphics pipeline, but playback still involves reading, demuxing and decompression. A fast SSD alone cannot prove that the player, CPU, GPU and outputs can sustain the complete workload. The HAP developer overview describes that processing path.
Play all intended files together from the delivery drive. Include the highest-load section, cue transitions, loops and the required display outputs. Watch dropped-frame counters where the player provides them. Test long enough to expose problems that do not appear in a short preview.
Chunking can help particular decoding workloads; more chunks are not automatically better. Start with a supported setting and change one variable at a time. Record the player version, machine, storage, format and frame rate alongside the result so the test can be repeated.
5. Plan the transfer and handover.
For large media packages, consider a 10GbE transfer path when the sender, receiver and storage can use it. A 10Gbps switch alone will not accelerate a computer limited to a 1Gbps network adapter. The calculator estimates both link rates with an explicit efficiency assumption.
Deliver a clear filename, dimensions, frame rate, format, duration and file checksum with the media. A successful decode check helps catch an unreadable output; it does not certify smooth playback or synchronisation across machines.
This is a planning and test workflow. Results depend on the actual media, player and hardware.