Normalize existing text files to LF to conform to the repository-wide
line-ending policy defined by .gitattributes by:
git add --renormalize .
Signed-off-by: Robin Getz <rgetz503@gmail.com>
get_spectrum_history reports what has been on a band over the last
while from the spectrum's scroll history, per bin and as a list of
signals with their duty cycles; get_waterfall_image returns the same
history as a picture, the first tool to put image content beside the
text in a result. Both switch scrolling on when it is off and say so.
list_windows shows every window with its workspace and whether it is
hidden, and set_workspace takes hidden alongside the workspace index.
capture_audio's inline copy is now mono and decimated to 16 kHz, so a
ten second capture fits under the 1 MB result limit; the file on disk
is unchanged.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The display was scaled for the gain the device had, and a change of tens of decibels left the
trace off the top or along the bottom. After the chosen gain has reached the trace the main
spectrum's reference level and range are set from it, as the GUI's autoscale button does; the
autoscale argument, default true, leaves the display alone when false, and the reply says
whether it was done. The auto tune in listen and scan does the same and says so.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The guard that removes a device set a failed listen or scan created compared only the index,
so a set another request had replaced at that index would have gone instead. The engine's UID
and the object's address are recorded at creation and checked before removal.
The Codex config writer now recognises sdrangel.url = "..." under [mcp_servers] as the server
already being defined, and refuses rather than adding a [mcp_servers.sdrangel] table a TOML
parser would reject as defined twice.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Tools: listen and scan reclaim their earlier channels before retuning the device, so a scanner
left running cannot move it in between; scan counts a range before building it; booleans are
read from JSON booleans, numbers and strings alike, so replace "false" is false and freeze 1
freezes; a MIMO device set takes receive and transmit channel types; deletion is serialised
from lookup to completion so two concurrent reclaims cannot take a third channel; tune_gain
refuses a gain or AGC key the device lacks; start_iq_recording checks the name first and cleans
up by UID; describe_settings emits a definition matched by name; remove_last_deviceset reports
a timeout; a device set a failed listen or scan created is removed again.
Capture: a name resolving to the capture directory itself is refused, a drive root works, and
files are listed by prefix rather than wildcard. The audio clock starts before the wait for the
sample rate. Subscriptions are capped per session, device set URIs checked, and absent device
sets skipped by the poll. The Codex writer drops dotted managed keys and refuses a spelling it
cannot rewrite rather than adding a duplicate table.
Bridge: one session at a time when SDRangel comes back, the stream socket is shut down rather
than closed from the other thread, SIGPIPE cannot end the process, and a failed notification
gets no reply.
Also: tool calls and audio captures give up when the server stops, so stopping the feature
cannot deadlock on a call waiting for the main thread; channels are held by UID throughout;
socket timeouts in the bridge; ResourceNotFound for a resources/read of a URI that is not there.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
listen modes dmr, dpmr, dstar, ysf, nxdn and nxdn24 set the DSD demodulator's FM deviation and
baud rate to what the standard needs, from the plugin readme's table, and dmr switches on both
time slots. Plain dsd sets the defaults explicitly so a retuned demodulator gets them too.
record_iq waited for nothing between patching the FileSink's file name and posting the record
action, and the action reaches the DSP thread ahead of settings routed through the channel, so
the sink recorded briefly to its old, empty name, leaving a .<timestamp>.sdriq in the working
directory. The file name is now confirmed on the channel before recording starts, and a bad
name is refused before a FileSink is added for it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
A feature listen added is kept while any channel of a type that feeds it exists, whoever
added it, so cleanup cannot take away a feature the user's own decoder is using.
A repeated listen in a paired mode retunes both demodulators rather than reclaiming and
recreating them: reuse is allowed when the intent channels of the type number what the mode
uses, and the partner is kept through the reclaim.
The capture path check resolves the nearest existing ancestor of the target to where the file
system really puts it, so a symbolic link or junction under the capture directory cannot lead
a recording outside it. Qt's canonical path does not see through a junction on Windows, so
the final path is asked of the system there.
The bridge remembers the resources the client subscribed to and subscribes again whenever it
rebuilds a session after SDRangel restarts, so updates carry on arriving.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
listen tracks the features it adds for a mode's output (AIS, Radiosonde, APRS) by UID, as it
does channels. The next listen or scan with replace removes one once no channel the intent tools
added still feeds it, on any device set, and cleanup removes the rest and lists them. A feature
that was already there is never tracked.
New listen modes: aprs, a PacketDemod with the APRS feature, and packet for the demodulator
alone. AIS is received on two channels, so listen ais centres the device on the frequency given
and puts a demodulator at each of -25 and +25 kHz, and the partner is counted as this call's
rather than reported as a leftover. arrange_workspace posts the new WorkspaceActions. The
settling loop tolerates a demodulator with no channel report instead of failing the call.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
listen and scan measure and set the receiver gain, as tune_gain does, when
they create a device set or move one to another band, and leave it alone on
a move within a band or a change of mode, or when told tuneGain false. On a
new device set this replaces the fixed 40 dB profile, which stays only when
tuning is declined.
A retune moves every channel on the device set, since each is an offset from
the centre. Channels the intent tools did not add are now kept on the
frequency they had, by moving their offset, where the new baseband still
holds them; an audio demodulator it cannot hold is removed, since all it
could do is play noise; a file sink, an analyser or anything else without
audio is left in place and named in the reply. The offset key is read from
the channel's own settings, as it differs by type.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
tune_gain steps a device through its gain range, measuring the noise floor
and the strongest signal on the main spectrum at each, and applies the gain
where the signal stands furthest above the floor, or, on a quiet band, the
lowest gain at which the antenna's noise rather than the converter's sets
the floor, short of overload. It knows the RTL-SDR, HackRF, Airspy, LimeSDR,
PlutoSDR and USRP, and takes a gain key and values for anything else.
scan steps by the channel spacing usual for the mode unless told otherwise,
refuses modes on fixed frequencies, measures its threshold from the floor
rather than assuming one, and reports every active frequency rather than the
five strongest and where the scanner happened to park. Broadcast FM is
scanned on its 100 kHz raster whatever step is given, with only the local
peaks reported, and listen and scan give it a 512 kS/s baseband with the
channel clear of the DC spike. pager, sonde and dsc modes are added.
listen retunes a demodulator of the right type a previous call added rather
than replacing it, and applies the RTL-SDR receiver profile only to a device
set it created. set_spectrum_settings reads the settings back and says when
a value was rounded or an averaging mode is set with nothing to average over.
get_spectrum_data returns its power array, which the generated serialiser had
been dropping.
describe_settings covers the spectrum display, and list_docs and get_docs
serve the GUI's own pages: the spectrum, its markers, measurements and
calibration, the main spectrum window, audio, configurations, device user
arguments and the transverter dialog.
The receiving guide gains sections on scanning, where each mode's output
appears and how long to wait for it, judging signal levels, gain, the
frequencies asked for by name including the DAB blocks, and the RTL-SDR's
limits on HF.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
listen only remembered the one channel its previous call added to a device
set, and scan remembered nothing, so exploring a band with both left a trail
of demodulators all playing audio and a Frequency Scanner still sweeping.
Both now register the channels they add, by uid so that a channel removed
from the GUI and another allocated at its address are not confused. replace,
now on scan as well, removes every such channel on the device set first, and
a new cleanup tool removes them all. Channels added any other way are never
touched; the reply says which of them the retune may have left outside the
baseband, and how to retune or remove them.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>