Request preparation
What would you like?
Persist CW Reader Sensitivity across application restarts
What
Currently, the CW reader sensitivity setting in AetherSDR is not saved when the application is closed. Every time the application is launched, the user must manually re-adjust the sensitivity to their preferred level. This feature would ensure the last-used sensitivity value is stored and restored automatically.
Why
AetherSDR users often operate in consistent noise environments or have personal preferences for the decoder's trigger threshold. Manually resetting this value every session is a repetitive task that detracts from the "set and forget" user experience expected of a native desktop client.
How Other Clients Do It
SmartSDR (Windows): Saves all slice-specific and global decoder settings within the client profile or global settings database.
SDR++ / GQRX: Generally persist all slider positions and DSP thresholds in a .conf or .ini file upon exit.
Suggested Behavior
The sensitivity value should be hooked into the AetherSDR settings management system (likely via QSettings).
The user adjusts the sensitivity slider in the RxApplet or specialized CW decoder panel.
Upon application exit (or immediately upon change), the value is written to the configuration file.
On the next startup, the RxApplet (or relevant UI component) initializes the slider and the underlying decoder logic with the stored value.
Protocol Hints
While the CW reader is likely a client-side DSP implementation in AetherSDR, if it utilizes the FlexRadio discovery/API for thresholding, relevant commands might involve:
c{stream_id} threshold={value} (if handled by radio firmware)
Most likely: Local client-side variable persistence within the AetherSDR C++ logic.
Acceptance Criteria
CW sensitivity slider position is identical after a restart to what it was before closing.
The actual decoding threshold reflects the restored slider position immediately upon startup.
Settings are stored per-slice if AetherSDR supports independent decoder instances.
Suggested Labels: enhancement, GUI
Request preparation
What would you like?
Persist CW Reader Sensitivity across application restarts
What
Currently, the CW reader sensitivity setting in AetherSDR is not saved when the application is closed. Every time the application is launched, the user must manually re-adjust the sensitivity to their preferred level. This feature would ensure the last-used sensitivity value is stored and restored automatically.
Why
AetherSDR users often operate in consistent noise environments or have personal preferences for the decoder's trigger threshold. Manually resetting this value every session is a repetitive task that detracts from the "set and forget" user experience expected of a native desktop client.
How Other Clients Do It
SmartSDR (Windows): Saves all slice-specific and global decoder settings within the client profile or global settings database.
SDR++ / GQRX: Generally persist all slider positions and DSP thresholds in a .conf or .ini file upon exit.
Suggested Behavior
The sensitivity value should be hooked into the AetherSDR settings management system (likely via QSettings).
The user adjusts the sensitivity slider in the RxApplet or specialized CW decoder panel.
Upon application exit (or immediately upon change), the value is written to the configuration file.
On the next startup, the RxApplet (or relevant UI component) initializes the slider and the underlying decoder logic with the stored value.
Protocol Hints
While the CW reader is likely a client-side DSP implementation in AetherSDR, if it utilizes the FlexRadio discovery/API for thresholding, relevant commands might involve:
c{stream_id} threshold={value} (if handled by radio firmware)
Most likely: Local client-side variable persistence within the AetherSDR C++ logic.
Acceptance Criteria
CW sensitivity slider position is identical after a restart to what it was before closing.
The actual decoding threshold reflects the restored slider position immediately upon startup.
Settings are stored per-slice if AetherSDR supports independent decoder instances.
Suggested Labels: enhancement, GUI