Skip to content

Add Gnani (STT and TTS) community integrations#991

Open
Gnani-AI-Mintlify wants to merge 3 commits into
pipecat-ai:mainfrom
Gnani-AI-Mintlify:add-gnani-community-integration
Open

Add Gnani (STT and TTS) community integrations#991
Gnani-AI-Mintlify wants to merge 3 commits into
pipecat-ai:mainfrom
Gnani-AI-Mintlify:add-gnani-community-integration

Conversation

@Gnani-AI-Mintlify

Copy link
Copy Markdown

Gnani

Adds Gnani to the Community Integrations page under both Speech-to-Text and Text-to-Speech.

Gnani Vachana is a production speech AI platform for Indian languages, providing high-accuracy STT and low-latency TTS across REST, SSE, and WebSocket. The integration includes GnaniHttpSTTService, GnaniSTTService, GnaniHttpTTSService, GnaniSSETTSService, and GnaniTTSService. WebSocket STT supports 10+ Indian languages at 8/16/44.1/48 kHz, while TTS offers four voices (Pranav, Kaveri, Shubhra, and Deepak) with interruptible WebSocket streaming.

Tested with the latest Pipecat main branch (v1.5.0+).

Repository: https://github.com/Gnani-AI-Mintlify/pipecat-gnani
PyPI: https://pypi.org/project/pipecat-gnani/
Core SDK: https://pypi.org/project/gnani-vachana/
Demo Video: https://go.screenpal.com/watch/cOi2nynUax5
Maintainers: (Gnani.ai)


## Overview

`GnaniHttpSTTService` and `GnaniSTTService` transcribe speech using

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be simpler to just add support for the streaming services? Or, are there use cases where the HTTP API is better suited for voice agents?

Same question for the TTS services.

Comment thread docs.json
"source": "/server/services/stt/gladia",
"destination": "/api-reference/server/services/stt/gladia"
},
{

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need for a redirect since these were just added.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure , will remove those

Comment thread docs.json
"source": "/server/services/tts/fish",
"destination": "/api-reference/server/services/tts/fish"
},
{

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same here, remove.

@markbackman markbackman left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before moving forward, I think it's worth considering which APIs to expose to Pipecat. Do you want to maintain HTTP and Websocket endpoints? Pipecat is for realtime / voice use cases, so streaming services are almost always preferred.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants