aethersdr / aethersdr/AetherSDR
Hi Contrast/Optimized GUI for contesting
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 221
- Forks
- 117
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 299
Description
Request preparation
- I used an AI assistant to help structure this request
- I checked for existing issues covering the same feature
What would you like?
Subject: Feature Request: Streamlined Contest-Focused GUI Mode
Hi,
First, thank you for the work you've put into AetherSDR — it's a capable and feature-rich client for FlexRadio systems. That depth is genuinely impressive, and it's clear a lot of thought has gone into it.
That said, I'd like to make a case for an alternate GUI mode specifically designed for contest operating.
During a contest, operators are making contacts rapidly and continuously — sometimes hundreds per hour. In that environment, the current interface presents more information and controls than can be safely processed at a glance, and the layout isn't optimized for the narrow set of adjustments a contester actually needs to touch in the heat of a run.
What I'd love to see is a streamlined "Contest Mode" panel or alternate window layout that focuses on the essentials:
Panadapter/Waterfall is critical with Spot / Skimmer Input
Critical meters (always visible, large and readable):
- TX power output
- PA temperature
- Mic / audio input level
Fast-access controls (minimal clicks, ideally sliders or knobs), but not limited to:
- RF power
- RF gain
- AGC threshold (AGC-T)
- Audio / AF gain
- Filter bandwidth
Mode coverage:
- SSB (the primary contest mode)
- CW
- RTTY (increasingly common in digital contests)
Receiver / Signal:
S-meter (signal strength) - surprisingly critical for deciding whether to work a weak station or move on
NB (noise blanker) on/off and level - contest weekends and power line noise go hand in hand
NR (noise reduction) on/off and level
Transmit:
VOX on/off and delay (for SSB operators not using PTT footswitch)
MON (TX monitor/sidetone) level - important for CW ops to hear their own keying
Tune button / power level for antenna tuner cycles
Operating workflow:
Split operation indicator and easy VFO A/B swap - essential for working DX running split during contests
RIT (receiver incremental tuning) display and clear button - you drift it, you need to reset it fast
Band and mode display (obvious but needs to be prominent)
CW speed (WPM) control if using the radio's internal keyer
Visual / ergonomic:
High contrast / dark mode optimized for low-light shack environments (night owl contest shifts)
Large click targets suitable for someone who may be fatigued after 24-48 hours of operating
Keyboard shortcut support for all primary controls
Nice to have:
Waterfall or bandscope in a minimal form - even a narrow one helps spot activity without switching apps
ANF (automatic notch filter) toggle - kills heterodynes from nearby stations fast
The goal is a layout where an operator can monitor their station health and make quick RF adjustments without taking their eyes off the logging software or the exchange. Think of it as a "heads-up display" for the radio — clean, high-contrast, and focused. This is different than the current Minimal display.
This doesn't need to replace the current full-featured GUI at all. A toggleable compact window or a separate contest skin would be ideal. Many operators run dual-monitor setups where the logging software gets the main screen and the radio client gets a secondary display — a streamlined contest panel would be perfect for that workflow.
I think this would make AetherSDR significantly more competitive as a FlexRadio client for the contesting community, which is a large and enthusiastic segment of the amateur radio world. Contesters also tend to be vocal advocates for the tools they trust, so this could have real visibility benefits as well.
Thanks for considering it — and again, great work on the project overall. Happy to elaborate on any of the specifics or provide feedback on mockups if that would be helpful.
73,
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reviewing the existing GUI and the current Minimal display, then determine whether a contest-focused panel or alternate layout is feasible. Done would require a clearly scoped design covering the prioritized controls, high-contrast presentation, supported operating modes, and interaction workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100