| 1 | # Editing next to a recording |
| 2 | |
| 3 | `candidate/Features.one` is the writer's output for |
| 4 | `editing_a_recorded_page_keeps_the_recording_and_its_annotation` in |
| 5 | `crates/onestore/tests/page_media.rs`: the native section of |
| 6 | `corpus/m6/native-features-01` with one plain paragraph appended to the page |
| 7 | "Files and recording", where OneNote 2010 recorded `silence.wav` and |
| 8 | annotated a paragraph with the moment 500 ms. The recording attachment |
| 9 | (`page::Attachment::recording`) and the annotation |
| 10 | (`PageParagraph::media`) are read from the page and kept through the edit; |
| 11 | a model that drops the recording refuses to write. `corpus/recording` covers |
| 12 | writing recordings and links. |
| 13 | |
| 14 | `cold/` is a fresh OneNote 2010 read: `MediaFile`, `MediaReference` and |
| 15 | `MediaIndex` name the same recording and moment as before the edit, next to |
| 16 | the added paragraph. `tools/test_media_edit.py` checks this without a VM. |
| 17 | Regenerate with `ONESTORE_MEDIA_EXPORT` set to a new directory while running |
| 18 | the test, then cold-open with `--expected-pages 13 --collect-notebook`. |