Recherche avancée

Médias (1)

Mot : - Tags -/MediaSPIP 0.2

Autres articles (21)

  • Support audio et vidéo HTML5

    10 avril 2011

    MediaSPIP 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 (...)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Déploiements possibles

    31 janvier 2010, par

    Deux types de déploiements sont envisageable dépendant de deux aspects : La méthode d’installation envisagée (en standalone ou en ferme) ; Le nombre d’encodages journaliers et la fréquentation envisagés ;
    L’encodage de vidéos est un processus lourd consommant énormément de ressources système (CPU et RAM), il est nécessaire de prendre tout cela en considération. Ce système n’est donc possible que sur un ou plusieurs serveurs dédiés.
    Version mono serveur
    La version mono serveur consiste à n’utiliser qu’une (...)

Sur d’autres sites (5801)

  • How can I best utilize an AWS service to segment a video into smaller chunks and then combine them back to together ? [on hold]

    19 avril 2018, par Justin Malin

    I am trying to do processing on videos uploaded to AWS S3 using an AWS Lambda function in Python. However, FFmpeg and ffmpeg-python (as far as I am aware) are unable to process objects and must do processing on stored files. Lambda only allows for 500 MB of storage in the /tmp/ folder, thus limiting the size of video that I can do processing on.

    If there is an alternative to FFmpeg that allows me to work on object files that I am unaware of, that would be a reasonable solution because I can scale up the memory of the Lambda function (although there is still a limit).

    Alternatively, I have looked into segmenting the video using AWS Elastic Transcoder, but I do not think I can dynamically segment the video using that service. If there is a service similar to this that could segment the video into individual frames (and back), that would be even better.

    I have also considered using AWS EC2, but I would only be using the EC2 service to segment videos sporadically, so it would be a waste to constantly have a server that capable running. If I use the AWS Elastic Beanstalk, would it automatically start a more powerful instance of EC2 to do the video segmentation (and reformation) when that is called and revert back to a much smaller instance when dormant ?

    Essentially, I would like to know if there are any services (preferably within AWS) that allow me to segment a video into shorter videos or into each frame at-will.

  • Run 3 Docker images together as a single service

    20 juin 2018, par kitce

    I want to run 3 Docker images as a single service. They are the official nginx, jrottenberg/ffmpeg and a custom image.

    The custom image will return video files for HTTP requests on port 80, e.g. http:////video.mp4.

    I want to make the video files available for HLS in M3U8 playlist (or other better formats ?).

    The main idea is as follows :

    • Encode video.mp4, output video.m3u8 and segment files with ffmpeg
    • Serve the video.m3u8 and segment files with Nginx
    • The final and the only available web service of the container is http:///.m3u8.
    • Encode only when someone is requesting it (i.e. trigger the encoding when the first request comes, stop encoding and delete segment files when nobody requests it)

    I tested the HLS part with ffmpeg and it works. I am just not sure about how to put Nginx and ffmpeg to work together.

  • avformat/mpegtsenc : use increasing numbers in default service names

    2 août 2019, par Marton Balint
    avformat/mpegtsenc : use increasing numbers in default service names

    Maybe we should use service ID instead of increasing numbers ?
    

    Signed-off-by : Marton Balint <cus@passwd.hu>
    • [DH] libavformat/mpegtsenc.c

Navigation