Expert-verified device compatibility records · 13 verified
Focusrite Scarlett 18i20 4th Gen ↔ Hegel H95: port-level class analysis found a damaging path. OVERVOLTAGE: amplified speaker-level output into a mic-level input will damage the input stage. OVERVOLTAGE: amplified speaker-level output into a line-level input will damage the input stage. LEVEL/IMPEDANCE: headphone output into a line input — the headphone amp is driving a bridging input instead of the low-impedance load it is designed for, so set its volume control well below maximum and check for level and distortion at the input. OVERVOLTAGE: amplified speaker-level output into a instrument-level input will damage the input stage. A class-matched path does exist (Hegel H95 Preamp output → Focusrite Scarlett 18i20 4th Gen Line Inputs 1-8; Hegel H95 Headphone output → Focusrite Scarlett 18i20 4th Gen Line Inputs 1-8; Focusrite Scarlett 18i20 4th Gen Line Outputs 1-10 → Hegel H95 Line inputs; Focusrite Scarlett 18i20 4th Gen Headphone Outputs 1-2 → Hegel H95 Line inputs; Focusrite Scarlett 18i20 4th Gen S/PDIF Out → Hegel H95 Coaxial digital input), so the pair is conditional — but the flagged path must never be used. Auto-generated draft — requires expert verification. UNDECIDABLE — Focusrite Scarlett 18i20 4th Gen USB → Hegel H95 USB-B: missing data (USB (USB host/device role not recorded — connector USB-C does not determine it)). No verdict for this hop until it is sourced.
One analog audio path: TeamConnect Ceiling 2 Analog Out into one of the TesiraFORTÉ AVB VT4's Mic/Line In (AEC) channels, over balanced shielded twisted pair terminated on screw-terminal blocks at both ends. The TCC2's analog output level and its own onboard processing are commissioning settings made in Sennheiser Control Cockpit, not fixed properties of the device: the level is set to match the Tesira input, and the TCC2 processing is set together with the Tesira AEC. The TCC2's Dante ports cannot reach the VT4's AVB port without a Dante-to-AVB format converter, which is why the digital path is not the one used here. The Ethernet link carries control only, no audio.
Biamp Tesira FORTE DAN CI and Genelec 8030C share no network protocol; the direct signal path found is: Biamp Tesira FORTE DAN CI outputs 1-8 → Genelec 8030C INPUT (audio_analog). Auto-generated draft — requires expert verification.
Moog Mother-32 rear AUDIO OUT → Focusrite Scarlett 18i20 4th Gen Instrument Inputs 1–2, over a standard unbalanced 1/4" TS instrument cable. The Scarlett's instrument inputs are specified at 12 dBu maximum into 1 MΩ — a high-impedance input built for pickups and synth outputs, so the Mother-32's source impedance is not a concern. The level is, and for an unusual reason: Moog does not publish one. The Mother-32 has two audio outputs — the rear AUDIO OUT jack and the patchbay's own output jacks — and a single VOLUME control sets the level at both (User Manual p.16). For the patchbay outputs Moog states roughly ±5 V, about +11 dBV or +13.2 dBu, which sits at or just above the Scarlett instrument input's stated 12 dBu ceiling: at full VOLUME that path can clip the input stage. Moog publishes a peak output level of +/-1.7 V for the rear-panel 1/4" Headphone/Audio Output, equivalent to 1.202 Vrms (+3.8 dBu). This is a peak maximum, not a stated nominal operating level; Moog publishes no nominal. So one knob drives two outputs, and only one of them has a number attached. Nothing here is destructive — a 1 MΩ input is not at risk from either jack — but gain structure cannot be verified from the documentation. Start with VOLUME low, bring it up watching the Scarlett's meters, and do not assume the rear jack behaves like the patchbay figure. The MIDI route is separate and unremarkable: Scarlett MIDI Out → Mother-32 MIDI IN, 5-pin DIN, control data only.
Focusrite Scarlett 18i20 4th Gen Line Outputs 1–10 → Genelec 8030C INPUT. Both ends are balanced analog line level with published electrical figures on both sides. The Scarlett's line outputs deliver up to +16 dBu from a 200 Ω source; the 8030C's INPUT is XLR-F balanced at 10 kΩ, where −6 dBu produces 100 dB SPL at 1 m. Source impedance sits two decades below the load, so there is no loading concern. The level relationship is the thing to get right: the interface can deliver roughly 22 dB above the monitor's reference, so trim at the monitor (−12 dB, continuously variable) and set operating level at the interface. Use a balanced TRS→XLR cable — a TS cable makes this an unbalanced feed, which the 8030C manual permits only if pin 3 is grounded to pin 1 at the source, and that condition is not covered by this record. Each 8030C presents one mono input, so a stereo pair is two units and two cables.
Codec HDMI Out 1 is an HDMI 2.0 output; the AC-EX70-UHD TX takes HDMI 2.0 in. Direct HDMI jumper, no conversion needed.
The AC-EX70-UHD RX outputs HDMI 2.0, which the Samsung HDMI In 1 accepts. Direct HDMI jumper, no conversion needed.
Both devices speak HDMI video: Codec Pro G2 HDMI Out 1 → Samsung HDMI In 1 is a direct, valid video link with no intermediate device required. Two codec-side constraints apply: HDCP 2.3 / 4K60 on Out 1, and Out 2 going dark if Out 1 runs at 5K or above. The Samsung is now protocols_verified against its datasheet; the open question is narrower — HDCP revision and exact input complement vary by model revision and are not stated in the Business TV datasheet. Cable reach is a site condition and is recorded as a gotcha, not as a property of this pair.
Two valid connection paths, both recorded. IP path: one Cat cable to a codec PoE port carries video-over-IP, control and PoE+ power (802.3at Class 2, 42.5–57V / 0.5–0.4A), drawing from the shared 120W budget. HDMI path: HDMI 2.0 out into a codec HDMI input, which requires the combined wall/ceiling mount sold for HDMI+IP deployments. Where the PoE budget is already spent, the CS-PWR-INJ-30W injector powers the camera off-codec. Part number color suffixes (-L Arctic White, -C Carbon Black) are cosmetic only.
Datasheet C78-5735801-01 names the Ceiling Microphone Pro explicitly as a supported AV-over-IP peripheral on the Codec Pro G2 PoE ports. One Cat cable carries both audio-over-IP and power. The only real design constraint is the shared 120W PoE budget across all 8 ports, which must be summed for the whole room rather than validated per-port.
Barco CLICKSHARE CX-50 2ND GENERATION (protocols: Analog line-level, Dante, HDMI video) and Samsung The Frame (One Connect) (protocols: HDMI video, IP control) share HDMI video. Direct HDMI video connection is supported with no known constraints.
Biamp Tesira FORTE DAN CI outputs 1–8 → Hegel H95 line inputs. Biamp source: TESFDS-355-2010-EN-R1. Hegel source: H95 User Manual (Hegel Music Systems, Oslo), cross-checked against hegel.com — this replaces an earlier secondary source, a review reprint, and the three-optical/one-coaxial input split is now vendor-confirmed. The two devices share no network protocol: the Biamp carries Dante/AES67, the Hegel does not. The pair connects over analog line level only. This is conditional, not plainly compatible, because the two ends operate at different reference levels on different termination types. The Biamp's outputs are balanced Phoenix/Euroblock at a nominal +4 dBu professional level; the Hegel's line inputs are unbalanced RCA at a nominal −10 dBV consumer level. Feeding one into the other runs roughly 12 dB hot, and the unbalanced termination discards the balanced line's common-mode rejection — the noise immunity that makes a long pro run quiet in the first place. The pair works on these terms: pad the Biamp output or set its level to consumer reference rather than leaving it at professional reference; keep the cable run short, since an unbalanced run has no common-mode rejection to lose; and watch for ground-loop hum between chassis on separate earths, which is the usual failure mode when a rack-mounted DSP and a domestic integrated amplifier share a signal path but not a ground. Channel count is limited by physical I/O — verify counts against the design.
AtlasIED FS-D 4"/6" (Dante, AES67) and Audac M2 (Analog line-level, RS-232 control, IP control) have no shared protocol for direct connection. Expert verified.