From 89a882cb55b17f93a741e8fe65c60103608b0ccc Mon Sep 17 00:00:00 2001 From: avi Date: Tue, 22 Sep 2026 10:00:32 -0500 Subject: [PATCH] =?UTF-8?q?STATUS:=20close=20both=20Sep-16=20open=20items?= =?UTF-8?q?=20=E2=80=94=20pump-error.log=20already=20gone;=20Large=20v3=20?= =?UTF-8?q?quiet-CPU=20benchmark=20measured=20(0.27x=20RTF=20on=20300s,=20?= =?UTF-8?q?0.43x=20on=201200s,=20CPU=20int8,=20beam=5Fsize=3D5,=20engine?= =?UTF-8?q?=20args)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- STATUS.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/STATUS.md b/STATUS.md index 989c9f2..862b3c8 100644 --- a/STATUS.md +++ b/STATUS.md @@ -3,6 +3,30 @@ Checkpoint for the standalone desktop app. Prepend a new dated section per material change; keep history below. +## 2026-09-22 — open-item audit closed; Large v3 quiet benchmark; in-app update check + +- **pump-error.log (open item 1, Sep 16): CLOSED — already gone.** Nothing + named pump-error.log exists under `~/.config/shonar-desktop/` anymore + (only `logs/engine.log`). The code path that writes it + (`DesktopState.kt` pump failure logger) is current and legitimate. +- **Large v3 full-length timing (open item 2, Sep 16): MEASURED.** Quiet + machine (app + engine stopped), CPU int8, same args as the engine + (beam_size=5), clips cut from a real 2 h 09 m recording: + - 300 s audio → 1107 s wall (**0.27× real-time**), first segment 37 s, + model load 8.7 s. + - 1200 s audio → 2768 s wall (**0.43× real-time**), first segment 52 s. + The earlier note ("300 s clip ran well under 7 min") was optimistic — + under real quiet-CPU conditions Large v3 is ~4–8× slower than that. + Practical read: a 2-hour recording ≈ 4–8 h of CPU transcription; + Base (~7× real-time) stays the sensible default, Large v3 is for + shorter, quality-critical clips. +- **In-app update check** (`7195aa1`, pushed): Settings gains + "About & updates" — build commit baked into the jar + (`generateBuildInfo` → `shonar-build.properties`), a Check-for-updates + button against the Forgejo commits API (up to date / update available + with Open-repo link / newer-than-remote for dev builds), verified live + on-device. + ## 2026-09-16 — open-item audit; Large v3 provisioning verified - **Large v3 first-use download verified end-to-end** in an isolated