HyperDeck ISO Recorder 100G
HyperDeck ISO Recorder 100G: IP video and network recording
Ask GLMedia about rental options for event recording and monitoring. We review availability, configuration, and alternatives for your event.
Model and use
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.
HyperDeck ISO Recorder 100G records eight SMPTE-2110 video channels to ProRes files on network storage. It differs from HyperDeck systems with local media.
Preparing the system requires identifying sources and the recording destination. We can help compare an IP path with alternatives that retain existing connections.
Networks, sources, and files
- Video and storage
- Identify 100G IP video ports and storage ports: their roles differ. Also separate NMOS control, PTP reference, and management.
- SDI sources
- For SDI reception, the manufacturer proposes SDI Expander 8x12G. The recorder’s SDI monitoring connections are not camera inputs.
- Files
- Files are saved on network storage. Define folder, available space, required audio, and editing-system access.
What to prepare
Share how many sources need preservation, formats, duration, and later use. We can build an initial diagram before all equipment is selected.
Gather models of available switches, storage, and converters. Assign coordination of networking, recording, and editing access for a system rehearsal.
Basic preparation
- Identify model and firmware and draw separate video, storage, clock, control, and management paths.
- Check formats and source mapping. Identify modules and cables before finalizing topology.
- Check reference and PTP Lock status; if using NMOS, verify that intended sources and destinations are identified.
- Choose the recording destination and appropriate ProRes quality. Prepare a test with the planned source count and load.
- Record a sample with identifiable audio per source. Check files, duration, and temporal correspondence in the editor.
- Test simultaneous recording and editing access when required for the service. Record results and backup preparation.
Technical questions and show decisions
- Can the SDI monitor connections be used as camera recording inputs?
- Why does a network link not establish successful recording?
- Do redundant links provide two copies of recorded files?
- Should my show record the finished program or keep each camera separately?
- How do I plan material delivery and backup before the event?
Can the SDI monitor connections be used as camera recording inputs?
Those connections are outputs. For SDI sources, prepare documented conversion and verify models, formats, and the complete path.
Share camera connections and the intended destination; we can organize options before choosing an expander or network.
Why does a network link not establish successful recording?
Separate incoming video, synchronization, and storage access. Check received source, clock status, and destination folder before testing a file.
A recording and readback test with the planned load checks the complete system. Preserve per-source results to locate an unresponsive segment.
Do redundant links provide two copies of recorded files?
SMPTE 2022-7 redundancy protects IP video transport. File copies and storage recovery must be prepared separately.
Agree on retained media and the second copy’s location. Test access before relying on that backup.
Should my show record the finished program or keep each camera separately?
If you need to review or deliver what went on air, plan a program recording. If a new edit follows, separate camera recordings allow different shot choices. We can assess both paths and agree the audio needed for each deliverable.
Source count, duration, chosen quality, and editing deadline guide the proposal. Compare centralized IP recording with alternatives retaining existing connections. Separate camera recordings do not automatically create a finished edit: production, selection, and postproduction are defined service tasks.
How do I plan material delivery and backup before the event?
Agree sources, format, audio, file names, storage destination, and recipient. Use planned duration and quality to size storage and run a representative recording-and-reading test; if editing and recording share storage, include that load in rehearsal.
Operation, file checks, copying, and delivery can be included in the agreed scope. Define each copy’s location and when its readability is checked. Editor access to storage does not create a second independent copy; backup and recording continuity are planned separately.
Checks by symptom
| Symptom | Check | What it helps distinguish |
|---|---|---|
| Missing source | Video path, format, and reference. | Reception or synchronization. |
| Video visible, no file | Destination, access, and recording test. | Storage or recording. |
| Editor cannot find media | Shared folder and per-source files. | Access or location. |
Limits and precautions
Preserve configuration and media before updating or reorganizing storage. Schedule network changes outside operation.
If IP10 is used, both ends must support the mode; do not confuse it with the files’ ProRes format.
Keep ventilation clear and verify system power and redundancy against documentation. Redundant links do not replace recovery rehearsal.
Official documentation
- Product and overall workflow
- Exact-model specifications
- Official SMPTE-2110 settings guide
- Official menu and status guide
Verify firmware and system documentation before advanced setup.
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.