csharpRhino — .NET Quick Start

  • Speech-to-Intent Engine
  • Domain Specific NLU
  • Offline NLU
  • Local Voice Recognition
  • Linux
  • macOS
  • Windows
  • .NET
  • C#


  • .NET Core 3.1
  • OpenAL


  • Linux (x86_64)
  • macOS (x86_64)
  • Windows (x86_64)
  • Raspberry Pi

Cloning the Repository

If using SSH, clone the repository with:

git clone [email protected]:Picovoice/rhino.git

If using HTTPS, then type:

git clone https://github.com/Picovoice/rhino.git


Both demos use Microsoft's .NET Core framework.

MicDemo uses OpenAL. On Windows, install using the OpenAL Windows Installer.

On Linux use apt-get

sudo apt-get install libopenal-dev

On macOS use Brew

brew install openal-soft

Once .NET Core and OpenAL have been installed, you can build with the dotnet CLI

dotnet build -c MicDemo.Release
dotnet build -c FileDemo.Release


NOTE: the working directory for all dotnet commands is:


File Demo

The file demo uses Rhino to get an inference result from an audio file. This demo is mainly useful for quantitative performance benchmarking against a corpus of audio data. Note that only the relevant spoken command should be present in the file and no other speech. There also needs to be at least one second of silence at the end of the file.

dotnet run -c FileDemo.Release -- --input_audio_path ${AUDIO_PATH} --context_path ${CONTEXT_PATH}

Microphone Demo

The microphone demo opens an audio stream from a microphone and performs inference on spoken commands:

dotnet run -c MicDemo.Release -- --context_path ${CONTEXT_PATH}

It is possible that the default audio input device is not the one you wish to use. There are a couple of debugging facilities baked into the demo application to solve this. First, type the following into the console:

dotnet run -c MicDemo.Release -- --show_audio_devices

It provides information about various audio input devices on the box. On a Windows PC, this is the output:

Available input devices:
Device 0: Microphone Array (Realtek(R) Au
Device 1: Microphone Headset USB

You can use the device index to specify which microphone to use for the demo. For instance, if you want to use the Headset microphone in the above example, you can invoke the demo application as below:

dotnet run -c MicDemo.Release -- --context_path ${CONTEXT_PATH} --audio_device_index 1

If the problem persists we suggest storing the recorded audio into a file for inspection. This can be achieved with:

dotnet run -c MicDemo.Release -- --context_path ${CONTEXT_PATH} --audio_device_index 1 --output_path ./test.wav

If after listening to stored file there is no apparent problem detected please open an issue.

Custom Context

You can create custom Rhino context models using Picovoice Console.

Issue with this doc? Please let us know.