![streamelements tts voices streamelements tts voices](https://4.bp.blogspot.com/-2SdClYoVG-Y/XLKUCw1lpdI/AAAAAAAAAww/m84PU3ZZ0DEcLv5fbvvZ6rtgzhN0sBISACLcBGAs/s1600/Untitled.png)
The website still calls 1 API, but the API then calls one of the proxy servers (and kept track of which one was rate-limited and which wasn't), and the proxy server in turn calls the Streamlabs API to convert the message. I've then decided this had to be fixed and created a proxy server system in order to prevent rate-limiting to occur. That wouldn't work since the website on it's peak had 35-40 TTS submits a minute and would cause an inconsistent user experience. Meaning you could only do 20 calls before you'd have to wait to do more calls. Atleast I thought it was.Īpparently the Streamlabs API had a rate limit. So I had to host a simple webserver/API that the website could call and everything was fine. For the developers around: they protected the API with CORS. It does basically the same, but it couldn't be called directly from a website, there had to be a server inbetween. I've tinkered around with this for a few days until I stumbled upon the Streamlabs API. I've thought of using a service that solves captchas (paid), but decided it was too expensive. They added a captcha to their API, so it was impossible for the website to convert the TTS messages. Apparently the website caused so much traffic for StreamElements that they decided to implement security measures. After that I saw that the amount of visitors was climbing rapidly and with that, the site ranked higher and higher in Google.įast-forward to July 17th, 2021. I think it was on r/LiveStreamFails or r/xqcow, but I'm not sure. I wanted to perfect the website, so I've strived to get a high as possible score in Google Lighthouse and made sure to get SEO right, so the website would show up in Google.Īfter few months of having around 10-15 users a day, the website was featured in a Reddit post. Back then it was just a static website built with GatsbyJS, so it didn't cost much for me to host it and it was worth it. I decided make it public and host it as a website, mainly because of the low costs. Keep this in mind, this is important for later. But instead of calling an external API, the application comes bundled with it's own API which in turn calls the Streamlabs API to convert the text-to-speech.įAQ Why did you make an application instead continuing to develop the website?Įlundus Core started out as a project for me to test out some donation messages for xQc, using the StreamElements API.
![streamelements tts voices streamelements tts voices](https://res.cloudinary.com/practicaldev/image/fetch/s--oZL4cWYi--/c_imagga_scale,f_auto,fl_progressive,h_420,q_auto,w_1000/https://thepracticaldev.s3.amazonaws.com/i/c9kqd5bx8l3ex60l62k6.png)
The frontend, apart from a few minor tweaks, is exactly the same as the website that I've made. Start Elundus Core using the shortcut created on your desktop or from the start menu.dmg by right-clicking on it and selecting open, or try any of the installation methods in this link. Windows: if you get a SmartScreen warning, select More info and click Run anyway.
Streamelements tts voices download#
Go to releases and download the setup from the latest release.Auto-updater, so you'll receive the latest features and fixes automatically.Text-to-speech conversion for Amazon Polly voices (same voices are used by StreamElements and StreamLabs).Wondering why I've made the step to change it to a desktop application? Check out the FAQ. It's a port of the website that I've initially created for the same purpose. Elundus Core is a desktop application you can use to simulate/preview text-to-speech (TTS) voice messages for Twitch.