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

  • perchance@lemmy.worldM
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    5 months ago

    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-chat just so we can don’t end up making it harder for you to reproduce the bug you were up against here.

      • perchance@lemmy.worldM
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        5 months ago

        @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!

      • perchance@lemmy.worldM
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        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 🫡