Recherche avancée

Médias (91)

Autres articles (102)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    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 (...)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • Que fait exactement ce script ?

    18 janvier 2011, par

    Ce script est écrit en bash. Il est donc facilement utilisable sur n’importe quel serveur.
    Il n’est compatible qu’avec une liste de distributions précises (voir Liste des distributions compatibles).
    Installation de dépendances de MediaSPIP
    Son rôle principal est d’installer l’ensemble des dépendances logicielles nécessaires coté serveur à savoir :
    Les outils de base pour pouvoir installer le reste des dépendances Les outils de développements : build-essential (via APT depuis les dépôts officiels) ; (...)

Sur d’autres sites (11533)

  • Truly live streaming to Android/iPhone

    4 juillet 2012, par Tsaukpaetra

    I have spent quite a while (past week) trying this to little avail. However, what I want seems completely unheard of. So far, I have reviewed recommendations available through google, which include encoding a static file into multiple static files in different formats, creating a playlist that hosts static files in an m3u8 file (files which get added to the playlist as streaming continues).
    I have also seen ideas involving rtmp, rtsp etc which are completely out of the question because of their incompatibility.
    Ideally, I would have one webpage that would link to the stream (http://server/video.mp4) and/or show it in a webpage (via the video tag). With that in mind, the most likely format would be h264+aac in mp4 container.

    Unfortunately, (and probably because the file has no duration metadata) it does not work. I can use a desktop player (such as VLC) to open the stream and play it, but my iPhone and Android both give their respective "Can't be played" messages.

    I don't think the problem is caused by the devices' ability to stream, for I have made a streaming shoutcast server work just fine (mp3 only).

    Currently, the closest I have become is using the following setup on my win32 machine :

    FFMPEG Command: : ffmpeg -f dshow -i video="Logitech Webcam 200":audio="Microphone (Webcam 200)" -b:v 180k -bt 240k -vcodec libx264 -tune zerolatency -profile:v baseline -preset ultrafast -r 10 -strict -2 -acodec aac -ac 2 -ar 48000 -ab 32k -f flv "udp ://127.0.0.1:1234"

    VLC: : Stream from udp ://127.0.0.1:1234 to http:// :8080/video.mp4 (No Transcoding), basically just to convert the UDP stream into an http-accessible stream.

    Any hints or suggestions would be warmly welcomed !

  • Open avi file with OpenCV : ffmpeg ?

    28 juin 2012, par CTZStef

    This question is related to a previous question I asked here.

    I read on the Willow Garage website dedicated to OpenCV that we do not have to take care of ffmpeg while installing OpenCV since version 1.2.x. Here it is.

    However, some questions asked here on Stackoverflow suggest the contrary.

    So, what should I do ? Do I have to recompile OpenCV and do some special operation related to ffmpeg to get it to, finally, open avi file on my Linux system ?

  • Need help understanding HTML 5 audio/video meta data use and placement

    27 juin 2012, par nicoz

    I have spent a significant amount of time researching HTML 5 audio and video, however I am stuck understanding the encoding of the meta data. It seems that in my research, using programs like Handbrake (ffmpeg) it is recommend to check of "web optimized" (There is also a similar type of setting when exporting from other types of software, like imovie). I have concluded (and correct me if I am wrong) that this has to do with moving the file's meta data to the beginning of the file. This then gives the player/browser the info it requires to play immediately without having to wait to load the entire file.

    So here is where I am confused and the question I need help with

    Does this only apply to the mp4 MOOV atom ? Or is there something similar in .ogv and .webm files ?

Navigation