k2-fsa/sherpa-onnx: README-based editorial guide

k2-fsa/sherpa-onnx describes itself in the README as "Speech-to-text, text-to-speech, speaker diarization, speech enhancement, source separation, and VAD using next-gen Kaldi with onnxruntime without Internet connection.". This article keeps to facts that can be checked in the repository. Stars, forks, and promotional badges are signals of attention, not proof of quality. Under "Supported functions", the README says: |Speech recognition| [Speech synthesis][tts-url] | [Source separation][ss-url] | |------------------|------------------|-------------------| | ✔️ | ✔️ | ✔️ |. That establishes the project's stated boundary, not a production test.

The README's "Introduction" section gives a useful starting point for deciding whether the project fits: Speech enhancement (e.g., [gtcrn][gtcrn], DPDFNet. If that problem is not yours, popularity is a poor reason to adopt it. Project names, commands, and component names are kept as written so a reader can return to the primary source without guessing at terminology. Another checkable README item is: Speech-to-text (i.e., ASR); both streaming and non-streaming are supported. It can shape a first test, but it does not replace testing in the intended environment.

The operating model is spread across sections such as "Supported functions". The source evidence includes: | [Spoken Language identification][slid-url] | [Audio tagging][at-url] | [Voice activity detection][vad-url] | |--------------------------------|---------------|--------------------------| | ✔️ | ✔️ | ✔️ |. This article does not turn missing architecture, performance, or security details into claims. A real deployment still needs a look at the repository layout, configuration files, and release history.

Start installation from the README's documented entry point. A command that can be checked in the source is: README 没有给出可直接复制的安装命令。 When the README contains no runnable command, this article does not invent one. Open its "Supported platforms" section and confirm system dependencies, default ports, and first-run initialization before using a public server.