
Recherche avancée
Médias (1)
-
SPIP - plugins - embed code - Exemple
2 septembre 2013, par
Mis à jour : Septembre 2013
Langue : français
Type : Image
Autres articles (102)
-
Sélection de projets utilisant MediaSPIP
29 avril 2011, parLes exemples cités ci-dessous sont des éléments représentatifs d’usages spécifiques de MediaSPIP pour certains projets.
Vous pensez avoir un site "remarquable" réalisé avec MediaSPIP ? Faites le nous savoir ici.
Ferme MediaSPIP @ Infini
L’Association Infini développe des activités d’accueil, de point d’accès internet, de formation, de conduite de projets innovants dans le domaine des Technologies de l’Information et de la Communication, et l’hébergement de sites. Elle joue en la matière un rôle unique (...) -
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 (...) -
Ajouter notes et légendes aux images
7 février 2011, parPour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
Modification lors de l’ajout d’un média
Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)
Sur d’autres sites (10063)
-
How to debug ffmpeg-static in a AWS Lambda layer
31 mars 2021, par boblapointeI have an AWS Lambda layer containing nodejs ffmpeg-static. Calling "ffmpeg.path" will return the correct location of the ffmpeg executable in the layer.



But any call to ffmpeg will stop silently, making it impossible for me to know what caused the error. Here is my test function :



const exec = require( "child_process" ).exec
const ffmpeg = require( "ffmpeg-static" )
exports.handler = async (event, context, callback ) => {
 console.log( ffmpeg.path ) // Outputs: "/opt/nodejs/node_modules/ffmpeg-static/bin/linux/x64/ffmpeg"
 exec( ffmpeg.path + " -version",
 function( error, stdout, stderr ) {
 console.log( stdout ) // Nothing
 console.log( stderr ) // Nothing
 if ( error ) {
 console.log( error ) // Nothing
 }
 }
 )




The exec() callback is never triggered. How can I identify the problem ?


-
Unable to parse option value xxx.srt as image size Error applying option 'original_size' to filter 'subtitles' : Invalid argument
6 décembre 2023, par gabri yañez vallverduconst strFile = `http://localhost:8080/public/srtFiles/nombreArchivo.srt`
 
const localSubtitleFilePath = path.join(__dirname, 'nombreArchivo.srt');

 axios.get(strFile, { responseType: 'arraybuffer' })
 .then(response => {
 fs.writeFileSync(localSubtitleFilePath, Buffer.from(response.data));

 const outputFilePath = path.join(__dirname, '../../../public/videosSubtitled', `${videoName}`);
 console.log('Subtitle File Path:', localSubtitleFilePath);
 console.log('Output File Path:', outputFilePath);

 exec(`ffmpeg -i ${tempFilePath} -vf subtitles=${localSubtitleFilePath} ${outputFilePath}`, function(error, stdout, stderr) {
 if (error) {
 console.log(error);
 console.log(stdout);
 console.log(stderr);
 console.log("❌ Something went wrong!");
 res.status(500).json({ success: false, message: 'Error al crear el video subtitulado' });
 } else {
 fs.unlinkSync(tempFilePath);
 fs.unlinkSync(localSubtitleFilePath);
 console.log("Done! 🍿 😎");
 }
 });
 })
 .catch(error => {
 console.log("Error downloading subtitle file:", error);
 res.status(500).json({ success: false, message: 'Error al descargar el archivo de subtítulos' });
 });



Hi, I'm trying to add subtitles to a video with ffmpeg in a NodeJS app, but I have this error :
[Parsed_subtitles_0 @ 0000024140111580] Unable to parse option value xxx.srt as image size Error applying option 'original_size' to filter 'subtitles' : Invalid argument


I have tried to send the srt file by a public url and by a local file, but I have also a mistake.


-
Ffmpeg returning error code 1 in AWS Lamda function
14 avril 2018, par TometoyouI’m running a lambda function which takes an
mp4
video, and adds a watermark of apng
image over the top of it in the bottom right hand corner (with a10px
margin). It then outputs that image to a temporary location. It keeps failing withError code 1
, but that isn’t very helpful. I’m using a binary version offfmpeg
that is specified in the main directory of the code. I know thatffmpeg
is set up correctly due to using it in another lambda function in this way, which works. But adding an overlay fails. Here is the relevant part of my code :function addWatermark(next) {
var ffmpeg = child_process.spawn("ffmpeg", [
"-i", target, // url to stream from
"-i", watermarkPath,
"-filter_complex" ,"overlay=x=W-w-10:y=H-h-10:format=rgb,format=yuv420p",
"-c:a", "copy",
"pipe:1"
]);
ffmpeg.on("error", function(err) {
console.log(err);
})
ffmpeg.on("close", function(code) {
if (code != 0 ) {
console.log("child process exited with code " + code); // Always exits here.
} else {
console.log("Processing finished !");
}
tmpFile.end();
next(code);
});
tmpFile.on("error", function(err) {
console.log("stream err: ", err);
});
ffmpeg.on("end", function() {
tmpFile.end();
})
ffmpeg.stdout.pipe(tmpFile)
.on("error", function(err){
console.log("error while writing: ",err);
});
}Can anyone spot what may be wrong ?
UPDATE
I’ve managed to print out some more logs, I’m getting the error :
[NULL @ 0x42923e0] Unable to find a suitable output format for 'pipe:1'