Made in Vancouver, Canada by Picovoice
Picovoice is the end-to-end platform for building voice products on your terms. Unlike Alexa and Google services, Picovoice runs entirely on-device while being more accurate. Using Picovoice, one can infer a user’s intent from a naturally spoken utterance such as:
"Hey Edison, set the lights in the living room to blue"
Picovoice detects the occurrence of the custom wake word (Hey Edison), and then extracts the intent from the follow-on
spoken command:
{
"intent": "changeColor",
"slots": {
"location": "living room",
"color": "blue"
}
}- Private & Secure: Everything is processed offline. Intrinsically private; HIPAA and GDPR-compliant.
- Accurate: Resilient to noise and reverberation. Outperforms cloud-based alternatives by wide margins.
- Cross-Platform: Design once, deploy anywhere. Build using familiar languages and frameworks.
- Arm Cortex-M, STM32, Arduino, and i.MX RT
- Raspberry Pi, NVIDIA Jetson Nano, and BeagleBone
- Android and iOS
- Chrome, Safari, Firefox, and Edge
- Linux (x86_64), macOS (x86_64, arm64), and Windows (x86_64)
- Self-Service: Design, train, and test voice interfaces instantly in your browser, using Picovoice Console.
- Reliable: Runs locally without needing continuous connectivity.
- Zero Latency: Edge-first architecture eliminates unpredictable network delay.
-
Evaluate: The Picovoice SDK is a cross-platform library for adding voice to anything. It includes some pre-trained speech models. The SDK is licensed under Apache 2.0 and available on GitHub to encourage independent benchmarking and integration testing. You are empowered to make a data-driven decision.
-
Design: Picovoice Console is a cloud-based platform for designing voice interfaces and training speech models, all within your web browser. No machine learning skills are required. Simply describe what you need with text and export trained models.
-
Develop: Exported models can run on Picovoice SDK without requiring constant connectivity. The SDK runs on a wide range of platforms and supports a large number of frameworks. The Picovoice Console and Picovoice SDK enable you to design, build and iterate fast.
-
Deploy: Deploy at scale without having to maintain complex cloud infrastructure. Avoid unbounded cloud fees, limitations, and control imposed by big tech.
Picovoice makes use of the Porcupine wake word engine to detect utterances of given wake phrases. You can train custom wake words using Picovoice Console and then run the exported wake word model on the Picovoice SDK.
Picovoice relies on the Rhino Speech-to-Intent engine to directly infer user's intent from spoken commands within a given domain of interest (a "context"). You can design and train custom contexts for your product using Picovoice Console. The exported Rhino models then can run with the Picovoice SDK on any supported platform.
- Picovoice
- English, German, French, Spanish, Italian, Japanese, Korean, and Portuguese.
- Support for additional languages is available for commercial customers on a case-by-case basis.
Picovoice makes use of the Porcupine wake word engine to detect utterances of given wake phrases. An open-source benchmark of Porcupine is available here. In summary, compared to the best-performing alternative, Porcupine's standard model is 5.4 times more accurate.
Picovoice relies on the Rhino Speech-to-Intent engine to directly infer user's intent from spoken commands within a given domain of interest (a "context"). An open-source benchmark of Rhino is available here. Rhino outperforms all major cloud-based alternatives with wide margins.
Picovoice Console is a web-based platform for designing, testing, and training voice user interfaces. Using Picovoice Console you can train custom wake word, and domain-specific NLU (Speech-to-Intent) models.
If using SSH, clone the repository with:
git clone --recurse-submodules [email protected]:Picovoice/picovoice.gitIf using HTTPS, clone the repository with:
git clone --recurse-submodules https://github.com/Picovoice/picovoice.gitsudo pip3 install picovoicedemoFrom the root of the repository run the following in the terminal:
picovoice_demo_mic \
--access_key ${ACCESS_KEY} \
--keyword_path resources/porcupine/resources/keyword_files/${PLATFORM}/porcupine_${PLATFORM}.ppn \
--context_path resources/rhino/resources/contexts/${PLATFORM}/smart_lighting_${PLATFORM}.rhnReplace ${PLATFORM} with the platform you are running the demo on (e.g. raspberry-pi, beaglebone, linux, mac,
or windows). The microphone demo opens an audio stream from the microphone, detects utterances of a given wake
phrase, and infers intent from the follow-on spoken command. Once the demo initializes, it prints [Listening ...]
to the console. Then say:
Porcupine, set the lights in the kitchen to purple.
Upon success, the demo prints the following into the terminal:
[wake word]
{
intent : 'changeColor'
slots : {
location : 'kitchen'
color : 'purple'
}
}
For more information regarding Python demos refer to their documentation.
Install the demo package:
npm install -g @picovoice/picovoice-node-demoFrom the root of the repository run:
pv-mic-demo \
--access_key ${ACCESS_KEY} \
-k resources/porcupine/resources/keyword_files/${PLATFORM}/porcupine_${PLATFORM}.ppn \
-c resources/rhino/resources/contexts/${PLATFORM}/smart_lighting_${PLATFORM}.rhnReplace ${PLATFORM} with the platform you are running the demo on (e.g. raspberry-pi, linux, or mac). The
microphone demo opens an audio stream from the microphone, detects utterances of a given wake
phrase, and infers intent from the follow-on spoken command. Once the demo initializes, it prints
Listening for wake word 'porcupine' ... to the console. Then say:
Porcupine, turn on the lights.
Upon success, the demo prints the following into the terminal:
Inference:
{
"isUnderstood": true,
"intent": "changeLightState",
"slots": {
"state": "on"
}
}
Please see the demo instructions for details.
From the root of the repository run the following in the terminal:
dotnet run -p demo/dotnet/PicovoiceDemo/PicovoiceDemo.csproj -c MicDemo.Release -- \
--access_key ${ACCESS_KEY} \
--keyword_path resources/porcupine/resources/keyword_files/${PLATFORM}/porcupine_${PLATFORM}.ppn \
--context_path resources/rhino/resources/contexts/${PLATFORM}/smart_lighting_${PLATFORM}.rhnReplace ${PLATFORM} with the platform you are running the demo on (e.g. linux, mac, or windows). The microphone
demo opens an audio stream from the microphone, detects utterances of a given wake phrase, and infers intent from the
follow-on spoken command. Once the demo initializes, it prints Listening... to the console. Then say:
Porcupine, set the lights in the kitchen to orange.
Upon success the following it printed into the terminal:
[wake word]
{
intent : 'changeColor'
slots : {
location : 'kitchen'
color : 'orange'
}
}
For more information about .NET demos go to demo/dotnet.
Make sure there is a working microphone connected to your device. Then invoke the following commands from the terminal:
cd demo/java
./gradlew build
cd build/libs
java -jar picovoice-mic-demo.jar \
-a ${ACCESS_KEY} \
-k resources/porcupine/resources/keyword_files/${PLATFORM}/porcupine_${PLATFORM}.ppn \
-c resources/rhino/resources/contexts/${PLATFORM}/smart_lighting_${PLATFORM}.rhnReplace ${PLATFORM} with the platform you are running the demo on (e.g. linux, mac, or windows). The microphone
demo opens an audio stream from the microphone, detects utterances of a given wake phrase, and infers intent from the
follow-on spoken command. Once the demo initializes, it prints Listening ... to the console. Then say:
Porcupine, set the lights in the kitchen to orange.
Upon success the following it printed into the terminal:
[wake word]
{
intent : 'changeColor'
slots : {
location : 'kitchen'
color : 'orange'
}
}
For more information about the Java demos go to demo/java.
The demos require cgo, which means that a gcc compiler like Mingw is required.
From demo/go run the following command from the terminal to build and run the mic demo:
go run micdemo/picovoice_mic_demo.go \
-access_key ${ACCESS_KEY} \
-keyword_path "../../resources/porcupine/resources/keyword_files/${PLATFORM}/porcupine_${PLATFORM}.ppn" \
-context_path "../../resources/rhino/resources/contexts/${PLATFORM}/smart_lighting_${PLATFORM}.rhn"Replace ${PLATFORM} with the platform you are running the demo on (e.g. linux, mac, or windows). The microphone
demo opens an audio stream from the microphone, detects utterances of a given wake phrase, and infers intent from the
follow-on spoken command. Once the demo initializes, it prints Listening ... to the console. Then say:
Porcupine, set the lights in the kitchen to orange.
Upon success the following it printed into the terminal:
[wake word]
{
intent : 'changeColor'
slots : {
location : 'kitchen'
color : 'orange'
}
}
For more information about the Go demos go to demo/go.
To run the Picovoice Unity demo, import the latest Picovoice Unity package into your project, open the PicovoiceDemo scene and hit play. To run on other platforms or in the player, go to File > Build Settings, choose your platform and hit the Build and Run button.
To browse the demo source go to demo/unity.
To run the Picovoice demo on Android or iOS with Flutter, you must have the Flutter SDK installed on your system. Once installed, you can run flutter doctor to determine any other missing requirements for your relevant platform. Once your environment has been set up, launch a simulator or connect an Android/iOS device.
Run the prepare_demo script from demo/flutter with a language code to set up the demo in the language of your
choice (e.g. de -> German, ko -> Korean). To see a list of available languages, run prepare_demo without a language code.
dart scripts/prepare_demo.dart ${LANGUAGE}Replace your AccessKey in lib/main.dart file:
final String accessKey = "{YOUR_ACCESS_KEY_HERE}"; // AccessKey obtained from Picovoice Console (https://console.picovoice.ai/)Run the following command from demo/flutter to build and deploy the demo to your device:
flutter runOnce the demo app has started, press the start button and utter a command to start inferring context. To see more details about the current context information, press the Context Info button on the top right corner in the app.
To run the React Native Picovoice demo app you'll first need to install yarn and set up your React Native environment. For this, please refer to React Native's documentation. Once your environment has been set up, you can run the following commands:
cd demo/react-native
yarn android-install # sets up environment
yarn android-run # builds and deploys to Androidcd demo/react-native
yarn ios-install # sets up environment
yarn ios-run # builds and deploys to iOSOnce the application has been deployed, press the start button and say
Porcupine, turn off the lights in the kitchen.
For the full set of supported commands refer to demo's readme.
Using Android Studio, open demo/android/Activity as an Android project and then run the application. Press the start button and say
Porcupine, turn off the lights in the kitchen.
For the full set of supported commands refer to demo's readme.
The BackgroundService demo runs audio recording in the background while the application is not in focus and remains running in the background. The ForegroundApp demo runs only when the application is in focus.
To run the demo, go to demo/ios/BackgroundService and run:
pod installThen, using Xcode, open the generated PicovoiceBackgroundServiceDemo.xcworkspace and paste your AccessKey into the ACCESS_KEY variable in ContentView.swift. Build and run the demo.
To run the demo, go to demo/ios/ForegroundApp and run:
pod installThen, using Xcode, open the generated PicovoiceForegroundAppDemo.xcworkspace and paste your AccessKey into the ACCESS_KEY variable in ContentView.swift. Build and run the demo.
After running the demo, press the start button and try saying the following:
Picovoice, shut of the lights in the living room.
For more details about the iOS demos and full set of supported commands refer to demo's readme.
From demo/web use yarn or npm to install the dependencies, and the start script with a language code
to start a local web server hosting the demo in the language of your choice (e.g. pl -> Polish, ko -> Korean).
To see a list of available languages, run start without a language code.
yarn
yarn start ${LANGUAGE}(or)
npm install
npm run start ${LANGUAGE}Open http://localhost:5000 in your browser to try the demo.
From demo/angular use yarn or npm to install the dependencies, and the start script with a language code
to start a local web server hosting the demo in the language of your choice (e.g. pl -> Polish, ko -> Korean).
To see a list of available languages, run start without a language code.
yarn
yarn start ${LANGUAGE}(or)
npm install
npm run start ${LANGUAGE}Open http://localhost:4200 in your browser to try the demo.
From demo/react use yarn or npm to install the dependencies, and the start script with a language code
to start a local web server hosting the demo in the language of your choice (e.g. pl -> Polish, ko -> Korean).
To see a list of available languages, run start without a language code.
yarn
yarn start ${LANGUAGE}(or)
npm install
npm run start ${LANGUAGE}Open http://localhost:3000 in your browser to try the demo.
From demo/vue use yarn or npm to install the dependencies, and the start script with a language code
to start a local web server hosting the demo in the language of your choice (e.g. pl -> Polish, ko -> Korean).
To see a list of available languages, run start without a language code.
yarn
yarn start ${LANGUAGE}(or)
npm install
npm run start ${LANGUAGE}The command-line output will provide you with a localhost link and port to open in your browser.
From demo/rust/micdemo run the following command from the terminal to build and run the mic demo:
cargo run --release -- \
--keyword_path "../../../resources/porcupine/resources/keyword_files/${PLATFORM}/porcupine_${PLATFORM}.ppn" \
--context_path "../../../resources/rhino/resources/contexts/${PLATFORM}/smart_lighting_${PLATFORM}.rhn"Replace ${PLATFORM} with the platform you are running the demo on (e.g. linux, mac, or windows).
The microphone demo opens an audio stream from the microphone, detects utterances of a given wake phrase, and infers intent from the follow-on spoken command.
Once the demo initializes, it prints Listening ... to the console.
Then say:
Porcupine, set the lights in the kitchen to orange.
Upon success the following it printed into the terminal:
[wake word]
{
intent : 'changeColor'
slots : {
location : 'kitchen'
color : 'orange'
}
}
For more information about the Rust demos go to demo/rust.
The C demo requires CMake version 3.4 or higher.
The Microphone demo requires miniaudio for accessing microphone audio data.
Windows Requires MinGW to build the demo.
At the root of the repository, build with:
cmake -S demo/c/. -B demo/c/build && cmake --build demo/c/build --target picovoice_demo_micList input audio devices with:
./demo/c/build/picovoice_demo_mic --show_audio_devicesRun the demo using:
./demo/c/build/picovoice_demo_mic \
-a ${ACCESS_KEY}
-l ${PICOVOICE_LIBRARY_PATH} \
-p resources/porcupine/lib/common/porcupine_params.pv \
-k resources/porcupine/resources/keyword_files/${PLATFORM}/picovoice_${PLATFORM}.ppn \
-r resources/rhino/lib/common/rhino_params.pv \
-c resources/rhino/resources/contexts/${PLATFORM}/smart_lighting_${PLATFORM}.rhn \
-i {AUDIO_DEVICE_INDEX}Replace ${LIBRARY_PATH} with path to appropriate library available under /sdk/c/lib, ${PLATFORM} with the
name of the platform you are running on (linux, raspberry-pi, mac, or beaglebone), and ${AUDIO_DEVICE_INDEX} with
the index of your audio device.
List input audio devices with:
.\\demo\\c\\build\\picovoice_demo_mic.exe --show_audio_devicesRun the demo using:
.\\demo\\c\\build\\picovoice_demo_mic.exe -a ${ACCESS_KEY} -l sdk/c/lib/windows/amd64/libpicovoice.dll -p resources/porcupine/lib/common/porcupine_params.pv -k resources/porcupine/resources/keyword_files/windows/picovoice_windows.ppn -r resources/rhino/lib/common/rhino_params.pv -c resources/rhino/resources/contexts/windows/smart_lighting_windows.rhn -i {AUDIO_DEVICE_INDEX}Replace ${AUDIO_DEVICE_INDEX} with the index of your audio device.
The demo opens an audio stream and waits for the wake word "Picovoice" to be detected. Once it is detected, it infers your intent from spoken commands in the context of a smart lighting system. For example, you can say:
"Turn on the lights in the bedroom."
At the root of the repository, build with:
cmake -S demo/c/. -B demo/c/build && cmake --build demo/c/build --target picovoice_demo_fileRun the demo using:
./demo/c/build/picovoice_demo_file \
-a ${ACCESS_KEY}
-l ${LIBRARY_PATH} \
-p resources/porcupine/lib/common/porcupine_params.pv \
-k resources/porcupine/resources/keyword_files/${PLATFORM}/picovoice_${PLATFORM}.ppn \
-r resources/rhino/lib/common/rhino_params.pv \
-c resources/rhino/resources/contexts/${PLATFORM}/coffee_maker_${PLATFORM}.rhn \
-w resources/audio_samples/picovoice-coffee.wavReplace ${LIBRARY_PATH} with path to appropriate library available under sdk/c/lib, ${PLATFORM} with the
name of the platform you are running on (linux, raspberry-pi, mac, or beaglebone).
Run the demo using:
.\\demo\\c\\build\\picovoice_demo_file.exe -a ${ACCESS_KEY} -l sdk/c/lib/windows/amd64/libpicovoice.dll -p resources/porcupine/lib/common/porcupine_params.pv -k resources/porcupine/resources/keyword_files/windows/picovoice_windows.ppn -r resources/rhino/lib/common/rhino_params.pv -c resources/rhino/resources/contexts/windows/coffee_maker_windows.rhn -w resources/audio_samples/picovoice-coffee.wavThe demo opens up the WAV file. It detects the wake word and infers the intent in the context of a coffee maker system.
For more information about C demos go to demo/c.
There are several projects for various development boards inside the mcu demo folder.
Install the package:
pip3 install picovoiceCreate a new instance of Picovoice:
from picovoice import Picovoice
access_key = "${ACCESS_KEY}" # AccessKey obtained from Picovoice Console (https://console.picovoice.ai/)
keyword_path = ...
def wake_word_callback():
pass
context_path = ...
def inference_callback(inference):
print(inference.is_understood)
print(inference.intent)
print(inference.slots)
handle = Picovoice(
access_key=access_key,
keyword_path=keyword_path,
wake_word_callback=wake_word_callback,
context_path=context_path,
inference_callback=inference_callback)handle is an instance of the Picovoice runtime engine. It detects utterances of wake phrase defined in the file located at
keyword_path. Upon detection of wake word it starts inferring user's intent from the follow-on voice command within
the context defined by the file located at context_path. keyword_path is the absolute path to the
Porcupine wake word engine keyword file (with .ppn extension).
context_path is the absolute path to the Rhino Speech-to-Intent engine context file
(with .rhn extension). wake_word_callback is invoked upon the detection of wake phrase and inference_callback is
invoked upon completion of follow-on voice command inference.
When instantiated, the required rate can be obtained via handle.sample_rate. Expected number of audio samples per
frame is handle.frame_length. The engine accepts 16-bit linearly-encoded PCM and operates on single-channel audio. The
set of supported commands can be retrieved (in YAML format) via handle.context_info.
def get_next_audio_frame():
pass
while True:
handle.process(get_next_audio_frame())When done, resources have to be released explicitly handle.delete().
The Picovoice SDK for NodeJS is available from NPM:
yarn add @picovoice/picovoice-node(or)
npm install @picovoice/picovoice-nodeThe SDK provides the Picovoice class. Create an instance of this class using a Porcupine keyword (with .ppn extension)
and Rhino context file (with .rhn extension), as well as callback functions that will be invoked on wake word detection
and command inference completion events, respectively:
const Picovoice = require("@picovoice/picovoice-node");
const accessKey = "${ACCESS_KEY}"; // Obtained from the Picovoice Console (https://console.picovoice.ai/)
let keywordCallback = function (keyword) {
console.log(`Wake word detected`);
};
let inferenceCallback = function (inference) {
console.log("Inference:");
console.log(JSON.stringify(inference, null, 4));
};
let handle = new Picovoice(
accessKey,
keywordArgument,
keywordCallback,
contextPath,
inferenceCallback
);The keywordArgument can either be a path to a Porcupine keyword file (.ppn), or one of the built-in keywords
(integer enums). The contextPath is the path to the Rhino context file (.rhn).
Upon constructing the Picovoice class, send it frames of audio via its process method. Internally, Picovoice will
switch between wake word detection and inference. The Picovoice class includes frameLength and sampleRate properties
for the format of audio required.
// process audio frames that match the Picovoice requirements (16-bit linear pcm audio, single-channel)
while (true) {
handle.process(frame);
}As the audio is processed through the Picovoice engines, the callbacks will fire.
You can install the latest version of Picovoice by adding the latest Picovoice NuGet package in Visual Studio or using the .NET CLI.
dotnet add package PicovoiceTo create an instance of Picovoice, do the following:
using Pv;
const string accessKey = "${ACCESS_KEY}"; // obtained from Picovoice Console (https://console.picovoice.ai/)
string keywordPath = "/absolute/path/to/keyword.ppn";
void wakeWordCallback() => {..}
string contextPath = "/absolute/path/to/context.rhn";
void inferenceCallback(Inference inference)
{
// `inference` exposes three immutable properties:
// (1) `IsUnderstood`
// (2) `Intent`
// (3) `Slots`
// ..
}
Picovoice handle = Picovoice.Create(accessKey,
keywordPath,
wakeWordCallback,
contextPath,
inferenceCallback);handle is an instance of Picovoice runtime engine that detects utterances of wake phrase defined in the file located at
keywordPath. Upon detection of wake word it starts inferring user's intent from the follow-on voice command within
the context defined by the file located at contextPath. accessKey is your Picovoice AccessKey. keywordPath is the absolute path to
Porcupine wake word engine keyword file (with .ppn extension).
contextPath is the absolute path to Rhino Speech-to-Intent engine context file
(with .rhn extension). wakeWordCallback is invoked upon the detection of wake phrase and inferenceCallback is
invoked upon completion of follow-on voice command inference.
When instantiated, the required sample rate can be obtained via handle.SampleRate. The expected number of audio samples per
frame is handle.FrameLength. The Picovoice engine accepts 16-bit linearly-encoded PCM and operates on single-channel audio.
short[] GetNextAudioFrame()
{
// .. get audioFrame
return audioFrame;
}
while(true)
{
handle.Process(GetNextAudioFrame());
}Picovoice will have its resources freed by the garbage collector, but to have resources freed immediately after use, wrap it in a using statement:
using(Picovoice handle = Picovoice.Create(accessKey, keywordPath, wakeWordCallback, contextPath, inferenceCallback))
{
// .. Picovoice usage here
}The Picovoice Java library is available from Maven Central at ai.picovoice:picovoice-java:${version}.
The easiest way to create an instance of the engine is with the Picovoice Builder:
import ai.picovoice.picovoice.*;
String keywordPath = "/absolute/path/to/keyword.ppn";
final String accessKey = "${ACCESS_KEY}"; // AccessKey obtained from [Picovoice Console](https://console.picovoice.ai/)
PicovoiceWakeWordCallback wakeWordCallback = () -> {..};
String contextPath = "/absolute/path/to/context.rhn";
PicovoiceInferenceCallback inferenceCallback = inference -> {
// `inference` exposes three getters:
// (1) `getIsUnderstood()`
// (2) `getIntent()`
// (3) `getSlots()`
// ..
};
try {
Picovoice handle = new Picovoice.Builder()
.setAccessKey(accessKey)
.setKeywordPath(keywordPath)
.setWakeWordCallback(wakeWordCallback)
.setContextPath(contextPath)
.setInferenceCallback(inferenceCallback)
.build();
} catch (PicovoiceException e) { }handle is an instance of the Picovoice runtime engine that detects utterances of wake phrase defined in the file located at
keywordPath. Upon detection of wake word it starts inferring the user's intent from the follow-on voice command within
the context defined by the file located at contextPath. keywordPath is the absolute path to
Porcupine wake word engine keyword file (with .ppn extension).
contextPath is the absolute path to Rhino Speech-to-Intent engine context file
(with .rhn extension). wakeWordCallback is invoked upon the detection of wake phrase and inferenceCallback is
invoked upon completion of follow-on voice command inference.
When instantiated, the required sample rate can be obtained via handle.getSampleRate(). The expected number of audio samples per
frame is handle.getFrameLength(). The Picovoice engine accepts 16-bit linearly-encoded PCM and operates on single-channel audio.
short[] getNextAudioFrame()
{
// .. get audioFrame
return audioFrame;
}
while(true)
{
handle.process(getNextAudioFrame());
}Once you're done with Picovoice, ensure you release its resources explicitly:
handle.delete();To install the Picovoice Go module to your project, use the command:
go get github.com/Picovoice/picovoice/sdk/goTo create an instance of the engine with default parameters, use the NewPicovoice function. You must provide a Porcupine keyword file, a wake word detection callback function, a Rhino context file and an inference callback function. You must then make a call to Init().
. "github.com/Picovoice/picovoice/sdk/go/v2"
rhn "github.com/Picovoice/rhino/binding/go/v2"
const accessKey string = "${ACCESS_KEY}" // obtained from Picovoice Console (https://console.picovoice.ai/)
keywordPath := "/path/to/keyword/file.ppn"
wakeWordCallback := func() {
// let user know wake word detected
}
contextPath := "/path/to/keyword/file.rhn"
inferenceCallback := func(inference rhn.RhinoInference) {
if inference.IsUnderstood {
intent := inference.Intent
slots := inference.Slots
// add code to take action based on inferred intent and slot values
} else {
// add code to handle unsupported commands
}
}
picovoice := NewPicovoice(
accessKey,
keywordPath,
wakeWordCallback,
contextPath,
inferenceCallback)
err := picovoice.Init()
if err != nil {
// handle error
}Upon detection of wake word defined by keywordPath it starts inferring user's intent from the follow-on voice command within
the context defined by the file located at contextPath. accessKey is your Picovoice AccessKey. keywordPath is the absolute path to
Porcupine wake word engine keyword file (with .ppn suffix).
contextPath is the absolute path to Rhino Speech-to-Intent engine context file
(with .rhn suffix). wakeWordCallback is invoked upon the detection of wake phrase and inferenceCallback is
invoked upon completion of follow-on voice command inference.
When instantiated, valid sample rate can be obtained via SampleRate. Expected number of audio samples per
frame is FrameLength. The engine accepts 16-bit linearly-encoded PCM and operates on single-channel audio.
func getNextFrameAudio() []int16 {
// get audio frame
}
for {
err := picovoice.Process(getNextFrameAudio())
}When done resources have to be released explicitly
picovoice.Delete()Import the latest Picovoice Unity Package into your Unity project.
The SDK provides two APIs:
PicovoiceManager provides a high-level API that takes care of audio recording. This is the quickest way to get started.
The constructor PicovoiceManager.Create will create an instance of the PicovoiceManager using the Porcupine keyword and Rhino context files that you pass to it.
using Pv.Unity;
PicovoiceManager _picovoiceManager = new PicovoiceManager(
"/path/to/keyword/file.ppn",
() => {},
"/path/to/context/file.rhn",
(inference) => {};Once you have instantiated a PicovoiceManager, you can start/stop audio capture and processing by calling:
try
{
_picovoiceManager.Start();
}
catch(Exception ex)
{
Debug.LogError(ex.ToString());
}
// .. use picovoice
_picovoiceManager.Stop();PicovoiceManager uses our unity-voice-processor Unity package to capture frames of audio and automatically pass it to the Picovoice platform.
Picovoice provides low-level access to the Picovoice platform for those who want to incorporate it into an already existing audio processing pipeline.
Picovoice is created by passing a Porcupine keyword file and Rhino context file to the Create static constructor.
using Pv.Unity;
try
{
Picovoice _picovoice = Picovoice.Create(
"path/to/keyword/file.ppn",
OnWakeWordDetected,
"path/to/context/file.rhn",
OnInferenceResult);
}
catch (Exception ex)
{
// handle Picovoice init error
}To use Picovoice, you must pass frames of audio to the Process function. The callbacks will automatically trigger when the wake word is detected and then when the follow-on command is detected.
short[] GetNextAudioFrame()
{
// .. get audioFrame
return audioFrame;
}
short[] buffer = GetNextAudioFrame();
try
{
_picovoice.Process(buffer);
}
catch (Exception ex)
{
Debug.LogError(ex.ToString());
}For Process to work correctly, the provided audio must be single-channel and 16-bit linearly-encoded.
Picovoice implements the IDisposable interface, so you can use Picovoice in a using block. If you don't use a using block, resources will be released by the garbage collector automatically, or you can explicitly release the resources like so:
_picovoice.Dispose();Add the Picovoice Flutter package to your pub.yaml.
dependencies:
picovoice: ^<version>The SDK provides two APIs:
PicovoiceManager provides a high-level API that takes care of audio recording. This class is the quickest way to get started.
The static constructor PicovoiceManager.create will create an instance of a PicovoiceManager using a Porcupine keyword file and Rhino context file that you pass to it.
import 'package:picovoice/picovoice_manager.dart';
import 'package:picovoice/picovoice_error.dart';
final String accessKey = "{ACCESS_KEY}"; // AccessKey obtained from Picovoice Console (https://console.picovoice.ai/)
void createPicovoiceManager() {
_picovoiceManager = PicovoiceManager.create(
accessKey,
"/path/to/keyword/file.ppn",
_wakeWordCallback,
"/path/to/context/file.rhn",
_inferenceCallback);
}The wakeWordCallback and inferenceCallback parameters are functions that you want to execute when a wake word is detected and when an inference is made.
The inferenceCallback callback function takes a parameter of RhinoInference instance with the following variables:
- isUnderstood - true if Rhino understood what it heard based on the context or false if Rhino did not understand context
- intent - null if
isUnderstoodis not true, otherwise name of intent that were inferred - slots - null if
isUnderstoodis not true, otherwise the dictionary of slot keys and values that were inferred
Once you have instantiated a PicovoiceManager, you can start/stop audio capture and processing by calling:
await _picovoiceManager.start();
// .. use for detecting wake words and commands
await _picovoiceManager.stop();Our flutter_voice_processor Flutter plugin handles audio capture and passes frames to Picovoice for you.
Picovoice provides low-level access to the Picovoice platform for those who want to incorporate it into an already existing audio processing pipeline.
Picovoice is created by passing a Porcupine keyword file and Rhino context file to the create static constructor. Sensitivity, model files and requireEndpoint are optional.
import 'package:picovoice/picovoice_manager.dart';
import 'package:picovoice/picovoice_error.dart';
final String accessKey = "{ACCESS_KEY}"; // AccessKey obtained from Picovoice Console (https://console.picovoice.ai/)
void createPicovoice() async {
double porcupineSensitivity = 0.7;
double rhinoSensitivity = 0.6;
try {
_picovoice = await Picovoice.create(
accessKey,
"/path/to/keyword/file.ppn",
wakeWordCallback,
"/path/to/context/file.rhn",
inferenceCallback,
porcupineSensitivity,
rhinoSensitivity,
"/path/to/porcupine/model.pv",
"/path/to/rhino/model.pv",
requireEndpoint);
} on PicovoiceException catch (err) {
// handle picovoice init error
}
}To use Picovoice, just pass frames of audio to the process function. The callbacks will automatically trigger when the wake word is detected and then when the follow-on command is detected.
List<int> buffer = getAudioFrame();
try {
_picovoice.process(buffer);
} on PicovoiceException catch (error) {
// handle error
}
// once you are done using Picovoice
_picovoice.delete();First add our React Native modules to your project via yarn or npm:
yarn add @picovoice/react-native-voice-processor
yarn add @picovoice/porcupine-react-native
yarn add @picovoice/rhino-react-native
yarn add @picovoice/picovoice-react-nativeThe @picovoice/picovoice-react-native package exposes a high-level and a low-level API for integrating Picovoice into your application.
PicovoiceManager provides a high-level API that takes care of audio recording. This class is the quickest way to get started.
The static constructor PicovoiceManager.create will create an instance of a PicovoiceManager using a Porcupine keyword file and Rhino context file that you pass to it.
const accessKey = "${ACCESS_KEY}"; // obtained from Picovoice Console (https://console.picovoice.ai/)
this._picovoiceManager = PicovoiceManager.create(
accessKey,
'/path/to/keyword/file.ppn',
wakeWordCallback,
'/path/to/context/file.rhn',
inferenceCallback);The wakeWordCallback and inferenceCallback parameters are functions that you want to execute when a wake word is detected and when an inference is made.
Once you have instantiated a PicovoiceManager, you can start/stop audio capture and processing by calling:
try {
let didStart = await this._picovoiceManager.start();
} catch(err) { }
// .. use for detecting wake words and commands
let didStop = await this._picovoiceManager.stop();@picovoice/react-native-voice-processor module handles audio capture and passes frames to Picovoice for you.
Picovoice provides low-level access to the Picovoice platform for those who want to incorporate it into an already existing audio processing pipeline.
Picovoice is created by passing a Porcupine keyword file and Rhino context file to the create static constructor. Sensitivity and model files are optional.
const accessKey = "${ACCESS_KEY}"; // obtained from Picovoice Console (https://console.picovoice.ai/)
async createPicovoice() {
let porcupineSensitivity = 0.7;
let rhinoSensitivity = 0.6;
let requireEndpoint = false;
try {
this._picovoice = await Picovoice.create(
accessKey,
'/path/to/keyword/file.ppn',
wakeWordCallback,
'/path/to/context/file.rhn',
inferenceCallback,
processErrorCallback,
porcupineSensitivity,
rhinoSensitivity,
"/path/to/porcupine/model.pv",
"/path/to/rhino/model.pv",
requireEndpoint);
} catch (err) {
// handle error
}
}To use Picovoice, just pass frames of audio to the process function. The callbacks will automatically trigger when the wake word is detected and then when the follow-on command is detected.
let buffer = getAudioFrame();
try {
await this._picovoice.process(buffer);
} catch (e) {
// handle error
}
// once you are done
this._picovoice.delete();Porcupine can be found on Maven Central. To include the package in your Android project, ensure you have included mavenCentral() in your top-level build.gradle file and then add the following to your app's build.gradle:
dependencies {
// ...
implementation 'ai.picovoice:picovoice-android:${LATEST_VERSION}'
}There are two possibilities for integrating Picovoice into an Android application.
PicovoiceManager provides a high-level API for integrating Picovoice into Android applications. It manages all activities related to creating an input audio stream, feeding it into Picovoice engine, and invoking user-defined callbacks upon wake word detection and inference completion.
final String accessKey = "${ACCESS_KEY}"; // AccessKey obtained from Picovoice Console (https://console.picovoice.ai/)
final String keywordPath = "/path/to/keyword.ppn"; // path relative to 'assets' folder
final String contextPath = "/path/to/context.rhn"; // path relative to 'assets' folder
PicovoiceManager manager = new PicovoiceManager.Builder()
.setAccessKey(accessKey)
.setKeywordPath(keywordPath)
.setWakeWordCallback(new PicovoiceWakeWordCallback() {
@Override
public void invoke() {
// logic to execute upon detection of wake word
}
})
.setContextPath(contextPath)
.setInferenceCallback(new PicovoiceInferenceCallback() {
@Override
public void invoke(final RhinoInference inference) {
// logic to execute upon completion of intent inference
}
})
.build(appContext);
);Keyword (.ppn) and context (.rhn) files should be placed under the Android project assets folder (src/main/assets/).
The appContext parameter is the Android application context - this is used to extract Picovoice resources from the APK.
When initialized, input audio can be processed using:
manager.start();Stop the manager with:
manager.stop();Picovoice.java provides a low-level binding for Android. It can be initialized as follows:
import ai.picovoice.picovoice.*;
try {
Picovoice picovoice = new Picovoice.Builder()
.setPorcupineModelPath("/path/to/porcupine/model.pv")
.setKeywordPath("/path/to/keyword.ppn")
.setPorcupineSensitivity(0.7f)
.setWakeWordCallback(new PicovoiceWakeWordCallback() {
@Override
public void invoke() {
// logic to execute upon detection of wake word
}
})
.setRhinoModelPath("/path/to/rhino/model.pv")
.setContextPath("/path/to/context.rhn")
.setRhinoSensitivity(0.55f)
.setInferenceCallback(new PicovoiceInferenceCallback() {
@Override
public void invoke(final RhinoInference inference) {
// logic to execute upon completion of intent inference
}
})
.build(appContext);
} catch(PicovoiceException ex) { }Keyword (.ppn), context (.rhn) and model (.pv) files should be placed under the Android project assets folder (src/main/assets/).
Once initialized, picovoice can be used to process incoming audio.
private short[] getNextAudioFrame();
while (true) {
try {
picovoice.process(getNextAudioFrame());
} catch (PicovoiceException e) {
// error handling logic
}
}Finally, be sure to explicitly release resources acquired as the binding class does not rely on the garbage collector for releasing native resources:
picovoice.delete();The Picovoice iOS SDK is available via Cocoapods. To import it into your iOS project install Cocoapods and add the following line to your Podfile:
pod 'Picovoice-iOS'There are two possibilities for integrating Picovoice into an iOS application.
PicovoiceManager class manages all activities related to creating an audio input stream, feeding it into Picovoice engine, and invoking user-defined callbacks upon wake word detection and completion of intent inference. The class can be initialized as below:
import Picovoice
let accessKey = "${ACCESS_KEY}" // obtained from Picovoice Console (https://console.picovoice.ai/)
let manager = PicovoiceManager(
accessKey: accessKey,
keywordPath: "/path/to/keyword.ppn",
onWakeWordDetection: {
// logic to execute upon detection of wake word
},
contextPath: "/path/to/context.rhn",
onInference: { inference in
// logic to execute upon completion of intent inference
})when initialized input audio can be processed using manager.start(). The processing can be interrupted using
manager.stop().
Picovoice.swift provides an API for passing audio from your own audio pipeline into the Picovoice Platform for wake word detection and intent inference.
o construct an instance, you'll need to provide a Porcupine keyword file (.ppn), a Rhino context file (.rhn) and callbacks for when the wake word is detected and an inference is made. Sensitivity and model parameters are optional
import Picovoice
let accessKey = "${ACCESS_KEY}" // obtained from Picovoice Console (https://console.picovoice.ai/)
do {
let picovoice = try Picovoice(
accessKey: accessKey,
keywordPath: "/path/to/keyword.ppn",
porcupineSensitivity: 0.4,
porcupineModelPath: "/path/to/porcupine/model.pv"
onWakeWordDetection: {
// logic to execute upon detection of wake word
},
contextPath: "/path/to/context.rhn",
rhinoSensitivity: 0.7,
rhinoModelPath: "/path/to/rhino/model.pv"
onInference: { inference in
// logic to execute upon completion of intent inference
})
} catch { }Once initialized, picovoice can be used to process incoming audio. The underlying logic of the class will handle switching between wake word detection and intent inference, as well as invoking the associated events.
func getNextAudioFrame() -> [Int16] {
// .. get audioFrame
return audioFrame;
}
while (true) {
do {
try picovoice.process(getNextAudioFrame());
} catch { }
}Once you're done with an instance of Picovoice you can force it to release its native resources rather than waiting for the garbage collector:
picovoice.delete();Install the Web SDK using yarn:
yarn add @picovoice/picovoice-webor using npm:
npm install --save @picovoice/picovoice-webCreate an instance of the engine using PicovoiceWorker and run on an audio input stream:
import { PicovoiceWorker } from "@picovoice/picovoice-web";
function wakeWordCallback(detection: PorcupineDetection) {
console.log(`Porcupine detected keyword: ${detection.label}`);
}
function inferenceCallback(inference: RhinoInference) {
if (inference.isFinalized) {
if (inference.isUnderstood) {
console.log(inference.intent)
console.log(inference.slots)
}
}
}
function getAudioData(): Int16Array {
... // function to get audio data
return new Int16Array();
}
const picovoice = await PicovoiceWorker.create(
"${ACCESS_KEY}",
keyword,
wakeWordCallback,
porcupineModel,
context,
inferenceCallback,
rhinoModel
);
for (; ;) {
picovoice.process(getAudioData());
// break on some condition
}Replace ${ACCESS_KEY} with yours obtained from Picovoice Console.
When done, release the resources allocated to Picovoice using picovoice.release().
yarn add @picovoice/picovoice-angular @picovoice/web-voice-processor(or)
npm install @picovoice/picovoice-angular @picovoice/web-voice-processorimport { Subscription } from "rxjs"
import { PicovoiceService } from "@picovoice/picovoice-angular"
...
constructor(private picovoiceService: PicovoiceService) {
this.wakeWordDetectionSubscription = picovoiceService.wakeWordDetection$.subscribe(
(wakeWordDetection: PorcupineDetection) => {
this.inference = null;
this.wakeWordDetection = wakeWordDetection;
}
);
this.inferenceSubscription = picovoiceService.inference$.subscribe(
(inference: RhinoInference) => {
this.wakeWordDetection = null;
this.inference = inference;
}
);
this.contextInfoSubscription = picovoiceService.contextInfo$.subscribe(
(contextInfo: string | null) => {
this.contextInfo = contextInfo;
}
);
this.isLoadedSubscription = picovoiceService.isLoaded$.subscribe(
(isLoaded: boolean) => {
this.isLoaded = isLoaded;
}
);
this.isListeningSubscription = picovoiceService.isListening$.subscribe(
(isListening: boolean) => {
this.isListening = isListening;
}
);
this.errorSubscription = picovoiceService.error$.subscribe(
(error: string | null) => {
this.error = error;
}
);
}
async ngOnInit() {
try {
await this.picovoiceService.init(
accessKey,
porcupineKeyword,
porcupineModel,
rhinoContext,
rhinoModel
);
}
catch (error) {
console.error(error)
}
}
ngOnDestroy() {
this.wakeWordDetectionSubscription.unsubscribe();
this.inferenceSubscription.unsubscribe();
this.contextInfoSubscription.unsubscribe();
this.isLoadedSubscription.unsubscribe();
this.isListeningSubscription.unsubscribe();
this.errorSubscription.unsubscribe();
this.picovoiceService.release();
}yarn add @picovoice/picovoice-react @picovoice/web-voice-processor(or)
npm install @picovoice/picovoice-react @picovoice/web-voice-processorimport { usePicovoice } from '@picovoice/picovoice-react';
function App(props) {
const {
wakeWordDetection,
inference,
contextInfo,
isLoaded,
isListening,
error,
init,
start,
stop,
release,
} = usePicovoice();
const initEngine = async () => {
await init(
${ACCESS_KEY},
porcupineKeyword,
porcupineModel,
rhinoContext,
rhinoModel
);
await start();
}
useEffect(() => {
if (wakeWordDetection !== null) {
console.log(`Picovoice detected keyword: ${wakeWordDetection.label}`);
}
}, [wakeWordDetection])
useEffect(() => {
if (inference !== null) {
if (inference.isUnderstood) {
console.log(inference.intent)
console.log(inference.slots)
}
}
}, [inference])
}yarn add @picovoice/picovoice-vue @picovoice/web-voice-processor(or)
npm install @picovoice/picovoice-vue @picovoice/web-voice-processor<script lang='ts'>
import { usePicovoice } from '@picovoice/picovoice-vue';
export default {
data() {
const {
state,
init,
start,
stop,
release
} = usePicovoice();
init(
${ACCESS_KEY},
{
label: "Picovoice",
publicPath: "picovoice_wasm.ppn",
},
{ publicPath: "porcupine_params.pv" },
{ publicPath: "clock_wasm.rhn" },
{ publicPath: "rhino_params.pv" },
);
return {
state,
start,
stop,
release
}
},
watch: {
"state.wakeWordDetection": function(wakeWord) {
if (wakeWord !== null) {
console.log(wakeWord)
}
},
"state.inference": function(inference) {
if (inference !== null) {
console.log(inference)
}
},
"state.contextInfo": function(contextInfo) {
if (contextInfo !== null) {
console.log(contextInfo)
}
},
"state.isLoaded": function(isLoaded) {
console.log(isLoaded)
},
"state.isListening": function(isListening) {
console.log(isListening)
},
"state.error": function(error) {
console.error(error)
},
},
onBeforeDestroy() {
this.release();
},
};
</script>To add the picovoice library into your app, add picovoice to your app's Cargo.toml manifest:
[dependencies]
picovoice = "*"To create an instance of the engine with default parameters, use the PicovoiceBuilder function.
You must provide a Porcupine keyword file, a wake word detection callback function, a Rhino context file and an inference callback function.
You must then make a call to init():
use picovoice::{rhino::RhinoInference, PicovoiceBuilder};
let wake_word_callback = || {
// let user know wake word detected
};
let inference_callback = |inference: RhinoInference| {
if inference.is_understood {
let intent = inference.intent.unwrap();
let slots = inference.slots;
// add code to take action based on inferred intent and slot values
} else {
// add code to handle unsupported commands
}
};
let mut picovoice = PicovoiceBuilder::new(
keyword_path,
wake_word_callback,
context_path,
inference_callback,
).init().expect("Failed to create picovoice");Upon detection of wake word defined by keyword_path it starts inferring user's intent
from the follow-on voice command within the context defined by the file located at context_path.
keyword_path is the absolute path to Porcupine wake word engine keyword file (with .ppn suffix).
context_path is the absolute path to Rhino Speech-to-Intent engine context file (with .rhn suffix).
wake_word_callback is invoked upon the detection of wake phrase and
inference_callback is invoked upon completion of follow-on voice command inference.
When instantiated, valid sample rate can be obtained via sample_rate().
Expected number of audio samples per frame is frame_length().
The engine accepts 16-bit linearly-encoded PCM and operates on single-channel audio:
fn next_audio_frame() -> Vec<i16> {
// get audio frame
}
loop {
picovoice.process(&next_audio_frame()).expect("Picovoice failed to process audio");
}Picovoice is implemented in ANSI C and therefore can be directly linked to C applications. Its public header file (sdk/c/include/pv_picovoice.h) contains relevant information. An instance of the Picovoice object can be constructed as follows.
const char* ACCESS_KEY = "${ACCESS_KEY}"; // AccessKey string obtained from [Picovoice Console](https://console.picovoice.ai/)
const char *porcupine_model_path = ... // Available at resources/porcupine/lib/common/porcupine_params.pv
const char *keyword_path = ...
const float porcupine_sensitivity = 0.5f;
const char *rhino_model_path = ... // Available at resources/rhino/lib/common/rhino_params.pv
const char *context_path = ...
const float rhino_sensitivity = 0.5f;
const bool require_endpoint = true;
static void wake_word_callback(void) {
// take action upon detection of wake word
}
static void inference_callback(pv_inference_t *inference) {
// `inference` exposes three immutable properties:
// (1) `IsUnderstood`
// (2) `Intent`
// (3) `Slots`
// take action based on inferred intent
pv_inference_delete(inference);
}
pv_picovoice_t *handle = NULL;
pv_status_t status = pv_picovoice_init(
access_key,
porcupine_model_path,
keyword_path,
porcupine_sensitivity,
wake_word_callback,
rhino_model_path,
context_path,
rhino_sensitivity,
require_endpoint,
inference_callback,
&handle);
if (status != PV_STATUS_SUCCESS) {
// error handling logic
}Sensitivity is the parameter that enables developers to trade miss rate for false alarm. It is a floating-point number within [0, 1]. A higher sensitivity reduces miss rate (false reject rate) at cost of increased false alarm rate.
handle is an instance of Picovoice runtime engine that detects utterances of the wake phrase provided by keyword_path. Upon detection of wake word it starts inferring user's intent from the follow-on voice command within the context defined in context_path. wake_word_callback is invoked upon the detection of wake phrase and inference_callback is invoked upon completion of follow-on voice command inference.
Picovoice accepts single channel, 16-bit PCM audio. The sample rate can be retrieved using pv_sample_rate(). Finally, Picovoice accepts input audio in consecutive chunks
(aka frames) the length of each frame can be retrieved using pv_porcupine_frame_length().
extern const int16_t *get_next_audio_frame(void);
while (true) {
const int16_t *pcm = get_next_audio_frame();
const pv_status_t status = pv_picovoice_process(handle, pcm);
if (status != PV_STATUS_SUCCESS) {
// error handling logic
}
}Finally, when done be sure to release the acquired resources.
pv_picovoice_delete(handle);Picovoice is implemented in ANSI C and therefore can be directly linked to embedded C projects. Its public header file contains relevant information. An instance of the Picovoice object can be constructed as follows:
#define MEMORY_BUFFER_SIZE ...
static uint8_t memory_buffer[MEMORY_BUFFER_SIZE] __attribute__((aligned(16)));
static const uint8_t *keyword_array = ...
const float porcupine_sensitivity = 0.5f
static void wake_word_callback(void) {
// logic to execute upon detection of wake word
}
static const uint8_t *context_array = ...
const float rhino_sensitivity = 0.75f
static void inference_callback(pv_inference_t *inference) {
// `inference` exposes three immutable properties:
// (1) `IsUnderstood`
// (2) `Intent`
// (3) `Slots`
// ..
pv_inference_delete(inference);
}
pv_picovoice_t *handle = NULL;
const pv_status_t status = pv_picovoice_init(
MEMORY_BUFFER_SIZE,
memory_buffer,
sizeof(keyword_array),
keyword_array,
porcupine_sensitivity,
wake_word_callback,
sizeof(context_array),
context_array,
rhino_sensitivity,
inference_callback,
&handle);
if (status != PV_STATUS_SUCCESS) {
// error handling logic
}Sensitivity is the parameter that enables developers to trade miss rate for false alarm. It is a floating-point number within [0, 1]. A higher sensitivity reduces miss rate (false reject rate) at cost of increased false alarm rate.
handle is an instance of Picovoice runtime engine that detects utterances of wake phrase defined in keyword_array. Upon detection of wake word it starts inferring user's intent from the follow-on voice command within the context defined in context_array. wake_word_callback is invoked upon the detection of wake phrase and inference_callback is invoked upon completion of follow-on voice command inference.
Picovoice accepts single channel, 16-bit PCM audio. The sample rate can be retrieved using pv_sample_rate(). Finally, Picovoice accepts input audio in consecutive chunks
(aka frames) the length of each frame can be retrieved using pv_porcupine_frame_length().
extern const int16_t *get_next_audio_frame(void);
while (true) {
const int16_t *pcm = get_next_audio_frame();
const pv_status_t status = pv_picovoice_process(handle, pcm);
if (status != PV_STATUS_SUCCESS) {
// error handling logic
}
}Finally, when done be sure to release the acquired resources.
pv_picovoice_delete(handle);- Improvements to error reporting
- Upgrades to authorization and authentication system
- Added
reset()function to API PicovoiceManagerclasses can now access context information without a call tostart()- Added Farsi support for microcontrollers
- Various bug fixes and improvements
- Node min support bumped to 16
- Unity editor min support bumped to 2021
- Patches to .NET support
- Added language support for Arabic, Dutch, Hindi, Mandarin, Polish, Russian, Swedish and Vietnamese
- Added support for .NET 7.0 and fixed support for .NET Standard 2.0
- iOS minimum support moved to 11.0
- Improved stability and performance
- macOS arm64 (Apple Silicon) support added for Java and Unity SDKs
- Various bug fixes and improvements
- Improved accuracy
- Added Rust SDK
- macOS arm64 support
- Added NodeJS support for Windows, NVIDIA Jetson Nano, and BeagleBone
- Added .NET support for NVIDIA Jetson Nano and BeagleBone
- Runtime optimization
- Improved accuracy
- Runtime optimizations
- .NET SDK
- Java SDK
- React Native SDK
- C SDK
- Initial release
You can find the FAQ here.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent