Hollyland Pyro S

Check the camera’s output signal and the receiver’s output, not just the camera’s recording format. On Pyro S, HDMI supports 3840 × 2160 up to 30p, while SDI operates in HD. An SDI PsF input may also emerge as p or i depending on its rate. Compare the signal path with the format table before changing cables or settings.

1. Read Resolution & Frame Rate on TX and RX and note whether each end uses HDMI or SDI. Check camera → TX and RX → switcher connections: TX receives video, RX outputs it. Save the original camera and destination formats.
2. If TX shows No Video, Hollyland recommends connecting the camera directly to a monitor to check the source and cable. If that also fails, check the output against the exact camera manual. If the direct connection works, test TX with a known working HDMI source in a supported format. Seeing the format on TX confirms input detection; the output still needs checking.
3. Once TX detects video, check the RX group and connection, then connect its output to a compatible monitor. If that has a picture but the switcher does not, check the final cable and the format accepted by that input. For example, the guide maps SDI 1080PsF25 to 1080i50 at the Pyro S outputs; do not record it as 1080p25. For a different format, prepare a documented camera output or converter and test again.
4. An HDMI 3840 × 2160p25 input retains that format at RX HDMI and produces 1080p25 at SDI. This documented conversion does not allow arbitrary frame-rate or resolution changes. Before feeding HDMI to an ATEM Mini Pro, also check its supported formats and test the actual combination.
5. Test the complete path with moving content and audio, first nearby and then at the event position. Record where the picture appears and where it disappears, changing one variable at a time. If the direct cable works and the wireless path does not, keep that alternative available for production and continue troubleshooting off program.

Compare against a direct connection and check whether RX still receives motion. A static picture can be the last frame retained by Frozen Frame after an interruption; a displayed image does not prove the link is active. If motion continues but detail is reduced, check Scene Mode and compare results before treating it as a camera fault.

1. During rehearsal, compare the same scene over cable and wireless using the same monitor and framing. Note output format, detail, motion, delay and connection status. In TX Scene Mode, HD Mode prioritizes detail at up to 12 Mb/s; Smooth Mode adjusts quality to maintain lower delay under interference. Test both along the intended route and record the differences. Neither guarantees enough detail for critical focus nor removes the delay of the entire chain.
2. For blocking or dropouts, first check stable power, fitted antennas and the signal path. The FAQ specifies DC or NP-F: USB-C cannot power these units. On RX, use Frequency Scan to inspect occupancy and choose a channel, or check AUTO/Auto Frequency Hopping against the guide. Do this during rehearsal because a channel change can interrupt video. Repeat along the operating route under expected conditions; improvement close to the stage does not prove coverage everywhere.
3. If pairing fails, check Group Pairing and the group on both units. The FAQ recommends at least 1 m between TX and RX for this check. Hold Confirm/Menu for three seconds and read Version Information on each unit. Record H100 or H110 revision before assessing firmware. V1.0.5.6 release notes warn about pairing upgraded and non-upgraded units. Prepare any update with the official file and sequence for that exact revision, saved settings and time to test; do not update during the event.
4. Agree how the team will detect and cover an interruption with Frozen Frame enabled. Use visible motion as a reference and check RX status, not just the presence of a picture. Test return to program and a backup path with the actual equipment. If degradation persists after comparing modes, channel and power, record results for support and assess another path for that function. A low-latency claim does not make an inadequate picture suitable for focus or IMAG.