@sorisdk/matcher 0.6.0 → 0.6.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +3 -1
- package/dist/generated/core_bg.wasm +0 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -74,7 +74,9 @@ If you want campaign events and browser recognition flow on top of matching, use
|
|
|
74
74
|
Audiopack footer metadata is available through explicit lookup rather than being
|
|
75
75
|
embedded in `MatchResult`. Segment timing is the exception: when a pack provides
|
|
76
76
|
valid `matcherSegments` metadata, `MatchResult.position` is segment-local and
|
|
77
|
-
`MatchResult.durationMillis` contains the matched segment duration.
|
|
77
|
+
`MatchResult.durationMillis` contains the matched segment duration. For packs
|
|
78
|
+
whose stored AFP starts after a small leading extractor warmup gap, the matcher
|
|
79
|
+
infers that gap before checking the source-time segment ranges.
|
|
78
80
|
|
|
79
81
|
```ts
|
|
80
82
|
const best = await session.bestMatch(queryBytes);
|
|
Binary file
|