v1.23.1
canticle v1.23.1
v1.23.0 said the audio detector's result count would climb several-fold the moment you upgraded. On the dashboard, where you would actually look for it, nothing moved. This release makes that true.
The count lives in two places. The Prometheus metrics read one of them and the dashboard reads the other, and v1.23.0 only corrected the first. So the detector's tile carried on reporting a few hundred results against several thousand real ones, exactly as before the upgrade. The correction now covers both, and arrives with the upgrade rather than waiting on a command nobody knew to run.
On a decent-sized library the detector's tile climbs sharply the first time you start this version, then settles. That is the correction landing, and it does not repeat.
What's changed
Fixed
- The dashboard's provider-effectiveness tile now credits the audio detector for tracks it settled before it became a tracked source. v1.23.0 corrected only the Prometheus counters, leaving the dashboard unchanged and its promise of a jump unfulfilled (#537)
Upgrading
Nothing to do. The correction runs during the database upgrade on first start, applies once, and records that it has run.
If you already ran canticle scan reconcile-detector-stats by hand, nothing here disturbs it. Attempts recorded live always take precedence over reconstructed ones, so the upgrade fills only what is genuinely missing.
Detector failures remain a known gap and are still not reconstructed: canticle knows how many times a track was passed over but not when, and the detector has not always existed, so some of those attempts predate it. Filling that in would mean crediting work to something that was not running yet. The Prometheus metrics and the dashboard tile will therefore still disagree about the detector's failures, on purpose.
Docker: docker pull ghcr.io/sydlexius/canticle:1.23.1
Full changelog: v1.23.0...v1.23.1