
Recherche avancée
Médias (1)
-
The Great Big Beautiful Tomorrow
28 octobre 2011, par
Mis à jour : Octobre 2011
Langue : English
Type : Texte
Autres articles (42)
-
La file d’attente de SPIPmotion
28 novembre 2010, parUne file d’attente stockée dans la base de donnée
Lors de son installation, SPIPmotion crée une nouvelle table dans la base de donnée intitulée spip_spipmotion_attentes.
Cette nouvelle table est constituée des champs suivants : id_spipmotion_attente, l’identifiant numérique unique de la tâche à traiter ; id_document, l’identifiant numérique du document original à encoder ; id_objet l’identifiant unique de l’objet auquel le document encodé devra être attaché automatiquement ; objet, le type d’objet auquel (...) -
MediaSPIP Player : les contrôles
26 mai 2010, parLes contrôles à la souris du lecteur
En plus des actions au click sur les boutons visibles de l’interface du lecteur, il est également possible d’effectuer d’autres actions grâce à la souris : Click : en cliquant sur la vidéo ou sur le logo du son, celui ci se mettra en lecture ou en pause en fonction de son état actuel ; Molette (roulement) : en plaçant la souris sur l’espace utilisé par le média (hover), la molette de la souris n’exerce plus l’effet habituel de scroll de la page, mais diminue ou (...) -
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
Sur d’autres sites (6703)
-
Replacing the standard Android H264 software encoder with an ffmpeg based one
10 août 2012, par rubenvbIn Android ICS and later, a new OpenMax IL API version is in use, making old binary blobs useless/unused. This leads to older devices that otherwise run ICS just fine and dandy to have broken video playback (YouTube HQ and IMBD, for example) because Androids fallback software decoder sucks when compared to what ffmpeg can do on the same device (I tested MXPlayer+arm6vfp ffmpeg and a 720p movie played back great).
I am trying to dig through the Android source code to see where and what exactly I could add/replace code to allow the ffmpeg library's awesomeness to be used. The problem is I don't know exactly what code is being used in for example the YouTube app to decode video, or how that's decided.
So I have two options as far as I can tell :
-
Figure out the current software decoder being used, and try to wrap its external interface around ffmpeg, effectively replacing the slow software decoder currently used. The end result would be a single .so I could push to the device.
-
Figure out how to trick Android into thinking an OMX library based on ffmpeg (I have built one succesfully for Android : limoa) and add this somewhere to the list of considered libraries (or better : replace the unusable hardware codec).
As an extension, I'd like to also make camcorder video encoding work through this, so a true integrated solution would be very much wanted. The question is : how, and where, and what ? Searching the Android source tree gives numerous counts of "H264" and related stuff in many different places. I need the lowest and simplest possible, so I can simply wrap the hypothetical
decode(buffer)
function call to use ffmpeg (libavcodec). -
-
how to publish flv file using ffmpeg to RTMP server in `real time` ?
29 octobre 2012, par Akram Berkawywhat i'm trying to do is publishing a
.flv
media file toRTMP
server to let subscribers watch it.
i'm testing to view the stream in several subscribers (theoflaDemo
) and withffplay
.the problem is that ffmpeg publish the 5 minutes .flv file to the server in nearly 20 seconds, in these 20 seconds the stream appear on subscribes, but after that it cuts.
the command i use is :ffmpeg -i file.flv -re -acodec copy -vcodec copy -f flv "rtmp://localhost/oflaDemo/aaa live=1"
how can i force
ffmpeg
to stream the 5 minutes file in 5 minutes, or any other solution.thanks.
-
Will ffmpeg transcoding change the media's duration ?
6 juillet 2012, par MaiTianoFor example, I have a example flv media : 1775818137_1775828481_10344.flv. Only audio data has contained in it. (No video data)
The major properties of this flv are :
_____________________________________________________________________
Format : Flash Video
File size : 87.4 KiB
Duration : 494 hours
Overall bit rate mode : CBR
Overall bit rate : 0 bps
Writing application : Lavf53.4.0
Audio
Format : MPEG Audio
Format version : Version 1
Format profile : Layer 3
Mode : Joint stereo
Mode extension : MS Stereo
Codec ID : 2
Codec ID/Hint : MP3
Duration : 49hours
Bit rate mode : CBR
Bit rate : 64.0 Kbps
Channel(s) : 2 channels
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 13.3 GiB
_____________________________________________________________________Because this is the flv piece generated from the Suse10.0 server, the timestamp may be not correctly wrote into the flv metadata. Therefore, the Duration item listed above is not the real time of it.
I has record the time in its file name.
So, the beginning time is 1775818137 ms
the ending time of this flv is 1775828481 ms
The actual duation of this flv is 10344 ms which is about 10 seconds.**HERE IS MY QUESTION -.- **
When I use ffmpeg to transcode flv fromat into ts format, like this,
./ffmpeg -i 1775818137_1775828481_10344.flv -f mpegts -vn -acodec libfaac -ar 44100 -ab 48k 1775818137_1775828481_10344.ts
Is there possibility that the duration of final gotten ts file is not equal to the duation of original flv file ? In other words, the ts file's duration is not 10344ms.