We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when initializing cartesia synthesizer
GPT-4
Deepgram
None
real-time streaming with cartesia
conversation = StreamingConversation( output_device=speaker_output, transcriber=DeepgramTranscriber( DeepgramTranscriberConfig.from_input_device( microphone_input, endpointing_config=PunctuationEndpointingConfig(), api_key=settings.deepgram_api_key, ), ), agent=ChatGPTAgent( ChatGPTAgentConfig( openai_api_key=settings.openai_api_key, initial_message=BaseMessage(text="What up"), prompt_preamble="""The AI is having a pleasant conversation about life""", ) ), synthesizer=CartesiaSynthesizer( CartesiaSynthesizerConfig( api_key=settings.cartesia_api_key, voice_id=CARTESIA_VOICE_ID, sampling_rate=16000, audio_encoding="linear16", experimental_voice_controls={ "speed": "slow", "emotion": "positivity: high" } ).from_output_device(speaker_output), ), ) await conversation.start()
There should be no error at all
The text was updated successfully, but these errors were encountered:
The error might be caused by unpublished release (latest is June 17) when replacing cartesia.tts with cartesia (July 3)
cartesia.tts
cartesia
949711f
Sorry, something went wrong.
I'm having this issue as well and tried to go in and fix things in the Vocode files but wasn't able to figure it out as more and more errors came out.
No branches or pull requests
Brief Description
Error when initializing cartesia synthesizer
LLM
GPT-4
Transcription Services
Deepgram
Synthesis Services
None
Telephony Services
None
Conversation Type and Platform
real-time streaming with cartesia
Steps to Reproduce
Expected Behavior
There should be no error at all
Screenshots
The text was updated successfully, but these errors were encountered: