Preset directory watching via CLAP's invalidation factory #8

New issue

Closed

opened 2026-08-18 01:34:39 +00:00 by bcox · 0 comments

bcox commented

2026-08-18 01:34:39 +00:00

Owner

CLAP has a mechanism for exactly this — clap_plugin_invalidation_factory —
and the design spec parks it deliberately:

Watching the preset directory for changes. CLAP has an invalidation
factory for exactly this, and a host may re-index on its own. Adding it
before anyone has a library worth re-indexing is speculative.

That judgement still holds, but the workflow this project is built around —
author in the standalone editor, load in the DAW — is precisely the one where
it would be felt. Worth revisiting once there are enough presets that
re-scanning by hand is annoying.

Small in scope: a second entry-level factory reporting the files whose
modification invalidates the index.

The preset-discovery provider declares one location and the host crawls it. Nothing tells the host when the contents change, so a preset saved from the standalone editor while the DAW is open will not appear in its browser until the host re-indexes on its own. CLAP has a mechanism for exactly this — `clap_plugin_invalidation_factory` — and the design spec parks it deliberately: > **Watching the preset directory for changes.** CLAP has an invalidation > factory for exactly this, and a host may re-index on its own. Adding it > before anyone has a library worth re-indexing is speculative. That judgement still holds, but the workflow this project is built around — author in the standalone editor, load in the DAW — is precisely the one where it would be felt. Worth revisiting once there are enough presets that re-scanning by hand is annoying. Small in scope: a second entry-level factory reporting the files whose modification invalidates the index.