
Recherche avancée
Médias (1)
-
Rennes Emotion Map 2010-11
19 octobre 2011, par
Mis à jour : Juillet 2013
Langue : français
Type : Texte
Autres articles (45)
-
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 -
Support audio et vidéo HTML5
10 avril 2011MediaSPIP utilise les balises HTML5 video et audio pour la lecture de documents multimedia en profitant des dernières innovations du W3C supportées par les navigateurs modernes.
Pour les navigateurs plus anciens, le lecteur flash Flowplayer est utilisé.
Le lecteur HTML5 utilisé a été spécifiquement créé pour MediaSPIP : il est complètement modifiable graphiquement pour correspondre à un thème choisi.
Ces technologies permettent de distribuer vidéo et son à la fois sur des ordinateurs conventionnels (...) -
De l’upload à la vidéo finale [version standalone]
31 janvier 2010, parLe chemin d’un document audio ou vidéo dans SPIPMotion est divisé en trois étapes distinctes.
Upload et récupération d’informations de la vidéo source
Dans un premier temps, il est nécessaire de créer un article SPIP et de lui joindre le document vidéo "source".
Au moment où ce document est joint à l’article, deux actions supplémentaires au comportement normal sont exécutées : La récupération des informations techniques des flux audio et video du fichier ; La génération d’une vignette : extraction d’une (...)
Sur d’autres sites (7819)
-
uploading video to ftp while transcoding with Xuggler
27 novembre 2013, par HollyI'm trying to transcode a video on a client PC (Win, Linux, IOS - x32 or x64 - all 6) and write the output directly to a ftp server using Xuggler. With pure ffmpeg it would look like this :
ffmpeg -i "local.mp4" -ftp-write-seekable 0 -c:v libx264 -crf 25 -f flv ftp://user:pass@server.net:1234/uploaded.flv
I'm assuming that it must be possible since ffmpeg can do it and Xuggler is supposed to be a wrapper for ffmpeg. I got it working using
exec("ffmeg")
but it needs to work on all 6 OS mentioned above.I tried to addapt this example : https://groups.google.com/forum/# !msg/xuggler-users/QeFTxqgc8Bg/0j1ntsl3tI0J by just using a
ftp://user:pass@server.net:1234/uploaded.flv
as the url but that does not work. Xuggler is unable to create a container based on such an url.I guess I should be able to write into an OutputStream and have ftp4j read from that stream and write to ftp. What would I need to consider for that ?
Failing all else I could write into a temp file and upload that, but I really don't like that as a solution.
-
Can someone please provide me with a code example of how to make Xuggler write to ftp directly ?
-
As a side question. I'm still looking into how to best capture data for displaying the progress in the GUI. So far I found :
IMediaListener onWritePacket(IWritePacketEvent event)
which I would register to the writer. However I'm not sure how to get the details ffmped reports (current compression, output size so far). The only useful info I found so far is the TimeStamp. Any help on that would also be most welcome.
-
-
uploading video to ftp while transcoding with Xuggler in JAVA on multiple platforms
27 novembre 2013, par HollyI'm trying to transcode a video on a client PC (Win, Linux, Mac OS - x32 or x64 - all 6) and write the output directly to a ftp server using the JAVA lib Xuggler. With pure ffmpeg it would look like this :
ffmpeg -i "local.mp4" -ftp-write-seekable 0 -c:v libx264 -crf 25 -f flv ftp://user:pass@server.net:1234/uploaded.flv
I'm assuming that it must be possible since ffmpeg can do it and Xuggler is supposed to be a wrapper for ffmpeg. I got it working using
exec("ffmeg")
but it needs to work on all 6 OS mentioned above.I tried to addapt this example : https://groups.google.com/forum/# !msg/xuggler-users/QeFTxqgc8Bg/0j1ntsl3tI0J by just using a
ftp://user:pass@server.net:1234/uploaded.flv
as the url but that does not work. Xuggler is unable to create a container based on such an url.I guess I should be able to write into an OutputStream and have ftp4j read from that stream and write to ftp. What would I need to consider for that ?
Failing all else I could write into a temp file and upload that, but I really don't like that as a solution.
-
Can someone please provide me with a code example of how to make Xuggler write to ftp directly ?
-
As a side question. I'm still looking into how to best capture data for displaying the progress in the GUI. So far I found :
IMediaListener onWritePacket(IWritePacketEvent event)
which I would register to the writer. However I'm not sure how to get the details ffmped reports (current compression, output size so far). The only useful info I found so far is the TimeStamp. Any help on that would also be most welcome.
-
-
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);
});