I’ve been made aware that the code I’ve written to access text-to-speech from ElevenLabs API is no longer working.
I’ve tested it and it seems that the CORS-Proxy that is being used in ai-character-chat currently doens’t allow POST methods (which is being used to ‘post’ the text to be ‘spoken’ in ElevenLabs).
Not a major/priority issue but might be nice to be fixed. I also wonder how many are using text to speech (even just using the Speech Synthesis code) in the ai-character-chat…
Hmm, I wasn’t able to replicate this problem. I added this as character’s custom code, and it does log the response in the console:
oc.thread.on("MessageAdded", async function() { let result = await fetch("https://httpbin.org/post", { method: "POST", headers: { "Content-Type":"application/json" }, body: JSON.stringify({foo:3}) }).then(r => r.json()); console.log(result); });Is it perhaps header values you’re missing, or something? Certainly possible that there is a big though and I’m just not hitting it with the above example for whatever reason.
Either way this motivated me to finally get around to creating a CORs-bypassing plugin: https://perchance.org/fetch-plugin That way I can ensure strong backwards-compatibility and performance instead of just relying on a little glitch.com server, which won’t scale, and doesn’t have good perf/uptime guarantees. I’ll wait to hear back from you before integrating it into
ai-character-chatjust so we can don’t end up making it harder for you to reproduce the bug you were up against here.bottom of page says “Check out more plugins at perchance.org/plugins” twice
edit: and now it doesn’t. must be magic
@Alllo@lemmy.world @VioneT@lemmy.world Sorry just realized the plugin is not quite ready for prime time! Need to make some breaking changes so I’ve commented out the code for now. The moment I started integrating it into ai-character-chat I realised it’s a bad idea to overwrite the existing fetch - should instead just be a separate “superFetch” or whatever because otherwise if you need to e.g. download a big file that you know doesn’t have any CORs problems, you’re forced to go through the proxy, which will be slower. Will update soon hopefully, if not tomorrow. Sorry for trouble if you’d started playing with it!
@Alllo@lemmy.world @VioneT@lemmy.world Okay,
superFetchit is: https://perchance.org/super-fetch-plugin … phew - happy I managed to pull the plug on that previous approach quickly, but sorry again for the breaking change! I’d only ever do when a plugin is extremely new - i.e. a few hours old, as in this case. I take breaking changes with the official plugins really seriously, so it was still somewhat painful to do.
Previously it worked fine, but now it doesn’t. Here’s the code for the ElevenLabs API that I wrote. Here is a HAR file of the requests.
Okay, thanks for the example, I think it’s all fixed now. Hopefully I didn’t break anything. Been up for two days straight tho so I wouldn’t bet on it, but I do some basic tests and it seems good. Will check lemmy messages first thing tomorrow 🫡
@perchance - pinging dev
@perchance@lemmy.world - There’s seems to be a fetch
POSTproblem again as of now.Sorry about this! I really want to create a stable platform that people can build upon without having annoying problems, so it’s top priority for me to solve stuff like this. It’s hard enough to debug custom code without having to deal with stuff like this 😓
That said, would you be able to share a character URL? I tried this code and it worked correctly:
oc.thread.on("MessageAdded", async function() { let result = await fetch("https://httpbin.org/post", { method: "POST", headers: { "Content-Type":"application/json" }, body: JSON.stringify({foo:3}) }).then(r => r.json()); console.log("POST response:", result); });If it works for you now, then maybe it was a temporary problem. If that’s the case, I’ll set up a monitor to do this once per minute, and see if I can catch any problems and correlate them with server logs/errors.
Here’s the character link: https://perchance.org/ai-character-chat?data=Chloe~0bbbcdc9119e3a37bf986ac033c43548.gz
Hmm, for whatever reason, that works fine for me. That said, with a VPN enabled, the response is has the 401 Unauthorized status with the following JSON instead of the audio:
{ "detail": { "status": "detected_unusual_activity", "message": "Unusual activity detected. Free Tier usage disabled..." } }What do you see in the network panel in devtools when it doesn’t work?
Something like that too. Though, I don’t have any VPN enabled (on Microsoft Edge, Windows 10), I guess they are quite limiting the free tier API now i.e. there is a limit to consecutive requests.
