How to use Krisp on client side?

To use Krisp noise cancellation on the client side with LiveKit, you need to integrate the Krisp Noise Filter into your LiveKit Cloud project. This feature is available for LiveKit Cloud projects on Scale or Enterprise plans. The integration involves installing the Krisp Noise Filter package and enabling it in your client codebase. Here's a brief overview of the steps: 1. Installation: Install the Krisp Noise Filter package using npm:

npm install @livekit/krisp-noise-filter

2. Usage: Import and enable the Krisp Noise Filter in your client code. You should dynamically import the filter and enable it when a local audio track is published. This is typically done in response to the

RoomEvent.LocalTrackPublished

event. For more detailed instructions, refer to the LiveKit documentation on enhanced noise cancellation. Would you like more detailed guidance on implementing this in your code? Sources: - Enhanced noise cancellation with Krisp 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

Krisp is run only on client side? Why it needs cloud project?

Krisp noise cancellation is primarily run on the client side, but it requires a LiveKit Cloud project because the Krisp technology involves licensing and authentication that is managed through LiveKit's cloud infrastructure. According to LiveKit documentation, Krisp is available only for LiveKit Cloud projects on Scale or Enterprise plans. This is because LiveKit has partnered with Krisp to provide this feature, and it involves a licensing fee that is integrated into the cloud service offering. Would you like more details on how this integration works or alternatives for self-hosted deployments? Sources: - Enhanced noise cancellation with Krisp 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.