Recherche avancée

Médias (17)

Mot : - Tags -/wired

Autres articles (81)

  • Les tâches Cron régulières de la ferme

    1er décembre 2010, par

    La gestion de la ferme passe par l’exécution à intervalle régulier de plusieurs tâches répétitives dites Cron.
    Le super Cron (gestion_mutu_super_cron)
    Cette tâche, planifiée chaque minute, a pour simple effet d’appeler le Cron de l’ensemble des instances de la mutualisation régulièrement. Couplée avec un Cron système sur le site central de la mutualisation, cela permet de simplement générer des visites régulières sur les différents sites et éviter que les tâches des sites peu visités soient trop (...)

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

Sur d’autres sites (9932)

  • 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. 


    3. trimming the first 28 bytes of each received packet
    4. 


    5. and send the processed packet over UDP.
    6. 


    



    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. 


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


    



    Browser

    



      

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


    



    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. 


    3. trimming the first 28 bytes of each received packet
    4. 


    5. and send the processed packet over UDP.
    6. 


    



    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. 


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


    



    Browser

    



      

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


    



    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.

    


  • get specific metadata with ffprobe

    1er mai, par mikem

    I'm having a terrible time getting one single line of metadata from ffprobe.

    


    I'm running this command :

    


    


    ffprobe -show_entries 'stream_tags :
format_tags=com.apple.quicktime.creationdate' -loglevel error
IMG_9931.MOV

    


    


    And I get this output

    


    


    [STREAM]

    


    TAG:creation_time=2022-05-14T20:24:55.000000Z

    


    TAG:language=und

    


    TAG:handler_name=Core Media Video

    


    TAG:encoder=H.264

    


    [/STREAM]

    


    [STREAM]

    


    TAG:creation_time=2022-05-14T20:24:55.000000Z

    


    TAG:language=und

    


    TAG:handler_name=Core Media Audio

    


    [/STREAM]

    


    [STREAM]

    


    TAG:creation_time=2022-05-14T20:24:55.000000Z

    


    TAG:language=und

    


    TAG:handler_name=Core Media Metadata

    


    [/STREAM]

    


    [STREAM]

    


    TAG:creation_time=2022-05-14T20:24:55.000000Z

    


    TAG:language=und

    


    TAG:handler_name=Core Media Metadata

    


    [/STREAM]

    


    [STREAM]

    


    TAG:creation_time=2022-05-14T20:24:55.000000Z

    


    TAG:language=und

    


    TAG:handler_name=Core Media Metadata

    


    [/STREAM]

    


    [FORMAT]

    


    TAG:com.apple.quicktime.creationdate=2022-05-14T16:24:55-0400

    


    [/FORMAT]

    


    


    But the only thing I want returned is

    


    


    com.apple.quicktime.creationdate=2022-05-14T16:24:55-0400

    


    


    I've searched and searched but I can't find any examples of pulling a single specific value of metadata.

    


    In actuality, I really just want the value of com.apple.quicktime.creationdate... ie "2022-05-14T16:24:55-0400"

    


    I know I can grep and awk my way through it, but it seems like there should be a way to do it with ffprobe alone given all of the options it has. I just can't figure out how.

    


    How can I do this ? Any help would be appreciated.