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
    1
    ·
    6 months ago

    I wasn’t able to reproduce this when trying it with this code:

    oc.thread.on("StreamingMessage", async function (data) {
      let lastChunkI = -1;
      let chunksText = "";
      let chunks = [];
      for await (let chunk of data.chunks) {
        chunks.push(chunk);
        chunksText += chunk.text;
        if(chunk.index !== lastChunkI+1) console.warn("OUT OF ORDER CHUNKS!", chunks);
        lastChunkI++;
      }
      console.log("chunks:", chunks);
      console.log("chunksText:", chunksText);
    });
    

    Or have I misunderstood the problem?

    • VioneT@lemmy.worldOPM
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      6 months ago

      You have. On trying your code. it gave me the OUT OF ORDER CHUNKS!:



      Here’s the character I used with the custom code to check the out of order chunks.: Link to Character

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

        Ahh, thank you! Was very confused at first because I iteratively made your character closer to the default Assistant to work out why it was happening in yours but not the assistant, and found that the profile pic was the cause lmao, but eventually realised that it was because data url vs normal URL, and the data url (being larger) was making an async IndexedDB request take a few milliseconds longer, which caused the out-of-order-ness. But I shouldn’t have even been doing those db requests in the first place, so I’ve removed them, and this race condition type bug shouldn’t be possible at all now. Thanks again!!