Reviewed September 24, 2026 against source v1.7.41. Features and fixes are labeled by version. Check release availability.
Separate applications
SPECTER SDR and SPECTER Imaging install, license, update, and operate independently. Neither application requires the other.
Local event handoff
When Imaging is running, it creates an authenticated loopback receiver on the same computer. SPECTER SDR discovers that local contract and can forward qualified event notifications. Critical events can request an Imaging anomaly capture.
- Communication is limited to
127.0.0.1. - A random token is created for each Imaging run.
- Duplicate event identifiers are ignored.
- No cloud relay or hosted dependency is involved.
- If Imaging is closed, SDR continues normally without retry noise.
Verify operation
- Start SPECTER Imaging.
- Start SPECTER SDR on the same Windows account.
- Generate a qualified simulated event or hardware alert.
- Confirm the SDR alert appears in Imaging with matching label and frequency.
Which workflow is being recorded?
Do not treat a channel activity WAV, a radiation reading, and a class-qualified RF event as interchangeable. The activity recorder saves locally; enabling it is not a promise that every recording requests an Imaging capture. Verify the intended qualified-event handoff separately. The v1.7.41 event-clip changes do not make the two applications dependent on each other.