Recherche avancée
Autres articles (60)
-
Demande de création d’un canal
12 mars 2010, parEn fonction de la configuration de la plateforme, l’utilisateur peu avoir à sa disposition deux méthodes différentes de demande de création de canal. La première est au moment de son inscription, la seconde, après son inscription en remplissant un formulaire de demande.
Les deux manières demandent les mêmes choses fonctionnent à peu près de la même manière, le futur utilisateur doit remplir une série de champ de formulaire permettant tout d’abord aux administrateurs d’avoir des informations quant à (...) -
Des sites réalisés avec MediaSPIP
2 mai 2011, parCette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page. -
Contribute to a better visual interface
13 avril 2011MediaSPIP is based on a system of themes and templates. Templates define the placement of information on the page, and can be adapted to a wide range of uses. Themes define the overall graphic appearance of the site.
Anyone can submit a new graphic theme or template and make it available to the MediaSPIP community.
Sur d’autres sites (8054)
-
nodejs fluent-ffmpeg process is too slow
22 août 2021, par snovoselI'm attempting to run the following ffmpeg command using fluent-ffmpeg and locally this command will take between 5-10 seconds. I have the same service deployed to a digital ocean server with 4CPU and 32GB of RAM as a test and the command will hang for sometimes up to 40 minutes. I'm uploading files 15mb-50mb in size as .mov files or .mp4 files. In all cases this has been too slow to be feasible... How can I begin to debug this ?


const handleVideoResize = async (filePath) => {
 try {
 const { height, width } = await getVideoDimensions(filePath); // ffmpeg probe to get the dimensions

 const newWidth = 423;
 const newHeight = 534;

 const x = width - (newWidth / newHeight) * height;

 const destFilePath = path.resolve(`./tmp/final-${uuidv4()}.webm`);

 const outputStream = fs.createWriteStream(destFilePath);

 FFmpeg()
 .input(filePath)
 .input(path.resolve("assets/watermark.png"))
 .complexFilter([
 `[0]crop=${width - x}:${height},scale=${newWidth}:${newHeight}[a]`,
 "[1]scale=iw*0.2:-1[wm];[a][wm]overlay=x=(W-w)-15:y=(H-h)-15",
 `colorchannelmixer=aa=0.6[1]`
 ])
 .format("webm")
 .outputFormat("webm")
 .on("start", () => {
 printText("ffmpeg child process spawned ---");
 })
 .on("end", () => {
 printText("video stream finished");
 })
 .on("error", err => {
 printError("err ffmpeg", err);
 })
 .output(outputStream)
 .run();
 } catch (error) {
 printError("error handle video resize", error);
 return;
 }
};


-
lavc/vaapi_encode : add support for maxframesize
5 mai 2022, par Linjie Fulavc/vaapi_encode : add support for maxframesize
Add support for max frame size :
- max_frame_size (bytes) to indicate the max allowed size for frame.Control each encoded frame size into target limitation size by adjusting
whole frame's average QP value. The driver will use multi passes to
adjust average QP setp by step to achieve the target, and the result
may not strictly guaranteed. Frame size may exceed target alone with
using the maximum average QP value. The failure always happens on the
intra(especially the first intra frame of a new GOP) frames or set
max_frame_size with a very small number.example cmdline :
ffmpeg -hwaccel vaapi -vaapi_device /dev/dri/renderD128 -f rawvideo \
-v verbose -s:v 352x288 -i ./input.yuv -vf format=nv12,hwupload \
-c:v h264_vaapi -profile:v main -g 30 -rc_mode VBR -b:v 500k \
-bf 3 -max_frame_size 40000 -vframes 100 -y ./max_frame_size.h264Max frame size was enabled since VA-API version (0, 33, 0), but query
is available since (1, 5, 0). It will be passed as a parameter in picParam
and should be set for each frame.Signed-off-by : Linjie Fu <linjie.fu@intel.com>
Signed-off-by : Fei Wang <fei.w.wang@intel.com> -
lavc/vaapi_encode : Enable block level bitrate control
8 mars 2024, par Fei Wang
Syndiquer tout le site
