Explain balanced result blending, user filters and plugin-only deployment

This commit is contained in:
Sleeps
2026-10-08 15:32:45 +01:00
parent 21fe3a4502
commit 07ee584b75
+17 -8
View File
@@ -587,7 +587,7 @@ Open **Dashboard → Plugins → Scene Search** and configure:
- API URL: `http://127.0.0.1:8097` when Jellyfin and scene-search run on the same machine.
- API key: the same value as `SCENE_API_KEY`.
- Require a search prefix: enabled by default.
- Search participation: normal queries work without any required prefix.
- Prefix: `scene:`.
- Indexed libraries: tick the Jellyfin libraries that Scene Search should manage.
@@ -611,11 +611,16 @@ Plugin-triggered indexing reuses the API process's existing SigLIP instance and
Normal Jellyfin searches now combine external providers, including the separate
Jellyfin Meilisearch plugin and Scene Search. Hybrid visual similarity still
finds semantic scenes; a separate caption-only text query ensures that literal
caption phrases are not buried below millions of visual frame matches. At
most two distinct exact-caption items receive a tiny reserved score boost
above normal Meilisearch scores (0–1), leaving most results for normal title
and other provider matches. This runs against the **existing** Meilisearch
documents and does **not** require re-captioning or a full Meilisearch rebuild.
caption phrases are not buried below millions of visual frame matches. The
Scene Search provider reserves **up to half of Jellyfin's requested result
slots, capped at ten**, for its top grouped website/API matches (including up
to two exact-caption matches). Those promoted items appear in the same order
as the standalone website, just above the other Meilisearch plugin's scores
(0–1). The remaining slots still include normal title and other-provider
matches. Jellyfin additionally filters matches by item type and the current
user's library permissions, and smaller autocomplete result limits mean fewer
reserved scene slots. This uses the **existing** Meilisearch documents and
does **not** require re-captioning or another index rebuild.
The optional `scene:` prefix still gives Scene Search stronger preference and
is stripped before querying the backend:
@@ -635,8 +640,12 @@ captions. An item can have a saved caption in `caption_windows` while its
caption into the serving index.
If the API returns caption matches but Jellyfin does not, check the diagnostics
for `API/core overlap` and `Resolved in Jellyfin DB`, and check that both the
Docker Scene Search service and the Jellyfin plugin DLL were updated. Caption
for `API/core overlap` and `Resolved in Jellyfin DB`. The API displays its
own top results; Jellyfin merges external providers, applies a result cap,
and can filter inaccessible or ineligible items. Check that the updated plugin
DLL is installed and Jellyfin has been restarted. **A plugin-only score
change does not require rebuilding the Docker service**, which matters if
an incremental Meilisearch index repair is currently running. Caption
synchronisation progress and any failures appear in the caption job status.
The first version contributes Movies, Episodes and generic Videos because those are the item types currently ingested by `jellyfin-index`.