Discussions
session_timeout
I am config the session_timeout to 300, i am unable to make that config , after the session_timeout in body, i am unable to get reponse , i am putting my code down below :
const sessionResponse:any = await fetch(${DID_API.url}/talks/streams, {
method: 'POST',
headers: {'Authorization': Basic ${DID_API.key}, 'Content-Type': 'application/json' , ...reaminingHeaders},
body: JSON.stringify({
source_url: "https://clips-presenters.d-id.com/amy/FLZ1USJl7m/vzswgDCwKZ/image.png",
session_timeout : 299
}),
}).catch(async ()=>{
console.log("stream not startedddd")
});
driver was not found
When I try to use a driver from the presenter list, such as from this URL:
https://api.d-id.com/clips/presenters/v2_public_alex@qcvo4gupoy/drivers,
and then use the following in the body of the POST request to https://api.d-id.com/clips:
Start a Stream call is failing
My Request
Enterprise Meeting Akash
Greetings Akash,
Finnish language
Multilingual agent makes still a lot of speaking errors with Finnish language + only one multilingual voice is working. I've tried my own voices via Elevenlabs but they do not work. Do you have plans for supporting Finnish any time soon?
voci pro +
posso usare le voci pro +
Unsubscribe
try this one to see if it works because I don't remember what the email was: [email protected]
Chinese (Taiwan) Teacher Project Example: 我想要一杯热巧克力
Chinese teacher Example (45 second short):
Chatbot with Streaming Video AI
I'm using the API key from DiD to use my Chatbot. It works, but it has many pronunciation problems with the prompts. The audio responses in the Streaming Video with OpenAI version 4o vision and OpenAI version 3.5 Turbo are equally as bad. The Chatbot can't pronounce many quotations marks and other punctuation marks, and comes out with "br slash" and "Asterisk" instead. Is there a fix for this? I already tried Enable Chatbot HTML Responses, and Convert Markdown To HTML In AI Generated Post Content, which worked when I use the non-streaming video Chatbots. However, the pronunciation mistakes start again when using this version of the API. Any ideas how to stop this? I will launch soon, so I want this to be a great feature for new visitors. Thanks!
Creating a fluid chat stream
Hi there,