Freeze actual Google music metadata and precise speech timing diagnostics

This commit is contained in:
karl committed 2026-10-13 18:11:07 +02:00
1 parent 8b4275d9b4
commit 6353d02c04
8 files changed
+440 -1

No files matched your search

+27
View File
@@ -62,3 +62,30 @@ English recording do not validate German speech or general transcription quality
Pinned CLI flag/output reference:
[upstream cli.cpp](https://github.com/ggml-org/whisper.cpp/blob/d1be6fde11ac6e0407606b4e42fe72d34add8037/examples/cli/cli.cpp).
## Frozen ordinary token-time comparison
`token-policy.json` declares an internal base-only comparison before inference.
Add `--token-sentences` to the existing command. The worker uses full JSON,
ordinary token timestamps and unchanged recognition flags; DTW is disabled.
The harness retains original raw JSON and segments, then adds exact recognized
sentence substrings and their token intervals in `aligned_segments`. No label
selects a sentence, source, word or start. All five sources and complete original
window coverage remain mandatory; empty speech is valid.
Structural tokens cannot become passage text. Ordinary text-token times must be
present, ordered and inside the source segment/window; reconstructed token text
must match original recognized bytes. Invalid alignment is retained as an error
and invalidates an accepted score. No clipping, invented time or omitted failing
competitor is permitted. Rankers must independently reconstruct these passages
from raw JSON and verify policy/contract provenance before publishing quality.
```powershell
$env:SEARCHI_FORCE_CPU = '1'
python tools/speech-eval/run.py --whisper .searchi/speech/build-cpu/bin/Release/whisper-cli.exe --whisper-sha256 12c681b4bcd9c7679b647b9a041e121a2f9e72cb2a9c6f189f529ec8b79c36f8 --ffmpeg .searchi/media-runtime/bin/ffmpeg.exe --ffprobe .searchi/media-runtime/bin/ffprobe.exe --model .searchi/speech/models/ggml-base.bin --candidate base --token-sentences --scratch-parent .searchi/speech/token-scratch --output .searchi/speech/base-token-sentences-v1.json
```
Run only with the coordinator's available CPU inference slot. The previous
base-only run took about 251 seconds including decode/process startup. Token
alignment has not yet been timed; each ASR process retains the 600-second limit.
No production behavior or quality claim follows from structural tests.