1420e56e77b8e6d2557c30e80a3cb625660d5a0a
Add diagnostic logging (no behaviour change) to distinguish, from one instrumented Windows test call, whether an auto-detected call records nothing because the wrong process tree was targeted, packets arrive but are flagged silent, or process loopback failed to start and the fallback hit the wrong device: - Log one line on every successful WASAPI stream open (initial and reopen): endpoint description (process tree pid + exe name for loopback, friendly name/id/role for device endpoints), rate and channels. - output_source_with_fallback: Info line when the primary target starts OK; the existing fallback Warn line now also names DefaultRender explicitly. - New CaptureStats (crates/audio/src/stats.rs), shared by the Windows and Linux capture loops: counts packets, frames, packets flagged silent, and the peak absolute sample value, reported every 10 s and once more when a stream stops. Plain counters updated inline on the audio thread; no locks, no extra threads. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Gesprächsrekorder
A Tauri 2 desktop app that records calls (Teams, MicroSIP, browser-based softphones, …), then transcribes and summarizes them.
Workspace layout
crates/core(recorder-core) — core domain logic: call detection, recording orchestration, transcription and summarization. Independent of the Tauri app shell and the audio backend so it can be unit-tested without a GUI, a sound device or network access.crates/audio(recorder-audio) — audio capture and WAV/FLAC encoding.src-tauri(call-recorder) — the Tauri application shell.ui— Svelte 5 + Vite + TypeScript frontend.
Development
# Rust workspace
cargo test --workspace
# UI
cd ui && pnpm install
# Run the desktop app in dev mode
cargo tauri dev