
Recherche avancée
Médias (1)
-
The Slip - Artworks
26 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (42)
-
Les autorisations surchargées par les plugins
27 avril 2010, parMediaspip core
autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs -
MediaSPIP v0.2
21 juin 2013, parMediaSPIP 0.2 is the first MediaSPIP stable release.
Its official release date is June 21, 2013 and is announced here.
The zip file provided here only contains the sources of MediaSPIP in its standalone version.
To get a working installation, you must manually install all-software dependencies on the server.
If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...) -
Librairies et binaires spécifiques au traitement vidéo et sonore
31 janvier 2010, parLes logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
Binaires complémentaires et facultatifs flvtool2 : (...)
Sur d’autres sites (9380)
-
FFmpeg NaCl module avformat_open_input (on rtsp stream) returns -5 : I/O error
8 janvier 2016, par Taimoor AlamI want to create an RTSP player in Chrome PNaCl.
I have successfully built the ffmpeg naclport including the following networking flags in the build.sh file for the ffmpeg NaCl port.
—enable network —enable-protocols —enable-demuxer=rtsp —enable-demux=rtp —enable-demuxer=sdp —enable-decoder=h264
Furthermore, I have successfully coded and the linked the ffmpeg NaCl port in my own PNaCl module. I have included the following network permissions in the manifest.json file :
"permissions": [
{
"socket": [
"tcp-listen:*:*",
"tcp-connect:*:*",
"resolve-host:*:*",
"udp-bind:*:*",
"udp-send-to:*:*"
],
}Now once I run the following code, in PNaCl, the avformat_open_input(...) returns -5 or I/O Error :
AVFormatContext* formatContext = avformat_alloc_context();
av_register_all();
avformat_network_init();
const char * stream_path = "rtsp://184.72.239.149/vod/mp4:BigBuckBunny_115k.mov";
int result = avformat_open_input(&formatContext, stream_path ,NULL,NULL);
if(result< 0){
PostMessage("input not opened, result: ");
PostMessage(result);
}else{
PostMessage(std::string("input successfully opened"));
}What am I possibly doing wrong, and why can’t the PNaCl module access the RTSP stream ?
PS. This is a similar question, but it gives no definitive answer.
-
fluent-ffmpeg module : "end" event does not fire
6 décembre 2015, par nduggerI’m using the
fluent-ffmpeg
npm moduleI’ve POSTed a video from my client, and am using
new stream.Readable
to "read" the video Buffer.ffmpeg is converting and saving the file, and everything seems beautiful, but the "end" event never fires.
My code is as follows :
const videoStream = new stream.Readable({
read: function (n) {
this.push(myVideoBuffer);
}
});
ffmpeg(videoStream)
.on('progress', e => console.log(e))
.on('end', () => {
console.log('ended')
videoStream.destroy();
})
.on('error', e => console.error(e))
.save(`${process.cwd()}/media/videos/${Date.now()}.mp4`);I get a log on every progress event, and it does save the video, but the "end" event’s callback never gets called.
I assume this is a bug, since everything else works just fine.
-
lavc : Drop deprecated deinterlace module
28 juillet 2015, par Vittorio Giovara