Web Quick Start
- Chrome & Chromium-based browsers
- Picovoice Account and AccessKey
- Node.js 14+
Picovoice Account & AccessKey
Signup or Login to Picovoice Console to get your
Make sure to keep your
Rhino you'll need a
Rhino context file (
.rhn) as well as a
model file (
.pv). Place these files in the project's
public directory or generate a base64 representation of the file using the built-in script:
Pass the path to the file (relative to the public directory) or use the base64 string:
RhinoWorker that infers intent from spoken commands within
a given context:
RhinoWorker to WebVoiceProcessor to pass audio to the Rhino engine:
Once done, unsubscribe to stop processing audio frames:
Release resources explicitly when done with Rhino:
Create custom contexts in the Picovoice Console using
the Rhino Grammar. Train and download a Rhino context file (
.rhn) for the target platform
Web (WASM). This model file can be used directly with
publicPath, but, if
base64 is preferable, convert the
.rhn file to a base64
Similar to the model file (
.pv), context files (
.rhn) are saved in IndexedDB to be used by Web Assembly. Either
publicPath must be set for the context to instantiate Rhino.
If both are set, Rhino will use the
In order to use Rhino with different languages you need to use the corresponding model file (
.pv) for the desired language.
The model files for all supported languages are available in the Rhino GitHub repository.
For the Rhino Web SDK, there is a Web demo project available on the Rhino GitHub repository.
Clone the Rhino repository from GitHub:
- Install dependencies and run:
- Open http://localhost:5000 to view it in the browser.