Skip to main content

How to play audio from decoded base64 string with ElevenLabs Streaming Websocket Typescript

I am attempting to use the ElevenLabs API and Websockets to stream audio to the browser. response.audio does return a generated partial MP3 audio chunk encoded as a base64 string, but I am stuck on trying to properly decode and play it. This is my current attempt:

Main notes:

  • The API does return a response of base64 string successfully
  • I keep receiving the error on Chrome: Uncaught (in promise) DOMException: Failed to load because no supported source was found.
  • My blob url returns a 404 error

Here is my code:

"use client";


import React, { useRef, useState } from 'react';

const StreamingAudioTest: React.FC = () => {

  const [isPlaying, setIsPlaying] = useState(false);
  const audioRef = useRef<HTMLAudioElement | null>(null);

  const handlePlayButtonClick = () => {

    const voiceId = "<voice-id>";
    const model = 'eleven_monolingual_v1';
    const wsUrl = `wss://api.elevenlabs.io/v1/text-to-speech/${voiceId}/stream-input?model_id=${model}`;
    const socket = new WebSocket(wsUrl);

    socket.onopen = function (event) {
      const bosMessage = {
        "text": " ",
        "voice_settings": {
          "stability": 0.5,
          "similarity_boost": true
        },
        "xi_api_key": "<api-key>", // replace with your API key
      };

      socket.send(JSON.stringify(bosMessage));

      const textMessage = {
        "text": "Hello ",
        "try_trigger_generation": true,
      };

      socket.send(JSON.stringify(textMessage));

      const eosMessage = {
        "text": ""
      };

      socket.send(JSON.stringify(eosMessage));
    };

    socket.onmessage = async function (event) {
      const response = await JSON.parse(event.data);

   
      if (response.audio) {
        
        const audioChunk = atob(response.audio); // decode base64

  
      
        console.log("Recieved audio chunk")

        if (audioRef.current) {
            const blob = new Blob([audioChunk], { type: 'audio/mp3' }); 
            audioRef.current.src = URL.createObjectURL(blob);
            audioRef.current.play();
          }
        
      }

      if (response.isFinal) {
        // Handle generation completion
      }

      if (response.normalizedAlignment) {
        // Handle alignment info if needed
      }
    };

    socket.onerror = function (error) {
      console.error(`WebSocket Error: ${error}`);
    };

    socket.onclose = function (event) {
      if (event.wasClean) {
        console.info(`Connection closed cleanly, code=${event.code}, reason=${event.reason}`);
      } else {
        console.warn('Connection died');
      }
    };

    // Cleanup the WebSocket when the component unmounts
    return () => {
      socket.close();
    };
  };


  return (
    <div className='text-red-500'>
      <h1>Text-to-Speech Audio Player</h1>
      <button onClick={handlePlayButtonClick} disabled={isPlaying}>
        {isPlaying ? 'Playing...' : 'Play Audio'}
      </button>
      {/* <audio ref={audioRef} controls /> */}

      <audio ref={audioRef} autoPlay controls />
    </div>
  );
};




export default StreamingAudioTest;

Via Active questions tagged javascript - Stack Overflow https://ift.tt/t9AZyWC

Comments

Popular posts from this blog

Confusion between commands.Bot and discord.Client | Which one should I use?

Whenever you look at YouTube tutorials or code from this website there is a real variation. Some developers use client = discord.Client(intents=intents) while the others use bot = commands.Bot(command_prefix="something", intents=intents) . Now I know slightly about the difference but I get errors from different places from my code when I use either of them and its confusing. Especially since there has a few changes over the years in discord.py it is hard to find the real difference. I tried sticking to discord.Client then I found that there are more features in commands.Bot . Then I found errors when using commands.Bot . An example of this is: When I try to use commands.Bot client = commands.Bot(command_prefix=">",intents=intents) async def load(): for filename in os.listdir("./Cogs"): if filename.endswith(".py"): client.load_extension(f"Cogs.{filename[:-3]}") The above doesnt giveany response from my Cogs ...

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console...

Where and how is this Laravel kernel constructor called? [closed]

Where and how is this Laravel kernel constructor called? public fucntion __construct(Application $app, $Router $roouter) { } I have read the documentation and some online tutorial but I can find any clear explanation. I am learning Laravel and I am wondering where does this kernel constructor receives its arguments from. "POSTMOTERM" CLARIFICATION: Here is more clarity.I have checked the boostrap/app.php and it is only used for boostrapping the interfaces into the container class. What is not clear to me is where and how the Kernel class is instatiated and the arguments passed to the object calling the constructor.Something similar to; obj = new kernel(arg1,arg2) or, is the framework using some magic functions somewhere? Special gratitude to those who burn their eyeballs and brain cells on this trivia before it goes into a full blown menopause alias "MARKED AS DUPLICATE". To some of the itchy-finger keyboard warriors, a.k.a The mods,because I believe in th...