
Recherche avancée
Autres articles (40)
-
Submit bugs and patches
13 avril 2011Unfortunately a software is never perfect.
If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
You may also (...) -
Les formats acceptés
28 janvier 2010, parLes commandes suivantes permettent d’avoir des informations sur les formats et codecs gérés par l’installation local de ffmpeg :
ffmpeg -codecs ffmpeg -formats
Les format videos acceptés en entrée
Cette liste est non exhaustive, elle met en exergue les principaux formats utilisés : h264 : H.264 / AVC / MPEG-4 AVC / MPEG-4 part 10 m4v : raw MPEG-4 video format flv : Flash Video (FLV) / Sorenson Spark / Sorenson H.263 Theora wmv :
Les formats vidéos de sortie possibles
Dans un premier temps on (...) -
Initialisation de MediaSPIP (préconfiguration)
20 février 2010, parLors de l’installation de MediaSPIP, celui-ci est préconfiguré pour les usages les plus fréquents.
Cette préconfiguration est réalisée par un plugin activé par défaut et non désactivable appelé MediaSPIP Init.
Ce plugin sert à préconfigurer de manière correcte chaque instance de MediaSPIP. Il doit donc être placé dans le dossier plugins-dist/ du site ou de la ferme pour être installé par défaut avant de pouvoir utiliser le site.
Dans un premier temps il active ou désactive des options de SPIP qui ne le (...)
Sur d’autres sites (9254)
-
uwp app throw error when install from package but works fine in any mode when run directly launching from visual studio
30 septembre 2020, par Abhishek SharmaI have created an app wrapping FFmpeg in uwp now for the requirement
I have all the major dll of FFmpeg and then set to content and copy always in property
now when I launch the app installed from the visual studio in any mode weather release, debug, x86,x64 it works fine but as I created a package and then install the app and run it, it throws an error where it says that dll not found not directly but says file not found which is because of dll because I face that problem in debug mode before and it's because of dll not available to uwp
you can look at the project here : https://github.com/AbhiSharma9350/Winfftool


-
fluent-ffmpeg throw er when concatenate videos
2 mai 2020, par Romualdo Arrechea HernándezI'm using fluent-ffmpeg version 2.1.2.
When I execute the current code the output show off a error message :



var ffmpeg = require('fluent-ffmpeg');
var glob= require('glob');
ffmpeg.setFfmpegPath("/usr/bin/ffmpeg");
ffmpeg.setFfprobePath("/usr/bin/ffprobe");
var command = ffmpeg();

const path='/home/username/somefolder/*/output.mp4';

var videos=glob.sync(path);
var output="./output.mp4";
videos.map(video=>command.addInput(video));
command.mergeToFile(output);




the console output>



**events.js:287
 throw er; // Unhandled 'error' event
 ^

Error: ffmpeg exited with code 1: Conversion failed!

 at ChildProcess.<anonymous> (/home/r/Projects/prueba/node_modules/fluent-ffmpeg/lib/processor.js:182:22)
 at ChildProcess.emit (events.js:310:20)
 at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
Emitted 'error' event on FfmpegCommand instance at:
 at emitEnd (/home/r/Projects/prueba/node_modules/fluent-ffmpeg/lib/processor.js:424:16)
 at endCB (/home/r/Projects/prueba/node_modules/fluent-ffmpeg/lib/processor.js:544:13)
 at handleExit (/home/r/Projects/prueba/node_modules/fluent-ffmpeg/lib/processor.js:170:11)
 at ChildProcess.<anonymous> (/home/r/Projects/prueba/node_modules/fluent-ffmpeg/lib/processor.js:182:11)
 at ChildProcess.emit (events.js:310:20)
 at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)**
</anonymous></anonymous>



The video should be created, but it's unable to concat. Some clue ?


-
Why ffmpeg launched on a google cloud function can throw "Error : Output stream error : Maximum call stack size exceeded" ?
15 décembre 2020, par Stepan ShilinI'm trying to process video files with ffmpeg running on google cloud functions. Video files are downloaded from a google file storage, processed in stream by fluent-ffmpeg and streamed to a new google storage file. It works on smaller files but throws an "Output stream error : Maximum call stack size exceeded" on larger files.



I tried running the code on a normal pc, and I haven't encountered this error, even with larger files.



These are the parameters I deploy the function with



gcloud functions deploy $FUNCTION_NAME --runtime nodejs8 --trigger-http --timeout=180 --memory 256




This is the code that processes video



function cutVideo({videoUrl, startTime, duration, dist}) {
 return ffmpeg(videoUrl)
 .outputOptions('-movflags frag_keyframe+empty_moov')
 .videoCodec('copy')
 .audioCodec('copy')
 .format('mp4')
 .setStartTime(startTime)
 .setDuration(duration);
}

const sectionStream = cutVideo({
 videoUrl,
 startTime,
 duration,
 dist: tempFilePath,
});

const outputStream = bucket.file(sectionPath)
.createWriteStream({
 metadata: {
 contentType: config.contentType,
 },
 public: true,
});




Actual error stack looks like this



Error: Output stream error: Maximum call stack size exceeded
 at Pumpify.<anonymous> (/srv/node_modules/fluent-ffmpeg/lib/processor.js:498:34)
 at emitOne (events.js:121:20)
 at Pumpify.emit (events.js:211:7)
 at Pumpify.Duplexify._destroy (/srv/node_modules/duplexify/index.js:191:15)
 at /srv/node_modules/duplexify/index.js:182:10
 at _combinedTickCallback (internal/process/next_tick.js:132:7)
 at process._tickDomainCallback (internal/process/next_tick.js:219:9)
 RangeError: Maximum call stack size exceeded
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:28:31)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)
 at value.map.v (/srv/node_modules/@google-cloud/projectify/build/src/index.js:30:32)
 at Array.map (<anonymous>)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:30:23)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)
 at replaceProjectIdToken (/srv/node_modules/@google-cloud/projectify/build/src/index.js:37:30)
 at value.map.v (/srv/node_modules/@google-cloud/projectify/build/src/index.js:30:32)
 at Array.map (<anonymous>)
</anonymous></anonymous></anonymous>



What could cause this error on a google cloud function ?