
Recherche avancée
Autres articles (74)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Gestion des droits de création et d’édition des objets
8 février 2011, parPar défaut, beaucoup de fonctionnalités sont limitées aux administrateurs mais restent configurables indépendamment pour modifier leur statut minimal d’utilisation notamment : la rédaction de contenus sur le site modifiables dans la gestion des templates de formulaires ; l’ajout de notes aux articles ; l’ajout de légendes et d’annotations sur les images ;
-
Dépôt de média et thèmes par FTP
31 mai 2013, parL’outil MédiaSPIP traite aussi les média transférés par la voie FTP. Si vous préférez déposer par cette voie, récupérez les identifiants d’accès vers votre site MédiaSPIP et utilisez votre client FTP favori.
Vous trouverez dès le départ les dossiers suivants dans votre espace FTP : config/ : dossier de configuration du site IMG/ : dossier des média déjà traités et en ligne sur le site local/ : répertoire cache du site web themes/ : les thèmes ou les feuilles de style personnalisées tmp/ : dossier de travail (...)
Sur d’autres sites (10101)
-
get specific metadata with ffprobe
1er mai, par mikemI'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.


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