
Recherche avancée
Autres articles (112)
-
MediaSPIP 0.1 Beta version
25 avril 2011, parMediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Mise à jour de la version 0.1 vers 0.2
24 juin 2013, parExplications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...) -
Personnaliser en ajoutant son logo, sa bannière ou son image de fond
5 septembre 2013, parCertains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;
Sur d’autres sites (7615)
-
FFMPEG spawn promise not resolving
24 décembre 2020, par fitzmodeI have a problem where running
ffmpeg
withspawn
using the event listener API forclose
orexit
events works fine but when I try to convertspawn
into aPromise
it does not resolve.

I'm


This works fine


const ls = spawn(ffmpeg_static.path,`-i movie.mov movie.mp4`.split(" ");

 //Listen for processing close
 ls.on("close", (code) => {
 console.log(`child process exited with code ${code}`);
 
 });




function pspawn(args) {
 
 // *** Return the promise
 return new Promise(function (resolve, reject) {
 
 const process = spawn(ffmpeg_static.path, args);
//Listen for close and resolve.
 process.on("close", function (code) {
 
 resolve("Complete");
 });
 process.on("error", function (err) {
 // *** Process creation failed
 reject(err);
 });
 });
}

... 

async function run () {
await pspawn(['-i', 'movie.mov','movie.mp4'])
}



I might be missing something simple but can't seem to figure out what it is.


-
avfilter : Remove redundant ff_formats/channel_layouts_unref()
7 août 2020, par Andreas Rheinhardtavfilter : Remove redundant ff_formats/channel_layouts_unref()
ff_add_format() and ff_add_channel_layout() already unref the list upon
error.Reviewed-by : Nicolas George <george@nsup.org>
Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com> -
Trigger exec_pull on http connection
29 octobre 2019, par M. ColeIs it possible to trigger
exec_pull
on http connection ? For example, I have the following Nginx configuration :server {
listen 80;
location /hls {
types {
application/vnd.apple.mpegurl m3u8;
video/mp2t ts;
}
root /mnt;
add_header Cache-Control no-cache;
index index.m3u8 index.ts;
add_header Access-Control-Allow-Origin *;
}
}
}
rtmp {
server {
listen 1935;
allow play all;
application hls {
live on;
exec_options on;
exec_pull /usr/bin/ffmpeg -re -i http://example.com:333/293.m3u8 -c copy -f flv rtmp://localhost:1935/hls/$name;
}
application hls {
live on;
hls on;
hls_path /mnt/hls;
hls_fragment 3s;
}
}
}I would like to have an
exec_pull
triggered on HLS http request.
For example If I request http://my-serverip.com/hls/293.m3u8 then it should start ffmpeg to start creatinghls
files.I’ve been working on this for 5-6 days and could not figure out how to trigger
exec_pull
on http requests.