Soundpacks and factory content #11

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

Status: excluded by design during the preset-transport spec. Filed for the
record.

The discovery provider declares one filetype and one user-content location. It
declares no soundpacks and no factory-content location. From the spec:

Soundpacks and factory content. We ship no presets.

plugin/preset_provider.h carries the same reasoning: declaring an empty
factory location would show the user an empty folder in the browser, which is
worse than no folder.

This becomes worth doing the moment the project ships presets with the plugin —
at which point the provider gains a second location flagged
CLAP_PRESET_DISCOVERY_IS_FACTORY_CONTENT, and possibly a soundpack
declaration to group them. The code is already shaped for it; ProviderInit
declares locations in a loop of one.

Depends on someone authoring presets worth shipping.

**Status: excluded by design during the preset-transport spec. Filed for the record.** The discovery provider declares one filetype and one user-content location. It declares no soundpacks and no factory-content location. From the spec: > **Soundpacks and factory content.** We ship no presets. `plugin/preset_provider.h` carries the same reasoning: declaring an empty factory location would show the user an empty folder in the browser, which is worse than no folder. This becomes worth doing the moment the project ships presets with the plugin — at which point the provider gains a second location flagged `CLAP_PRESET_DISCOVERY_IS_FACTORY_CONTENT`, and possibly a soundpack declaration to group them. The code is already shaped for it; `ProviderInit` declares locations in a loop of one. Depends on someone authoring presets worth shipping.