summaryrefslogtreecommitdiff
path: root/examples/micscope/README.md
diff options
context:
space:
mode:
authorGabriel Schneider <[email protected]>2026-11-17 01:01:26 -0300
committerGabriel Schneider <[email protected]>2026-11-17 12:15:01 -0300
commit70be2e0776d2e61a2d018b264ef5602e7e2c7f86 (patch)
tree620d316cc48062d374b1c270cda0723afbb3fc7f /examples/micscope/README.md
parente699ffe4182f66e28180ea2d91ab1fb8c408d49e (diff)
downloadsketchbook-70be2e0776d2e61a2d018b264ef5602e7e2c7f86.tar.gz
sketchbook-70be2e0776d2e61a2d018b264ef5602e7e2c7f86.zip
micscope: a take starts its file empty; a deleted take's file stays, and why
Phase 1 left two loose ends in micscope's take files. A new take could continue an old file when its id met one already written without a jump in between (the jump is what moves next_id past written files), and a deleted take's file stayed on disk. The host gains one call beside appendFile: f.host.writeFile(name, bytes) writes a new, empty file of that name, through the same vtable entry with a `replace` flag. The old file is unlinked, so a readFile mapping of it keeps its bytes, and the host's cached mapping is retired (kept until exit, the sketch may hold it) so the next readFile maps the new file. The web host writes nothing, as for appendFile. micscope writes each take's file so when the take begins: on the frame whose transport request is newly `recording`, live, and not a jump (a jump's requests are restored State's, not a beginning; a fresh Session counts old requests as handled, so a restart mid-recording keeps its file), before the takes are read; `open` writes a file's samples so too. A deleted take's file stays: its State entry comes back with any seek or mark from before the delete, marks are kept with no end, and an exported session carries them; neither the sketch (which cannot see the history) nor the host (which cannot read State's meaning) can tell when none is left. So "never, safely": the file is kept. Tests: zig build test, 164/166 steps, 132/132 tests (the appendFile test now also replaces a file and reads back only the new bytes); the one failure was the Typst bench's 1 ms bound (1.024 ms), timing code this change does not touch, on a machine loaded by other builds; it passed in the next full run (166/166, with the change above this one). micscope's zig build test, 67/67 steps, 10/10 tests. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_016Y9MNBECMWcJD5pdS4SR6T
Diffstat (limited to 'examples/micscope/README.md')
-rw-r--r--examples/micscope/README.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/examples/micscope/README.md b/examples/micscope/README.md
index c02318c..e917bf0 100644
--- a/examples/micscope/README.md
+++ b/examples/micscope/README.md
@@ -151,7 +151,8 @@ addresses as QR codes, for phones).
Each take is a file of its samples (mono 32-bit floats at the host's
rate), `micscope.state.take-<id>.f32` beside the state (in `.sketchbook/`
under `zig build run`), written as it records (`Host.appendFile`). State
-lists the takes, so they are still there after a restart. A deleted take's
-file stays: a seek back finds it again. Takes stop at ten minutes; the
+lists the takes, so they are still there after a restart. A take starts
+its file empty (`Host.writeFile`). A deleted take's file stays: a seek
+back, or any mark from before the delete, finds it again. Takes stop at ten minutes; the
strip holds 64. A `micscope.state.store` from before is not read: its takes
stay in it.