Every box drew its label unconditionally, so overlapping transmissions
stacked their text into an unreadable smear — several frame names painted
over each other at the same pixels.
DrawBoxLabel now claims a screen-space rect before drawing and skips the
label if it would intersect one already placed this frame. Draw order
decides the winner, so the topmost box keeps its text and the ones beneath
go quiet instead of smearing. The claim is clipped to the box width, so a
long label reserves only what the scissor actually paints rather than
silencing neighbours over space it never uses. Nothing is lost: hovering
still reports every box under the cursor.
The stacked-hover tooltip now sits above the cursor and centred on it,
flipping below only when there is no room. It previously opened down and
to the right, covering the very boxes being described.
Also removes click-to-pin. It was never asked for, it did not reliably
work, and hover alone answers the question it was meant to serve.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8ZWfr5XZyyDttvkhJUgHN
The source image was sized at one column per STFT segment with no upper
bound. That is fine for short captures but impossible for long ones: a
5.7-hour file at 12 kHz yields ~478k segments, i.e. a 478450x1025 RGBA
image (~2 GB) roughly 29x past the ~16k-per-dimension texture limit every
GL implementation enforces. The upload failed, the texture id stayed 0,
and the draw was skipped — so the spectrogram was simply blank, with no
error anywhere to say why.
Build the image for the segment range actually on screen instead of the
whole file, capped at MAX_SPECTRO_IMAGE_WIDTH. Simply clamping the
full-file width would have fixed the blank render while permanently
discarding the detail zooming is meant to reveal (478k segments into 8k
columns is 59:1, no matter how far in you go). Tying the range to the view
keeps resolution proportional to zoom: 59 segments per column at full
zoom-out, reaching 1:1 by ~1% zoom, with the image never exceeding ~33 MB.
Where several segments do share a column their per-bin MAX is kept rather
than a sum or mean, so a short burst lights its column instead of being
diluted by quiet neighbours — the same reasoning behind a min/max waveform
envelope. Amplitude normalisation is likewise scoped to the visible span,
which keeps rebuild cost independent of total duration and lets the colour
scale follow what is on screen instead of a loud burst hours away.
Rebuilds trigger when the view leaves the cached range, which is padded by
25% so ordinary panning re-renders about once every six frames rather than
every frame. The headless --render path sets no range and so still covers
the whole file, capped; verified end to end on a 5.67-hour capture, which
now renders 8110x1025 with visible structure where it previously produced
nothing at all.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8ZWfr5XZyyDttvkhJUgHN
The hover hit-test collected its result into a single int, and each layer
assigned unconditionally, so the last box drawn won and everything beneath
it was silently dropped. With multiple stations transmitting concurrently
that hid most of what was there: co-located frames in the same band are
indistinguishable on screen, and the tooltip would name exactly one of
them with no indication the others existed.
Collect the hits into a stack during the same draw pass (the collision
math was already there, only the result was being discarded). When more
than one box is under the cursor the tooltip becomes a list — one row per
event, topmost-first, each with its own colour swatch so a row maps back
to a box on screen. Rows lead with node / frame / seq / ch, which is what
actually separates overlapping transmissions. Depth is capped at
MAX_HOVER_STACK with a "+N more" count so a deep pile can't cover the
spectrogram; a single hit still gets the full-detail tooltip as before.
Clicking a stack pins the list so it can be read without holding the
cursor still — otherwise the tooltip vanishes the moment you move toward
it. Click again or Esc to release. A pinned stack is a frozen snapshot,
so live hover does not overwrite it; it is dropped when the annotation
overlay is hidden or a new file is loaded, both of which would leave it
pointing at events that no longer exist.
Clicking stacked annotations pins rather than clearing the selection.
A click on empty space or a lone box clears as before.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8ZWfr5XZyyDttvkhJUgHN
The minimum visible time window was a flat 2% of the file, but view.start
and view.end are normalized to the whole signal — so the achievable time
resolution scaled with file length. A 30-minute recording could never show
less than a 36-second span, while a 30-second one reached 0.6 s. Long
captures were effectively unreadable at the sample level no matter how far
you scrolled.
Derive the floor from the STFT hop instead (MinTimeViewWidth): segments sit
fftSize/HOP_RATIO samples apart, so the real limit is the point where only
a handful of segments span the viewport and further zoom would interpolate
rather than reveal. The floor is now a constant ~43 ms at 48 kHz/1024
regardless of duration — an 844x improvement on a 30-minute file, and it
tightens further with a smaller FFT. Guards cover the unloaded (sampleRate
0) and shorter-than-the-floor cases.
Zooming is also no longer forced to move both axes together. The bare wheel
keeps the existing coupled behaviour; Shift+wheel is time-only and
Ctrl+wheel frequency-only, so a long capture can be stretched along time
without collapsing the frequency range to match.
Time-axis labels now pick their precision from the span between adjacent
ticks (1 to 4 decimals, and m:ss.sss past a minute). At the spans this
change makes reachable the old fixed "%.1fs" printed the same value in
every slot, which read as a frozen axis.
Adds a `wheel X Y N [mod]` action to shot_input.sh for exercising zoom
headlessly, and known_bugs.md for behaviour that is unspecified rather
than broken.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8ZWfr5XZyyDttvkhJUgHN
DrawScopeView's waveform envelope already drew only viewStart..viewEnd,
but TimeToX ignored both and mapped 0-1 across the full widget width. The
grid lines and the playback cursor were therefore laid out against the
whole signal while the trace beneath them showed a zoomed sub-range, so
the two drifted out of register the moment the view was zoomed or panned —
and out of register with the spectrogram directly above, which shares the
same time axis.
Map through the visible window in TimeToX, space the ten divisions across
that window rather than the whole signal, and keep the existing bounds
check so a cursor outside the current view is dropped instead of clamped
to an edge.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8ZWfr5XZyyDttvkhJUgHN
PlaySelectedRegion copies, bandpasses and normalises the selected span up
front, so the audio in flight is fixed the moment Space is pressed. The
playhead, though, was drawn against the live app.sel and its duration
re-derived from the live selection — so moving or resizing the selection
mid-playback made the marker jump, overrun, or scale against a region
that had nothing to do with what was audible.
Snapshot the played region (playSelStart/playSelEnd) and take the duration
from the buffer's own sample count rather than app.signal.duration, which
is derived pre-mono-downmix and disagrees for stereo files. The playhead
and the scope cursor both read the snapshot; playheadT is clamped at 1.
Also: a sub-threshold click inside an existing selection no longer clears
it. Silently resetting to full range there changes what Space plays, which
is surprising when the click was an aborted drag. A click on empty space
still resets as before.
The *semantics* of editing a selection during playback remain undefined —
whether audio should follow the box, stop, or keep going as it does now.
This commit only makes the marker honest about what is coming out of the
speakers. Recorded in known_bugs.md.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8ZWfr5XZyyDttvkhJUgHN
Follows 81bab18, which fixed the same class of bug in the PNG export path.
sel.freq* are fractions of the *displayed* frequency axis (capped at
EffectiveMaxFreqHz), not of true Nyquist, but BuildSelectionAudio and
ExportSelectionWAV both scaled them against sampleRate/2. With a display
crop active this widened the bandpass by 1/DisplayFreqFraction(), so the
audio you heard (and the WAV you exported) covered a higher, wider band
than the box you drew.
Convert through EffectiveMaxFreqHz for the selection bounds; the filter
still reasons in true-Nyquist terms, which is what the separate `nyquist`
local is for. The "is this effectively full-band?" test likewise compares
against nyquist, so an uncropped selection still skips filtering.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V8ZWfr5XZyyDttvkhJUgHN
The spectrogram image spans the full Nyquist axis, but sel.freq* are
fractions of the displayed axis (capped at EffectiveMaxFreqHz). ExportPNG
mapped the selection straight onto the full image height, so when the
display max frequency was below Nyquist the export grabbed a band higher
in frequency than the box-select. Scale by DisplayFreqFraction() to match
the on-screen texture sub-sampling.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Scrollbars: proper track-travel geometry so a min-size thumb stays
inside the track and dragging maps 1:1 to the cursor at any zoom;
clicking the empty track jumps the view to re-center the thumb under
the cursor. Rounded thumbs with hover/active highlight; taller track.
- Spectrum slice (PSD) always spans the full frequency range; ignoring
the selection's freq bounds avoids cropping bins and skewing the
auto-ranged dB axis and peak pick. Selection rect still drawn normally.
- Default annotation overlay opacity 0.06 -> 0.24 (quiet but legible).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- README: rewrite Build section for the hand-written Makefile (make /
make DEBUG=1 / run / test / bench). Add a "System dependencies" table
with the X11+GL dev packages per distro (apt/dnf/pacman/zypper/apk),
since a clone won't build without them and the error is otherwise
cryptic. Fix stale ./bin/Debug paths to ./bin/Release.
- Makefile: add `make check-deps` — probes for the required X11/GL dev
headers and prints the install command for the detected distro on
failure (via /etc/os-release).
- build_web.sh: auto-discover app modules from src/*.c (drop the
hardcoded APP_MODULES list that had to be hand-synced), matching the
desktop Makefile. Excludes the desktop platform backends. Remove the
stale rspektrum.make reference.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Build system
- Add a single hand-written Makefile (GNU make + gcc, pure C). Builds
raylib from vendored source and links rspektrum with no premake/lua.
Targets: all/run/test/bench/clean; release default, DEBUG=1 for debug;
ARCH overridable (defaults to -march=x86-64-v3).
- Remove premake entirely: rspektrum.make, raylib.make, build/premake5*
binaries, build/premake5.lua, build/ecc/*. The generated top-level
Makefile was gitignored, so hand-edits to it were silently lost.
- Vendor raylib src/ into the repo (was gitignored -> fresh clones could
not build). Commit only src/ (~16MB); examples/projects stay local.
Verified: a build from the git-tracked tree alone succeeds offline.
- Release flags bumped to -O3 -ffast-math with a portable arch baseline
(x86-64-v3 = AVX2+FMA on x64, SSE2 on x86). Confirmed FMA/AVX codegen
in fft.o.
FFT optimization (src/fft.c)
- Precompute twiddle factors and the bit-reversal permutation once per
size, cached as a small plan table (FFTW's idea, lightweight). Removes
the per-butterfly cexpf() and per-element bit-twiddling that dominated.
- 3.6x faster on the mlnl_samples.wav STFT workload (2048-pt, -O2 same
flags both sides): 81us -> 22us per FFT. With the new -O3/-ffast-math/
AVX2 release flags stacked: ~15us (5.5x vs the old -O2 baseline).
- Verified vs a double-precision reference DFT: 1e-6 relative error,
round-trip 2.4e-7. Drop-in: same FFT() signature.
Tests/bench (bench/)
- fft_verify.c: FFT vs reference DFT + round-trip check (make test).
- fft_bench.c: times the real STFT workload (make bench).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The font atlas was rasterized once at a fixed 16px and point-filtered, then
scaled to a logical size at draw time. On HiDPI it got upscaled (acceptable);
on standard-DPI it got downscaled, and point filtering dropped rows/columns of
the anti-aliased glyphs, thinning stems into a faint "hyper-skinny" look.
Bake the atlas at the real physical size text is drawn at
(16 * GetUIScale() * GetWindowScaleDPI().y), quantized to 4px steps, and rebuild
it via EnsureUIFont() once per frame when that density changes (resize, or
moving between monitors of different DPI). Use mipmaps + trilinear filtering so
downsampling stays smooth. Call sites are unchanged: DrawTextEx still scales the
atlas glyph to the same logical size, only the backing resolution differs.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The overview-then-idle high-res fill had two defects that left permanent
black/low-res vertical stripes:
- On any interaction the driver set isBgProcessing=false to pause, but nothing
ever re-armed it, so the background sweep died on the first pan/zoom and the
strided overview was never completed. Now isBgProcessing simply tracks
!bgFinished and the per-frame compute is gated on !IsUserInteracting(), so the
sweep resumes on its own once the user stops interacting.
- The foreground (visible-range) fill overwrote the background sweep cursor
bgHighResSeg with the current view position, so the sweep skipped everything
before the view and stranded it uncomputed. The foreground pass no longer
touches the cursor; the sweep stays monotonic from 0.
Also recolor the displayed image as segments fill in (throttled during the
sweep, forced at completion) instead of only at the very end, so freshly
computed regions actually appear; and short files whose overview is already
full-resolution (skipFactor 1) skip the sweep entirely.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The left-hand control panel is laid out top-to-bottom with a running y; with
annotations expanded or a short window, the bottom buttons (export, signal
info, about) ran off the bottom and were unreachable. Offset the content by a
sidebarScroll amount, measure the laid-out height, and let the wheel scroll it
(clamped) when the cursor is over the sidebar and no modal is open. No visible
scrollbar; the spectrogram's wheel-zoom already ignores the sidebar column so
the two never both fire.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The three test_tone_*.wav files are unused and regeneratable via
generate_test_tones.py; resources/test_announce_qpsk_275hz.wav was also
unreferenced. mlnl_samples.wav remains as the in-repo sample.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- README: embed resources/Screenshot.png under the intro
- remove accidentally-committed app export outputs (spectrogram_full.png,
spectrogram_export.png) and gitignore them so they don't return
- remove unused resources/wabbit_alpha.png and stray .qwen/settings.json.orig
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Rewrite --render to compute the spectrogram and write a PNG entirely on the
CPU, with no window, no GL context, and no X server. Previously it opened a
hidden GL window and grabbed LoadImageFromScreen(), which still required an X
server (Xvfb); the output was a UI screenshot rather than the spectrogram data.
The new path (RunHeadlessRender) loads the WAV, computes the STFT, colorizes
the bitmap at native STFT resolution, bakes the mLnL annotation overlay onto
it, and exports — all CPU-only. render.c gains a GL-free colorize
(BuildSpectrogramImageCPU), a CPU font loader (LoadFontCPU), and a CPU overlay
drawer (DrawAnnotationsToImage).
Annotations draw outline + label only: mLnL captures contain many overlapping
full-band boxes whose translucent fills alpha-stack to opaque and bury the
signal. The outline marks each region while the spectrogram reads through; a
dark backing strip keeps labels legible. Note: MeasureTextEx/ImageText* bail
when font.texture.id == 0, so the CPU font sets a sentinel non-zero id (the
draw path reads glyph images, never the texture).
Render options: --annotation-opacity (overlay strength), --annotation-kinds
(comma-separated kind filter), --width (resize; default native). Removed the
obsolete --pane/--height window options and the screenshot workaround.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Replaces the stale Unity-port README (wrong controls, premake build,
missing features). Documents the mLink/mLnL focus, real keybindings,
make-based build, headless --render mode, and the Xvfb GUI-driving
primer. Consolidates the old SPECTROGRAM_README.md into README.md.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Captures the idle-CPU findings and patterns from the perf work:
event-driven idle, raylib's constant ~5% busy-wait, lazy audio
device, headless render recipe, and the warnings that bit us.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
raylib's frame limiter partial-busy-waits ~5% of every frame interval, so
capping the FPS couldn't get idle CPU below ~5% of a core, and the audio
output device's mixing thread spun continuously even when nothing played.
- Idle render: go fully event-driven when idle. While active (focused +
something animating, or within a 0.5s grace window) run at ACTIVE_FPS;
otherwise EnableEventWaiting() so EndDrawing's PollInputEvents blocks on
glfwWaitEvents until the next input/window event. Unfocused windows skip
drawing entirely and block. Headless render is exempt (its hidden window
gets no events). Replaces the earlier fixed-FPS idle throttle.
- ACTIVE_FPS lowered 60 -> 30: ample for a non-game UI, halves active cost.
- Lazy audio device: open it on demand at first playback (EnsureAudioDevice)
and release it once idle and not playing (ReleaseAudioDevice), reopened on
the next play. Never closes mid-playback (gated on !isPlaying), so audio
always finishes first. Shutdown is guarded with IsAudioDeviceReady().
Idle/backgrounded window now drops to ~0% CPU (no render busy-wait, no audio
thread); snaps back instantly on input.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The main loop redrew the whole scene at 60 fps unconditionally, keeping
the GPU (and, on software GL, the CPU) busy even while idle — enough to
heat the machine. Add two cooling measures (desktop only):
- Idle FPS throttle: drop to 10 fps when nothing needs animating (no
input, mouse movement, playback, loading/background STFT, drag/pan, or
counting-down notice), with a 0.5s grace window; snap back to 60 fps on
activity. Measured ~34% -> ~8% idle CPU on real hardware.
- Focus pause: when the window isn't focused, skip the frame entirely —
pump events via PollInputEvents() + WaitTime() with zero drawing, so
refocus/close still register. Guarded with !headless so the hidden
render window still draws its single capture frame.
Also fix two -Wformat-truncation warnings (surfaced at -O2) in the
tx_frame label path: widen pos[16]->[28] for the worst-case " %d/%d",
and the caller's label buffer lbl[64]->[160] since base can be note[96]
(DrawBoxLabel scissor-clips to the box, so behavior is unchanged).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Commit the accumulated working-tree changes as one snapshot.
- Headless render: `--render OUT.png INPUT.wav` draws the spectrogram
(full window, or `--pane` for the spectrogram pane only) to a PNG
with no visible window. Options: `--annotations`/`--no-annotations`,
`--annotation-opacity`, `--width`/`--height`.
- mLnL annotations: parse the optional `mLnL` RIFF chunk (schema v2)
and render tx_frame/assertion/control overlays, a timeline lane, and
a waveform-scope echo, with hover tooltips on the spectrogram,
timeline, and scope.
- sched_offset_ms: parse the per-frame intent->air latency and surface
it in the hover tooltips (boxes stay air-anchored upstream).
- Supporting: build wiring (rspektrum.make), shared types/headers,
web-build and capture-script tweaks, and removal of the old
synchrosqueezing LaTeX doc.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Make the Emscripten build behave like the desktop app for loading, window
scaling, and exporting. All changes are #ifdef __EMSCRIPTEN__-gated or no-op on
desktop, so native behavior is unchanged.
Scaling:
- Drop FLAG_WINDOW_HIGHDPI on web. The emscripten-GLFW shim forces a fixed
pixel canvas style (!important) when HiDPI-aware, overriding the shell's
100vw/100vh CSS so the canvas can't fill the page; raylib's own resize/window
callbacks also disagree about dividing by devicePixelRatio, desyncing the
framebuffer from the reported screen size.
- Sync raylib's window size to window.innerWidth/innerHeight each frame via
SetWindowSize (guarded against no-op churn). This keeps screen size, GL
viewport, and projection consistent, so the UI fills the viewport and reflows
on resize like the desktop window.
Loading:
- Compute the full-resolution STFT synchronously when a file loads instead of
the desktop overview-then-deferred-high-res path, which relied on many
main-loop iterations yielding to the browser and appeared to stall partway.
- Allow the wasm heap to grow (INITIAL_MEMORY + ALLOW_MEMORY_GROWTH) so longer
recordings fit now that everything is computed up front.
Exports:
- Add Platform_OfferFileToUser(): no-op on desktop (file is already on disk);
on web it reads the just-written file from MEMFS and triggers a browser
download, then unlinks the temp copy. Wired into PNG and WAV export, which
now show just the filename in the status message.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The web build had bit-rotted since the last successful build (Apr 12):
- build_web.sh only compiled spectrogram.c + platform_web.c, but commit
3a8f20b split the code into 9 modules — link failed with undefined
symbols. Now compiles all app modules (kept in sync with rspektrum.make,
swapping platform_linux -> platform_web).
- Dropped -DPLATFORM_WEB from the app-module compile/link: the platform
refactor (b6942d8) added a `Platform` enum whose PLATFORM_WEB enumerator
collides with the macro. Web behavior is selected by linking
platform_web.c, not the macro, so the define was never needed by our code
(raylib still gets it in its own build).
- Removed the stale `fonts/DejaVuSansMono.ttf` preload (font moved to
resources/fonts/); resources@resources already bundles it and the runtime
loads it relative to the resources dir.
- platform_web.c: include <errno.h> for ENOSYS (this stub had never compiled).
- build_web.sh: skip the slow raylib rebuild when libraylib.a already exists.
Verified: `./build_web.sh release` exits 0 and produces html/js/wasm/data;
font is packaged; all artifacts serve 200 via python http.server and the
wasm has valid magic bytes.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Spectrum slice (S): floating panel plotting the time-averaged power
spectrum of the current selection (or the visible view when there's no
selection). Frequency on X over the region's band, auto-ranged dB on Y,
with a peak marker. Backed by ComputePowerSpectrum() in stft.c (mean
linear power per bin over the time span). The selection stat panel now
biases to the left when this panel is up so the two don't overlap.
Marker/ruler tool (M): press-drag-release drops point A and B; the
overlay shows crosshairs, a connecting line, and a readout of the
ham-useful deltas — Δt, Δf, tone spacing (1/Δt), and drift (Δf/Δt).
Marker mode swaps the LMB-drag gesture from box-select to marker drop
(Alt/middle still pan); RMB/Esc clear the measurement. Markers reset on
new-file load alongside the selection.
Both are gated toggles (off by default), wired into the keymap (so they
self-document in the About dialog) and the sidebar.
Verified headlessly: idle viewport pixel-identical to baseline (AE=0,
deterministic); both panels render correctly with sensible numbers.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
New "Export WAV (W)" button + W key saves the current selection as a mono
WAV — the same band-limited, time-cropped audio you'd hear on playback, so
"what you hear is what you save". Self-documenting filename encodes the
time span and frequency band (rspektrum_sel_<t0>-<t1>s_<f0>-<f1>Hz.wav).
Refactor the shared filtered-region builder out of PlaySelectedRegion
(which also fixes a leak: it never freed regionSamples after
LoadSoundFromWave copies it). Make the export confirmation message persist
~3s instead of flashing for a single frame (affected PNG export too).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The playback bandpass transition was freqPerBin*10 wide, and freqPerBin
depends on the FFT size, which is derived from the selection length — so
the same frequency band got a sharper or softer filter depending on how
long a region you selected. Set the skirt to ~20% of the passband (capped
at 100 Hz), floored at 3 FFT bins so it stays smooth at coarse resolution.
Now a given band sounds the same regardless of selection duration.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Floating tag follows the pointer over the spectrogram showing the time,
frequency, and STFT magnitude (dB) under the cursor — the standard
spectrum-analyzer probe. Suppressed while selecting/panning (which have
their own readout) and when a modal is open.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The selection readout was time-domain only — Energy/Peak/RMS/PAPR computed
from the whole-bandwidth waveform in the time span, ignoring the box's
frequency bounds entirely. The 2D box only measured one axis.
Add ComputeSpectralStats (stft.c): measures the boxed band from the STFT
magnitude (not the synchrosqueezed display buffer, which relocates energy)
and reports peak frequency, power-weighted centroid ("power center"),
occupied bandwidth (in-band span >3 dB over a median noise floor — robust
for both tones and noise-like bursts), and in-band SNR.
Also fold the two near-identical stats-panel blocks in render.c into one
DrawStatPanel + BuildSelectionStatLines helper so the live-drag and
committed-selection readouts can't drift.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Portable guide for an agent doing refactor/code-health work on a raylib
(or any GLFW/OpenGL) app: Xvfb + screenshot + pixel-diff loop, xdotool
key/mouse injection (incl. the press-release-must-span-frames gotcha),
determinism strategies for static apps vs continuously-animating games,
temp-keybinding state forcing, and a porting checklist for shot_input.sh.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
shot_input.sh launches the app under Xvfb and drives it with xdotool,
then screenshots for pixel-diff verification. Adds click/drag/rdrag
pseudo-actions that insert the frame gap raylib's button edge-detection
needs (a bare xdotool "click 1" is too fast and no-ops). Documents the
settled-capture timing (12s) and the 1280x800 viewport/sidebar bounds.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
ResetForNewSignal only reset the time view + selection, leaving the
previous file's frequency zoom, in-progress drags, and playback running.
Loading a new file now zooms out both axes, cancels any drag/pan/divide,
clears the selection, and stops playback + rewinds the playhead. Display
preferences (colormap, dB scale, FFT size, grid, scope layout) are
preserved by design. All three load paths funnel through this function.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The visible-window + pan-anchor state was 10 flat fields (viewStart, viewEnd,
freqView*, pan*) used densely throughout the zoom/pan/scrollbar code. Group
them into a Viewport sub-struct (app.view.*).
Rename anchored strictly to 'app.' so ScopeView's own view->viewStart/viewEnd
(same field names) are untouched. Settled render verified pixel-identical
(AE=0); End/zoom path verified via injected key input.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The box-selection state was 11 fields spread across three comment blocks
(time sel, freq sel, drag state). Consolidate them into one Selection
sub-struct (app.sel.*) and extract the 4-line 'clear to full range' block —
duplicated in 5 places — into a ClearSelection() helper.
Pure mechanical rename (anchored to app./spa-> so the ScopeView fields of the
same name are untouched) + behavior-identical dedup. Fully-settled render
verified pixel-identical (AE=0).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Reset Sel advertised an 'R' key that was never bound and only set the
selection to the current view, overlapping Clear/Esc. Removed it and made
Clear a single full-width button labelled to match the Esc shortcut.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Replace the global key handling scattered through the main loop with a single
KEYMAP table (key, gate, action, help text) and a DispatchKeymap() pass. The
About/Help overlay now renders its key list straight from the table, so the
on-screen shortcuts can never drift from the actual bindings.
- Order-sensitive keys (Space, Esc) stay inline where their frame ordering
matters; they carry action==NULL and appear in the table for the help list.
- Adds the F11 fullscreen binding the sidebar button already advertised but
that was never actually wired up.
- Fix About title em-dash rendering as '?' (font is ASCII-only); use a hyphen.
Launch render verified pixel-identical (AE=0); keys verified via injected input.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Collapse the repeated 'CheckCollisionPointRec + IsMouseButtonPressed' click
test and the 'DrawRectangleRec + DrawRectangleLinesEx' panel chrome into two
helpers used across the sidebar buttons. Pure readability; render output is
pixel-identical (verified AE=0 vs baseline).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The "Waveform (Time/Amplitude)" label was drawn in the same ~30px band as
the time-axis labels and the horizontal scrollbar, so it overlapped the
"0.0s / 7.7s / ..." ticks. Shorten to "Waveform" and tuck it faded inside
the scope's top-left, clear of that band.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The spectrogram layout metrics (sidebar width, margins, freq-label width,
scrollbar sizes, spectroHeight, viewBounds) were computed with identical
formulas in three places — the input, selection, and render passes — so a
layout tweak meant editing all three in sync (as the scope divider change
just did). Introduce a Layout struct + ComputeLayout(); each site now
unpacks from it into its existing locals, leaving every downstream
coordinate reference untouched. Verified pixel-identical to the previous
build (ImageMagick AE = 0).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
ComputeSTFTIncremental (overview, skipFactor-strided) and
ComputeNextHighResChunk (high-res fill) had ~50 lines of identical
per-segment code (windowing, FFT, bin fill for both the normal and
derivative spectra). Extract it into ComputeSegment() with a reusable
SegScratch buffer set (allocated once per pass, no per-segment malloc).
Each caller keeps only its own skip logic. Behavior-preserving — verified
the rendered spectrogram is unchanged.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Two extensibility easy-wins, both behavior-preserving:
- UiModalOpen() centralizes the "an overlay owns input" check that was
copy-pasted as `!showFileBrowser && !showAbout` across 6 input gates.
New overlays now update one place.
- Colormaps become a COLORMAPS[] table (name + function) indexed by enum.
GetColormapColor and the sidebar both read it, so adding a colormap is
one enum value + one Cmap* fn + one row — and the sidebar name can no
longer drift from the enum (deleted the parallel colormapNames[] array).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Toggling the scope off (P) now drops the divider to the bottom so the
spectrogram fills the whole view, instead of leaving an empty gap. The
divider handle is always drawn and grabbable: drag it up from the bottom
to bring the scope back, or drag it down past ~88% to hide it. Layout uses
an effective-divider helper (1.0 when hidden) so all three layout sites
stay in sync.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
dB floor handling:
- Fix the white-out/inversion when the floor was cranked up: guard the
(ceiling - floor) range in ColorizeSpectrogram so floor >= ceiling
degrades to a hard threshold instead of dividing by ~0 (white) or a
negative (inverted colors).
- Add two amplitude scale modes, toggled in the sidebar:
* Relative: ceiling tracks the signal peak, floor sits N dB below it
(slider = dynamic range, 10..100 dB). Floor can't cross the ceiling.
* Absolute: fixed dBFS scale (0 dBFS = full scale), slider sets an
absolute floor in dBFS. Brightness reflects real level.
Mode + both slider values persist across loads. This replaces the
amplitudeUserSet flag — storing the intent (range / absolute floor)
preserves it across re-scales structurally.
About / Help dialog (no help menu existed):
- F1 or sidebar button; documents the scale modes and the caveats
(dBFS not dBm — a WAV has no power reference; ~6 dB Hann window
offset; pixels are reassigned energy, not raw bins) plus key list.
- Modal: underlying spectrogram input is gated while open; open/close
handled in the main loop so the opening click can't self-close it and
a dismissing click can't fall through into a selection.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
- Split GenerateSpectrogramTexture into ComputeSpectrogramReassignment
(the expensive synchrosqueezing, cached in app.reassignBuffer) and
ColorizeSpectrogram (cheap). dB-floor and colormap changes now only
re-colorize instead of recomputing the whole reassignment every frame —
the dB slider and colormap switching are smooth on large files.
- AutoScaleAmplitude no longer overwrites a dB floor the user set by hand
(amplitudeUserSet flag, reset per file load).
- Extract ResetForNewSignal() used by all three load paths; removes the
duplicated reset blocks and the double ComputeSTFTInit per load. Drag-drop
now resets the selection like the browser already did.
- Remove the dead lastInteractedFrame field.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
spectrogram.c was ~2950 lines holding everything. Break it into cohesive
translation units; spectrogram.c keeps only globals + the main frame loop.
New modules:
- spectrogram_types.h shared types, constants, extern globals, inline math
- fft.c/.h FFT, bit-reverse, twiddle (standalone, no app deps)
- stft.c/.h STFT compute, adaptive resolution, FFT-size LRU cache
- audio.c/.h WAV/ffmpeg load, FreeSignal, bandpass, playback
- render.c/.h UI scaling, colormaps, texture gen, on-screen drawing
- ui.c/.h file browser, sidebar, sliders, PNG export
Also:
- utils.c now includes utils.h instead of re-typedef'ing AudioSignal/
SignalStats (they had to be hand-synced before).
- Remove dead code: ApplyHannWindow and ComputeSTFTHighResRange were never
called (the live high-res path is ComputeNextHighResChunk).
- Delete the unused raylib-template main.c.
- rspektrum.make: build the new units. premake5.lua: glob src/**.c so a
future regen stays correct.
Pure code movement otherwise; no behavior change. Builds clean (-Wshadow).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Three leaks, all at the relevant choke points:
- ComputeSTFTInit reallocated result->segments without freeing the old
array, and runs twice per load (load site + loadingPhase 0), so every
file load leaked the STFT. Free the previous result at the top.
- LoadWavFile malloc'd signal->samples without freeing the previous
buffer; free it just before the alloc (after all failure returns, so a
failed load never frees the existing signal).
- GenerateSpectrogramTexture overwrote *image with a fresh GenImageColor
without unloading the old one — leaked an image buffer on every reload
and every dB-floor/colormap regen. Unload first (NULL-safe on first use).
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
tyler