Recording guide
Program, ISO, and independent recording copies
Ask GLMedia how to record your event: a finished program, sources for editing, and an additional capture based on audio, duration, and operation.
Define the files you need
With the date, location, and intended use, we can review which equipment and combination can be offered. You can inquire before measurements, drawings, or the final schedule are ready.
Program recording preserves the selected live output. ISO recording preserves separate source feeds where the exact system and mode support it. Another recording path and a later file copy address different risks.
We can help plan from the intended delivery: a record of the event, an edited version, separate camera sources, or material for later review. You can start before the final camera list is ready.
Program, sources, and protection
- Program
- Define picture, graphics, and audio mix that should be recorded. Identify the exact output feeding the recorder.
- ISO
- Specify which sources and audio tracks are needed for editing. Check availability and formats on the actual system rather than relying on the word ISO.
- Additional protection
- Trace another capture path and later file copies separately. Record which sources, devices, storage, and power stages they share.
What to share
Tell us the intended use, required files, delivery format, and deadline. We can compare a program-only plan with one that retains separate sources.
Describe cameras, sound, graphics, remote participation, and expected event duration. Include whether post-production needs matching timing across recordings.
Share planned recorders and media, if known. We can identify the format, storage, and playback checks still needed.
For the proposal, share the date, venue, approximate session lengths, and who will receive the material. Tell us whether you need ready-to-watch content, editing flexibility, or coverage for a particular interruption; a final equipment list can come later.
Preparing the comparison
- Write the required deliverables before selecting recording devices or outputs. Include audio tracks and whether graphics should be visible.
- Confirm exact recording model, input, format, codec, and media support. Preserve starting settings and a known usable version of the plan.
- Record a representative segment with speech, slides, motion, video playback, and source changes. Watch for warnings during the test.
- Play the recorded file back and check beginning, middle, and end with audio. Review duration, framing, graphics, and the tracks that editing needs.
- For separate source recordings, test the intended synchronization and identify any missing or different source timing before the event.
- After recording, make the agreed file copies and check them before reusing media. Treat another capture path as a separate test, including what it shares with the primary path.
- List each deliverable’s picture, accompanying audio, program segment, and person checking the file. If requesting another capture, map its shared stages with the primary path before assessing which interruption it could cover.
Technical questions and show decisions
Does ISO recording automatically replace program recording?
They serve different delivery needs. Confirm whether the plan captures the live mix as well as the source files, and what audio accompanies each.
We can compare a short recorded sample with the expected deliverables before committing the recording plan.
Is another file on the same device an independent backup?
Trace the shared stages. The files may still depend on the same input, recorder, medium, or power. A later copy cannot capture a moment that was never recorded.
Describe the interruption you need to cover. We can compare another capture route with a copy process and test the selected approach.
The recording indicator was active. Is the file ready to deliver?
Inspect and play the actual files. Confirm video, audio, duration, and any warnings rather than inferring success from the indicator alone.
For the documented HyperDeck workflow, recording can include camera overlays already present in the feed. Check the source and recorded sample before promising a clean image.
What should we request for an edited recap while also keeping the full talk or show?
These are different deliverables to define before recording. For the full record, agree program segments, picture, graphics, and audio, including questions or videos where relevant. For the recap, identify sources, moments, and sound needed for editing; if separate cameras are required, verify how the selected system records them.
Compare recording and file handover with a proposal adding selection, editing, review, and final versions. Agree recipient, format, copies, and timing around duration and footage volume. ISO recording does not create the recap by itself, and copying files does not replace another capture path; these tasks and paths are prepared and checked separately.
Checks to guide decisions
| Symptom | Check | What it helps distinguish |
|---|---|---|
| Program exists, separate source absent | Exact ISO mode and resulting files. | Recording scope. |
| Picture correct, audio wrong | Recorded tracks and mix. | Audio delivery. |
| Warning or incomplete file | Mode, media, and playback test. | Recording performance. |
| Copy repeats the same problem | Shared capture stages. | Protection scope. |
Installation and limits
Do not format or reuse media until the required material has been preserved and checked. Identify the actual medium before any destructive operation.
Test changes outside the live program. Keep working configurations and record what was tested rather than applying a generic reset or firmware change.
Agree file naming, handover, and verification with the receiving team. Keep recording, copying, review, and delivery as separately checked steps.
Sources and context
- Blackmagic Design: recording by Television Studio model
- Blackmagic Design: HyperDeck model specifications
- Blackmagic Design: HyperDeck manual, relevant recording and media sections
Research reused from records consulted October 22, 2026. Recording capabilities and storage depend on model, firmware, and mode. No physical recording or file delivery has been performed.
Help us improve this guide
Is an explanation missing, did you find an error, or did you solve something differently? Tell us on WhatsApp.
WhatsApp opens with an editable draft. Review it and send it if you choose. Do not include passwords, keys or client information. Contributions are reviewed before being added to guides; they are not published automatically.