
Recherche avancée
Médias (1)
-
Revolution of Open-source and film making towards open film making
6 octobre 2011, par
Mis à jour : Juillet 2013
Langue : English
Type : Texte
Autres articles (55)
-
Websites made with MediaSPIP
2 mai 2011, parThis page lists some websites based on MediaSPIP.
-
Creating farms of unique websites
13 avril 2011, parMediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...) -
Les tâches Cron régulières de la ferme
1er décembre 2010, parLa 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 (...)
Sur d’autres sites (6295)
-
Homebridge camera ffmpeg : rtsp stream accessible with vlc but not with Home app
20 mars 2023, par someoneI can access the stream of my esp32 cam with vlc but it doesn't load in home app. Here is my config :


{
 "bridge": {
 "name": "Homebridge 963D",
 "username": "0E:B6:BD:6E:66:9B",
 "port": 51600,
 "pin": "399-77-791",
 "advertiser": "bonjour-hap"
 },
 "accessories": [],
 "platforms": [
 {
 "name": "Config",
 "port": 8581,
 "platform": "config"
 },
 {
 "name": "Camera FFmpeg",
 "cameras": [
 {
 "name": "cam1",
 "videoConfig": {
 "source": "-i rtsp://192.168.178.118:8554/mjpeg/1"
 }
 }
 ],
 "platform": "Camera-ffmpeg"
 }
 ]
}



the homebridge logs didn´t helped too. There is no video, so the problem is in homebridge ffmpeg


-
How see if the client aborted the request in nodejs
9 février 2023, par PitzhoI'm trying do a mp4 converter, but if the client cancel the request, continues the conversion, how I stop the conversion if the client cancel the request ?


Code from conversor :


// Start the ffmpeg child process
 const ffmpegProcess = cp.spawn(ffmpeg, [
 // Remove ffmpeg's console spamming
 '-loglevel', '8', '-hide_banner',
 // Redirect/Enable progress messages
 '-progress', 'pipe:3',
 // Set inputs
 '-i', 'pipe:4',
 '-i', 'pipe:5',
 // Map audio & video from streams
 '-map', '0:a',
 '-map', '1:v',
 // Keep encoding
 '-c:v', 'copy',
 // Define output file
 token + formato,
 ], {
 windowsHide: true,
 stdio: [
 /* Standard: stdin, stdout, stderr */
 'inherit', 'inherit', 'inherit',
 /* Custom: pipe:3, pipe:4, pipe:5 */
 'pipe', 'pipe', 'pipe', 'pipe'
 ],
 });

 ffmpegProcess.stdio[3].on('data', (err) => {
 console.log(res.status())
 });
 
 audio.pipe(ffmpegProcess.stdio[4]);
 video.pipe(ffmpegProcess.stdio[5]);
 
 ffmpegProcess.stdio[6].on('error', (err) => {
 // Remover token do objeto
 delete inUseTokens[token];
 res.status(500).send(err.message);
 });

 ffmpegProcess.stdio[6].on('close', () => {
 console.log("convertido!")
 res.render('downloated', {formato: formato, title: titulo, token: token, thumbnail: thumbnail, seconds: seconds})
 })
 });



I don't know how I can solve this...


-
Fluent-ffmpeg Invalid data found when processing input error only when the second request is received
31 décembre 2022, par koji tanakaI am using Node.js for backend to use ffmpeg. To use ffmpeg, I adopted fluent-ffmpeg. This is working perfectly except for one problem. That is when I send video from client side SPA(single page application) to the server-side for the "second" time, node application crashes.


What I did is saving the received video in the backend folder, which is made in the process, and taking a snapshot of the video.
This code actually works everytime after restarting the server, but once I used this route and try another time, the error message "Invalid data found when processing input video
./received/${receivedName}
" comes up.

app.post("/convert", fileUpload({ createParentPath: true }), async function (req, res) {
 makeDir(receivedVideoDirectory);
 const receivedName = Object.keys(req.files)[0];
 const directoryName = receivedName.substring(0, receivedName.indexOf("."));

 const receivedFile = req.files[receivedName];
 transcodedSegFolder = `./public/transcoded/${dirName}`;
 console.log("transcoded segment file folder is here", transcodedSegFolder);
 makeDir(transcodedSegFolder);

 fs.open(`./received/${receivedName}`, 'w', (err, fd) => {
 if (err) throw err;
 fs.writeFile(fd, receivedFile["data"], function (err) {
 if (err) {
 return console.log("Err in write file ", err);
 }
 console.log("The file was saved!", receivedName);
 fs.close(fd, (err) => {
 if (err) throw err;
 });
 });
 });

 ffmpeg(`./received/${receivedName}`)
 .takeScreenshots(
 {
 count: 1,
 timemarks: ['00:00:01.000'],
 folder: './public/thumbnails',
 filename: dirName
 }).on('error', function(err) {
 console.log('screenshot error happened: ' + err.message);
 }).on('end', function(err) {
 console.log('Screenshot process finished: ');
 });



Probably some program keeps working, but I cannot find it. Any help is appreciated. Thank you.