
Recherche avancée
Médias (1)
-
The Slip - Artworks
26 septembre 2011, par
Mis à jour : Septembre 2011
Langue : English
Type : Texte
Autres articles (64)
-
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 -
Le plugin : Podcasts.
14 juillet 2010, parLe problème du podcasting est à nouveau un problème révélateur de la normalisation des transports de données sur Internet.
Deux formats intéressants existent : Celui développé par Apple, très axé sur l’utilisation d’iTunes dont la SPEC est ici ; Le format "Media RSS Module" qui est plus "libre" notamment soutenu par Yahoo et le logiciel Miro ;
Types de fichiers supportés dans les flux
Le format d’Apple n’autorise que les formats suivants dans ses flux : .mp3 audio/mpeg .m4a audio/x-m4a .mp4 (...) -
HTML5 audio and video support
13 avril 2011, parMediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
For older browsers the Flowplayer flash fallback is used.
MediaSPIP allows for media playback on major mobile platforms with the above (...)
Sur d’autres sites (9253)
-
Install dependencies for Python ffmpeg library "av" (ImportError : libx264.so missing)
7 septembre 2018, par Make42In Python I installed the library
av
(which is a Python API for ffmpeg) into my conda environment withconda install -c conda-forge av=0.4.0
, but I when Iimport av
into my python script, I get the error messageImportError: libx264.so.138: cannot open shared object file: No such file or directory
on my Linux Kubuntu 14.4 machine. How can I resolve this issue ?
Wild guess : My Kubuntu repositories are a little old, so I cannot update ffmepg further and I guess this is why libx264 is missing, but am not sure.
-
Delay in displaying a video stream after streaming by libavformat
15 janvier 2014, par Blue SkyI am using libavformat library to stream a video at a network address like udp ://127.0.0.1:1000. I use ffplay to display the received video stream at the network address. However, the video appears few second later (e.g. 5 6 seconds) at ffplay on the same machine. Do you know what is the reason ?
More info :
I have written my own streaming application using libavformat. When I stream a 3sec 1080p video at 25fps, ffplay does not show anything. If I repeat streaming the same video once again, this time, ffplay starts displaying the previous streamed video as well as the current video. So, it looks like ffplay waits for a buffer to be filled up by some amount, and then displays the stream. But am I correct ?
-
How to capture a log message coming out of node JS spawn ffmpeg command
17 janvier 2014, par keenanI am trying to find the silent parts of an audio recording. This command does exactly what I want on my local machine.
ffmpeg -i http://twf-audio.s3.amazonaws.com/uploads/DBC50460-9A5C-4174-9885-07337A582D58_1377839443598_tell.m4a -af silencedetect=n=-40dB:d=0.2 -f null -
It sends a bunch of messages to the command line including these last three which are the lines of data that I need. (for reference : ffmpeg silencedetect docs)
[silencedetect @ 0x7feea040cf20] silence_start : 0.0321995
[silencedetect @ 0x7feea040cf20] silence_end : 0.975238 | silence_duration : 0.943039
[silencedetect @ 0x7feea040cf20] silence_start : 1.47184
I cannot figure out how to get that message out. Here is the nodejs code that is running. The only event that is triggered is the 'exit'. I thought that "pipe:1" sends output to stdout but that does not do anything.
var ffmpeg = spawn('ffmpeg', ['-i',filename,'-af','silencedetect=n=-40dB:d=0.2', '-f', 'null','-y', 'pipe:1' ]);
ffmpeg.on('message', function(data) {
console.log('ffmpeg2 PARENT got message:', JSON.stringify(data));
});
ffmpeg.stdout.on('data', function(data) {
console.log('ffmpeg stdout data = '+JSON.stringify(data) );
});
ffmpeg.on('exit', function (code, signal) {
console.log('child process exited with code:' + code + ' signal:' + signal);
});