Skip to content

VIGIL v0.1.4 — the watch does not stop for a dialog

Latest

Choose a tag to compare

@mogglemoss mogglemoss released this 14 Sep 22:40
FORM OSW-01 (RETROSPECTIVE ATTESTATION)

THE WATCH DOES NOT STOP FOR PAPERWORK,
AND A RECORD INTERRUPTED IS STILL A RECORD.

Replace v0.1.3 if you have it. Two faults in that build, both found the hard way on macOS 27, both capable of losing a clip.

The freeze

After a macOS update, EVE's next launch re-prompts for VIGIL's audio grant. In the gap before you approve, the tap delivers silence — and v0.1.3 put up a modal dialog about it on the main thread. Behind a fullscreen game nobody can see that dialog, let alone click it, and while it waits nothing else runs: the overlay sticks on screen, the menu greys out including Quit, the hotkeys go dead, and a clip that was open stays open.

Confirmed by sampling the process: the main thread inside -[NSAlert runModal], behind EVE, with a record still rolling.

The notice is now a floating, non-activating panel that draws above a fullscreen Space, never takes focus, and lets the watch run underneath it. And the check that raised it counts eight seconds from the tap's last attach rather than from app start — a watch that waited an hour for EVE was otherwise raising it one tick after attaching, before a single buffer could have arrived.

The rule, now written into the code: nothing on the main thread may block waiting for a click.

The loss

An 870 MB clip was killed mid-recording — pkill sends SIGTERM, and only SIGINT was handled. What was left was an mdat with no index: no way in without untrunc, a reference clip, and guessed timing.

Two fixes, both proven by killing a running watch mid-clip:

  • SIGTERM files an open clip on the way out, exactly as Ctrl-C does. That's pkill, Activity Monitor, logout and shutdown. Verified: 12.6 s of a 13 s clip, finalised and readable.
  • The writer fragments every four seconds. A finalised file is a normal MP4 and edits like one. An unfinalised one — crash, power loss, SIGKILL, anything that never reaches finish() — is readable up to its last fragment instead of being nothing. Verified under SIGKILL, which no handler can catch: 8.0 s readable of ~10. Four seconds lost instead of all of it.

Also since v0.1.3

  • Clips are named for whoever was flying, read fresh from the client's window title each time a record is struck.
  • The pilot's name has its own row in the overlay.
  • The menu bar distinguishes waiting from buffering, and the glyph turns red with a clock while a record is open.
  • Stand at login in Standing Orders.
  • The audio tap rebuilds when the default output device moves.

Installing

Still ad-hoc signed and not notarised. Gatekeeper refuses it on first open and, since macOS 15, Control-click no longer overrides that: open it, let it be refused, then System Settings › Privacy & Security › Open Anyway. Permissions must be granted again after each update. A Developer ID ends that and is pending.

On macOS 27, expect one more approval prompt the first time EVE launches with VIGIL standing. Approve it; the watch keeps standing while you do.

Still true

  • One watch at a time.
  • A real display sleep has never been sat through — only the recovery path it takes, forced deliberately.
  • Still not flown through a fleet fight.

Not affiliated with or endorsed by Fenris Creations. EVE Online and all related marks are the intellectual property of Fenris Creations (formerly CCP hf.).