docs: clarify FunASR rolling context behavior
This commit is contained in:
@@ -132,7 +132,7 @@ uv run --directory SKILL_DIR/scripts/transcription funasr-nano VIDEO_PATH --list
|
||||
|
||||
Where `VIDEO_DIR` is the directory containing the video file, `SKILL_DIR` is the skill installation directory, and `AUDIO_LANGUAGE_CODE` is the explicit transcription language (for example `zh` for Mandarin Chinese).
|
||||
|
||||
**Context and hotwords:** Fun-ASR-Nano is an LLM-based ASR model and upstream code supports prompt-style `language` and `hotwords` hints. However, do not assume the current bundled script automatically performs cross-segment semantic correction: it currently passes `language` / `use_itn`, but does not pass external hotwords or rolling `prev_text` context between VAD segments. If the video contains known game terms, names, locations, item names, or other jargon, ask the user for a hotword list or derive candidate terms and confirm them before transcription. See `references/funasr-nano-context-hotwords.md`. Hotwords are biasing hints, not a substitute for final manual checking.
|
||||
**Rolling context / semantic correction:** Fun-ASR-Nano has upstream support for `prev_text`-style rolling context in streaming/incremental examples: earlier stabilized text can be fed back as context for later decoding, similar to a 2-pass-style refinement. However, do not assume the current bundled offline script automatically enables whole-file rolling semantic correction: it currently calls ordinary `AutoModel.generate(...)` on the extracted WAV and does not run a cumulative chunked pass with `prev_text`. See `references/funasr-nano-rolling-context.md`. Treat the current transcript as a strong baseline, not the final word when unclear speech or homophones matter.
|
||||
|
||||
**Common OBS multi-track audio layouts.** When the user says "multi-track" or mentions OBS recording, these are the typical stream layouts:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user