
Recherche avancée
Autres articles (38)
-
Personnaliser les catégories
21 juin 2013, parFormulaire de création d’une catégorie
Pour ceux qui connaissent bien SPIP, une catégorie peut être assimilée à une rubrique.
Dans le cas d’un document de type catégorie, les champs proposés par défaut sont : Texte
On peut modifier ce formulaire dans la partie :
Administration > Configuration des masques de formulaire.
Dans le cas d’un document de type média, les champs non affichés par défaut sont : Descriptif rapide
Par ailleurs, c’est dans cette partie configuration qu’on peut indiquer le (...) -
Contribute to documentation
13 avril 2011Documentation is vital to the development of improved technical capabilities.
MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
To contribute, register to the project users’ mailing (...) -
Selection of projects using MediaSPIP
2 mai 2011, parThe examples below are representative elements of MediaSPIP specific uses for specific projects.
MediaSPIP farm @ Infini
The non profit organizationInfini develops hospitality activities, internet access point, training, realizing innovative projects in the field of information and communication technologies and Communication, and hosting of websites. It plays a unique and prominent role in the Brest (France) area, at the national level, among the half-dozen such association. Its members (...)
Sur d’autres sites (4495)
-
Revision a16794dd31 : Revert "Remove Wextra warnings from vp9_sad.c" This reverts commit 7ab9a9587b96
15 mai 2014, par Jim BankoskiChanged Paths :
Modify /test/sad_test.cc
Modify /vp8/common/rtcd_defs.pl
Modify /vp8/common/sad_c.c
Modify /vp8/common/variance.h
Modify /vp8/encoder/mcomp.c
Modify /vp8/encoder/rdopt.c
Modify /vp9/common/vp9_rtcd_defs.pl
Modify /vp9/encoder/vp9_encodeframe.c
Modify /vp9/encoder/vp9_mbgraph.c
Modify /vp9/encoder/vp9_mcomp.c
Modify /vp9/encoder/vp9_rdopt.c
Modify /vp9/encoder/vp9_sad.c
Modify /vp9/encoder/vp9_variance.h
Revert "Remove Wextra warnings from vp9_sad.c"This reverts commit 7ab9a9587b96db4edce6be916c1f02297a9555ff
Nightly test http://build.webmproject.org/jenkins/view/libvpx-nightly-
tests/job/libvpx%20unit%20tests%20(valgrind-2)/arch=x86_64-linux-
gcc,filter=-*VP8* :*Large.*/276/consoleFailed
This patch did not address all the assembly issues
some of the vp8 assembly counts on 5 arguments being passed in to this function :one example : vp8_sad8x16_wmt
Please address or split this into vp9 and vp8 patches.
Change-Id : I78afcc171649894f887bb8ee3c66de24aaddc7ca
-
How to upload files to Azure Blob Stotage like FTP ?
25 janvier 2016, par CG-GuyI am able to upload files from my
ffmpeg
app to an FTP using this path :ftp://[user:password]@server[:port]/MyFolder/video/video.flv
How do I achieve the same thing in Azure Blob ? I have tried this path :
https://[account-name].blob.core.windows.net/video/video.flv /DestKey:[account-storage-key]
But that doesn’t seem to work. TCP connection shows the app is making a connection with the Azure account to the remote address
104.208.XXX.XX
and remote port443
. However, it drops the connection and starts attempts to reconnect repeatedly. It will then time out after countless attempts and crash the app. I have also tried/>
without success. The same thing happens. It attempts connecting to the remote address and port80
.The FFMPEG app has full access to firewall ports and the app communication shell show files are published without errors. System is a Server 2008 R2 unit on-site, not VM.
-
"Error opening filters !" when using fluent-ffmpeg with Node
3 février 2015, par doremiI’m trying to get a basic example of html5 video streaming working in an express node app, but I keep running into ffmpeg errors that I’m unsure of how to resolve.
The input file/stream is the sample.mp4 located here.
Complete example :
var ffmpeg = require('fluent-ffmpeg');
var express = require('express');
var fs = require('fs');
var sampleApp = express();
var videoApp = express();
var SAMPLE_SERVER_PORT = 3000;
var VIDEO_SERVER_PORT = 5000;
sampleApp.get('/:video', function (req, res) {
var videoURL = 'http://localhost:' + VIDEO_SERVER_PORT + '/' + req.params.video;
return res.end('<video controls="controls" src=" + videoURL +"></video>');
});
videoApp.get('/:video', function(req, res) {
res.statusCode = 200;
res.setHeader('content-type','video/mp4');
var stream = fs.createReadStream('./samples/' + req.params.video);
var proc = ffmpeg(stream)
.format('mp4')
.size('320x?')
.videoBitrate('512k')
.videoCodec('libx264')
.fps(24)
.audioBitrate('96k')
.audioCodec('aac')
.audioFrequency(22050)
.audioChannels(2)
.on('error', function(err) {
console.log('an error happened: ' + err.message);
})
.pipe(res, { end:true });
});
var server = sampleApp.listen(SAMPLE_SERVER_PORT, function () {
console.log('Example app listening at http://%s:%s', server.address().address, SAMPLE_SERVER_PORT);
});
var videoServer = videoApp.listen(VIDEO_SERVER_PORT, function () {
console.log('Video Server listening at http://%s:%s', server.address().address, VIDEO_SERVER_PORT);
});The error (via console) :
an error happened: ffmpeg exited with code 1: Error opening filters!
ffmpeg configuration :
./configure --prefix=/usr/local --enable-gpl --enable-nonfree --enable-libass \
--enable-libfdk-aac --enable-libfreetype --enable-libmp3lame --enable-libopus \
--enable-libtheora --enable-libvorbis --enable-libvpx --enable-libx264 --enable-libxvid --enable-libfaac --enable-libfdk-aacAny input would be greatly appreciated.