Ask · Share · Build

Posting Waterfalls and I/Q Recordings Safely

Pavel

SDRstore_Pavel
Administrator
Staff member
Joined
Jul 30, 2026
Messages
121
Short answer: Share the smallest technical sample needed, with frequency, sample rate, format and settings, after removing private content, coordinates, identifiers and file metadata. A waterfall image is easier to sanitize; I/Q can contain every signal inside its captured bandwidth.

Before you start​

  • Use the most specific forum and write a title that names the device, software, signal or exact error.
  • Remove order numbers, addresses, phone numbers, tracking numbers, account details, credentials and precise private locations before posting.

Step-by-step method​

  1. Step 1: Crop the waterfall to the relevant time and band while preserving scale, center frequency, bandwidth and UTC context needed for analysis.
  2. Step 2: For I/Q, record a short nonclipped segment and document complex format, endianness, sample rate, center frequency and frequency correction.
  3. Step 3: Review what else falls inside the bandwidth, including voice, identifiers and private digital traffic. Do not upload if safe redaction would require altering the signal itself.
  4. Step 4: Remove EXIF, paths, hostnames, coordinates and account information, then reopen the final exported file and inspect it before posting.

Concrete example​

A 20-second, 2 MSPS complex recording around an unknown narrow signal may also contain 2 MHz of nearby spectrum. Check the entire span and choose a narrower safe recording when possible.

How to judge the result​

The upload is useful when another member can reproduce the signal display from documented metadata and no unrelated private information remains.

What to record​

  • A useful question lets another member reproduce the problem from the hardware, software version, settings and exact result supplied.
  • Mark a verified fix as the solution so future readers can reach it directly.
  • Edit the first post when a confirmed correction changes the instructions or compatibility information.

Common mistakes​

  • Using a vague title or omitting the details another member needs to reproduce the question, guide or result.
  • Posting private information first and expecting it to be removed later; public copies, notifications and downloads may already exist.
  • Blurring a screenshot does not sanitize the original baseband file or metadata attached separately.

Final check​

Read the post once as a stranger: its forum, title, prefix and evidence should be clear, while personal data, credentials, precise private locations and protected content are absent.
 
Top