Recherche avancée
Autres articles (64)
-
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 ;
-
Publier sur MédiaSpip
13 juin 2013Puis-je poster des contenus à partir d’une tablette Ipad ?
Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir -
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 (6075)
-
Merge commit ’3a0576702825423abecb32627c530dbc4c0f73bc’
14 février 2014, par Michael NiedermayerMerge commit ’3a0576702825423abecb32627c530dbc4c0f73bc’
* commit ’3a0576702825423abecb32627c530dbc4c0f73bc’ :
h264 : store current_sps_id inside the current spsConflicts :
libavcodec/h264.c
libavcodec/h264_ps.cThe current_sps_id is not removed as it used in security related code.
Merged-by : Michael Niedermayer <michaelni@gmx.at>
-
Error : ffmpeg exited with code 2 - Docker Container
15 avril 2020, par Vincenzo AstaI created a Docker Container that when I run I get this error (Why do I get this error ? It works locally) :



{
 "message": "Error: ffmpeg exited with code 2
 at ChildProcess.<anonymous> (/app/lib/node_modules/fluent-ffmpeg/lib/processor.js:182:22)
 at emitTwo (events.js:126:13)
 at ChildProcess.emit (events.js:214:7)
 at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12)"
}
</anonymous>


Below, the part of code where I get the error (in particular the execution goes into reject) :



var ffmpeg = require('fluent-ffmpeg');

module.exports = (sourcePath, outputPath, af, outputFormat="mp3") => {
 return new Promise((resolve, reject) => {
 let proc = new ffmpeg({ source: sourcePath, nolog: true });
 proc.audioQuality(0);
 proc.audioFilters(af);
 proc.setFfmpegPath(__dirname + "/ffmpeg-20180325-5b31dd1-win64-static/bin/ffmpeg.exe");
 proc.toFormat(outputFormat).on('end', function () {
 resolve();
 })
 .on('error', function (err) {
 reject(err);
 })
 .saveToFile(outputPath);
 })
}



My Dockerfile :



FROM node:8.11.1

WORKDIR /app

COPY package*.json /app/

RUN npm install

COPY . /app/

EXPOSE 8000

CMD [ "node", "app.js" ]



My package.json :



{
 "name": "",
 "version": "1.0.0",
 "description": "",
 "main": "app.js",
 "author": "",
 "license": "ISC",
 "dependencies": {
 "express": "^4.16.4",
 "azure-storage": "^2.1.0",
 "crypto": "^0.0.3",
 "ffmpeg": "^0.0.4",
 "ffmpeg-normalize": "^1.3.0",
 "fluent-ffmpeg": "^2.1.2",
 "fs": "^0.0.1-security",
 "jmespath": "0.15.0",
 "mp3-duration": "^1.1.0",
 "striptags": "^3.1.1"
 }
}


-
avformat/avidec : add support for recognizing HEVC fourcc when demuxing
24 août 2019, par Marton Balintavformat/avidec : add support for recognizing HEVC fourcc when demuxing
Some security cams generate this, as well as some versions of VirtualDub and
VLC so support for _reading_ such files is justified.Fixes ticket #7110.
See also this discussion : https://patchwork.ffmpeg.org/patch/8744/
Signed-off-by : Marton Balint <cus@passwd.hu>
Syndiquer tout le site
