fix: lock PyTorch CUDA builds for transcription
This commit is contained in:
@@ -291,7 +291,7 @@ Use whatever vision capability the agent's runtime provides to analyze extracted
|
||||
|
||||
- **Which model** to use (depends on the agent's runtime and available vision capabilities).
|
||||
- **Batch size** — depends on the model's context window. See `references/frame-extraction-guide.md` for token cost estimates at different resolutions.
|
||||
- **Windows setup troubleshooting** — see `references/windows-funasr-uv-setup.md` for Windows-host PowerShell transcription commands and uv/Python wheel issues such as `editdistance` source builds.
|
||||
- **Windows setup troubleshooting** — see `references/windows-funasr-uv-setup.md` for Windows-host PowerShell transcription commands, Python wheel issues such as `editdistance` source builds, and PyTorch CUDA-vs-CPU build checks.
|
||||
- **How many frames** per analysis pass — use the binary-search approach from Step 6.
|
||||
|
||||
**Completion criteria:** the agent has enough visual understanding to answer the user's question or produce the requested edit plan.
|
||||
|
||||
Reference in New Issue
Block a user