Recherche avancée

Sur d’autres sites (2026)

• How do I broadcast live audio in Node.js ?

  20 juin 2020, par Yousef Alaqra

  I'm trying stream live audio to a wide range of clients in a web browser.

  



  My current solution :

  



  Dotnet core 3.1 console application

  



  

  1. receive the audio data over UDP

  


  2. trimming the first 28 bytes of each received packet

  


  3. and send the processed packet over UDP.

  


  



  Node JS

  



  

  1. execute a Ffmepg as a child process to receive audio data packets
over UDP from the console app, and encode each packet to audio WAV
format

  


  2. Pipe out the result of the child process into a GET HTTP endpoint response

  


  



  Browser

  



  

  1. HTML audio element with source value equals to the node js GET
endpoint

  


  



  Problem :

  



  The solution is giving a good result, but only for one device(one to one), which is not what I want to achieve.

  



  I've tried many solutions to make it applicable to a wide range of devices, such as using working threads and forking a child process, but none of them changes the result.

  



  I believe that I've to make some changes to the node js implementation, so here I'll share it with you, hoping to get a clue to solve the problem.

  



  var express = require("express");
var app = express();
var children = require("child_process");

var port = 5001;
var host = "192.168.1.230";

app.listen(port, host, () => {
  console.log("Server running at http://" + host + ":" + port + "/");
});

app.get('/stream', (req, res) => {
  const ffmpegCommand = "ffmpeg";
  var ffmpegOptions =
    "-f s16le -ar 48000 -ac 2 -i udp://192.168.1.230:65535 -f wav -";

  var ffm = children.spawn(ffmpegCommand, ffmpegOptions.split(" "));

  res.writeHead(200, { "Content-Type": "audio/wav; codecs=PCM" });
  ffm.stdout.pipe(res);
});


  



  If someone interested to see the full implementation, please let me know.

  


• How to broadcast live audio in node js (1 to many)

  19 juin 2020, par Yousef Alaqra

  I'm trying stream live audio to a wide range of clients in a web browser.

  



  My current solution :

  



  Dotnet core 3.1 console application

  



  

  1. receive the audio data over UDP

  


  2. trimming the first 28 bytes of each received packet

  


  3. and send the processed packet over UDP.

  


  



  Node JS

  



  

  1. execute a Ffmepg as a child process to receive audio data packets
over UDP from the console app, and encode each packet to audio WAV
format

  


  2. Pipe out the result of the child process into a GET HTTP endpoint response

  


  



  Browser

  



  

  1. HTML audio element with source value equals to the node js GET
endpoint

  


  



  Problem :

  



  The solution is giving a good result, but only for one device(one to one), which is not what I want to achieve.

  



  I've tried many solutions to make it applicable to a wide range of devices, such as using working threads and forking a child process, but none of them changes the result.

  



  I believe that I've to make some changes to the node js implementation, so here I'll share it with you, hoping to get a clue to solve the problem.

  



  var express = require("express");
var app = express();
var children = require("child_process");

var port = 5001;
var host = "192.168.1.230";

app.listen(port, host, () => {
  console.log("Server running at http://" + host + ":" + port + "/");
});

app.get('/stream', (req, res) => {
  const ffmpegCommand = "ffmpeg";
  var ffmpegOptions =
    "-f s16le -ar 48000 -ac 2 -i udp://192.168.1.230:65535 -f wav -";

  var ffm = children.spawn(ffmpegCommand, ffmpegOptions.split(" "));

  res.writeHead(200, { "Content-Type": "audio/wav; codecs=PCM" });
  ffm.stdout.pipe(res);
});


  



  If someone interested to see the full implementation, please let me know.

  


• (Ffmpeg) How to play live audio in the browser from received UDP packets using Ffmpeg ?

  26 octobre 2022, par Yousef Alaqra

  I have .NET Core console application which acts as UDP Server and UDP Client

  



  

  • UDP client by receiving audio packet.

  


  • UDP server, by sending each received packet.

  


  



  Here's a sample code of the console app :

  



  static UdpClient udpListener = new UdpClient();
    static IPEndPoint endPoint = new IPEndPoint(IPAddress.Parse("192.168.1.230"), 6980);
    static IAudioSender audioSender = new UdpAudioSender(new IPEndPoint(IPAddress.Parse("192.168.1.230"), 65535));

    static void Main(string[] args)
    {
        udpListener.Client.SetSocketOption(SocketOptionLevel.Socket, SocketOptionName.ReuseAddress, true);
        udpListener.Client.Bind(endPoint);

        try
        {
            udpListener.BeginReceive(new AsyncCallback(recv), null);
        }
        catch (Exception e)
        {
            throw e;
        }

        Console.WriteLine("Press enter to dispose the running service");
        Console.ReadLine();
    }

    private async static void recv(IAsyncResult res)
    {
        byte[] received = udpListener.EndReceive(res, ref endPoint);
        OnAudioCaptured(received);
        udpListener.BeginReceive(new AsyncCallback(recv), null);
    }


  



  On the other side, I have a node js API application, which supposes to execute an FFmpeg command as a child process and to do the following

  



  

  • receive the audio packet as an input from the console app UDP server.

  


  • convert the received bytes into WebM

  


  • pipe out the result into the response.

  


  



  Finally, in the client-side, I should have an audio element with source value equals to the http://localhost:3000

  



  For now, I can only execute this FFmpeg command :

  



  ffmpeg -f  s16le  -ar 48000 -ac 2 -i 'udp://192.168.1.230:65535' output.wav


  



  Which do the following

  



  

  • Receive UDP packet as an input

  


  • Convert the received bytes into the output.wav audio file.

  


  



  How would I execute a child process in the node js server which receives the UDP packets and pipe out the result into the response as Webm ?