
Recherche avancée
Médias (1)
-
Carte de Schillerkiez
13 mai 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (38)
-
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...) -
Changer son thème graphique
22 février 2011, parLe thème graphique ne touche pas à la disposition à proprement dite des éléments dans la page. Il ne fait que modifier l’apparence des éléments.
Le placement peut être modifié effectivement, mais cette modification n’est que visuelle et non pas au niveau de la représentation sémantique de la page.
Modifier le thème graphique utilisé
Pour modifier le thème graphique utilisé, il est nécessaire que le plugin zen-garden soit activé sur le site.
Il suffit ensuite de se rendre dans l’espace de configuration du (...) -
Automated installation script of MediaSPIP
25 avril 2011, parTo overcome the difficulties mainly due to the installation of server side software dependencies, an "all-in-one" installation script written in bash was created to facilitate this step on a server with a compatible Linux distribution.
You must have access to your server via SSH and a root account to use it, which will install the dependencies. Contact your provider if you do not have that.
The documentation of the use of this installation script is available here.
The code of this (...)
Sur d’autres sites (7299)
-
How to broadcast live audio in node js (1 to many)
19 juin 2020, par Yousef AlaqraI'm trying stream live audio to a wide range of clients in a web browser.



My current solution :



Dotnet core 3.1 console application



- 

- receive the audio data over UDP
- trimming the first 28 bytes of each received packet
- and send the processed packet over UDP.









Node JS



- 

- 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
- Pipe out the result of the child process into a GET HTTP endpoint response







Browser



- 

- 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 do I broadcast live audio in Node.js ?
20 juin 2020, par Yousef AlaqraI'm trying stream live audio to a wide range of clients in a web browser.



My current solution :



Dotnet core 3.1 console application



- 

- receive the audio data over UDP
- trimming the first 28 bytes of each received packet
- and send the processed packet over UDP.









Node JS



- 

- 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
- Pipe out the result of the child process into a GET HTTP endpoint response







Browser



- 

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


-
stream webcam using ffmpeg to live555
16 juin 2014, par John QualisI am new to live555.
I want to stream my webcam from a windows 7 (64-bit) machine behind home LAN using ffmpeg as the encoder to a live555 server running on a Debian 64-bit linux machine in a data center over the WAN. I want to send a H.264 RTP/UDP stream from ffmpeg and the "testOnDemandRTSPServer" should send out RTSP streams to clients that connect to it.
I am using the following ffmpeg command which sends UDP data to port 1234, IP address AA.BB.CC.DD
.\ffmpeg.exe -f dshow -i video="Webcam C170":audio="Microphone (3- Webcam C170)" -an
-vcodec libx264 -f mpegts udp://AA.BB.CC.DD:1234On the linux server I am running the testOnDemandRTSPServer on port 5555 which expects raw UDP data from from AA:BB:CC:DD:1234. I try to open the rtsp stream in VLC using
rtsp://AA.BB.CC.DD:5555/mpeg2TransportStreamFromUDPSourceTest
But I get nothing in VLC. What am I doing wrong ? How can I fix it ?