Recherche avancée

Médias (2)

Mot : - Tags -/map

Autres articles (34)

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

  • HTML5 audio and video support

    13 avril 2011, par

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

  • De l’upload à la vidéo finale [version standalone]

    31 janvier 2010, par

    Le 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 (6793)

  • Streaming protocol relay without involving codec

    4 décembre 2015, par kiran_g

    I am trying to use libav to relay an RTSP stream. It involves PULLing the stream from an IP camera and then PUSHing to wowza.

    The video encoding in the IP camera stream is h264. To enable h264 in my libav application I need to enable x264. But as x264 is GPL, it will not work with my business plan.

    My questions is whether libav (ffmpeg) can be made to work like a dumb relay which is encoding-agnostic ? so that I dont need to integrate x264 with ffmpeg.

    This SO post says that I can use the "copy" argument, but does that allow me to exclude x264 ?

    BTW, is x264 actually needed by ffmpeg for decoding h264 ? Is x264 only used in encoding ?

    See here for my current code.

  • Streaming protocol relay without involving codec

    4 décembre 2015, par kiran_g

    I am trying to use libav to relay an RTSP stream. It involves PULLing the stream from an IP camera and then PUSHing to wowza.

    The video encoding in the IP camera stream is h264. To enable h264 in my libav application I need to enable x264. But as x264 is GPL, it will not work with my business plan.

    My questions is whether libav (ffmpeg) can be made to work like a dumb relay which is encoding-agnostic ? so that I dont need to integrate x264 with ffmpeg.

    This SO post says that I can use the "copy" argument, but does that allow me to exclude x264 ?

    BTW, is x264 actually needed by ffmpeg for decoding h264 ? Is x264 only used in encoding ?

    See here for my current code.

  • Rebuilding Website for sharing videos

    22 novembre 2015, par Léo Le Gall

    Some friends and I run a sport forum with a decent user base. A lot of users wanted the ability to share video clips of their tricks. We didn’t really think anyone would use a video website that we made, so I built a really simple one just to see if the users would really use it. I hosted the video site on a $10 VPS, and it got blown away. The site was literally garbage, it was not visually appealing and the performance was just sad. Just as expected really, since this was just a test site. Since our test project was a success, we want to create a new and more polished site for the videos.

    The website is really simple, and probably not optimized in any way at the moment. I will try to explain in details what the website does. The user uploads some video files in format X, the website combines them and converts (using ffmpeg) the final video to mp4(so it can be served with a html5 video player). The users gets a link (example.com/randomvideo) where he can see the video through a html5 player serving the mp4 file(just default html5, nothing fancy). The videos only contains highlights, and the final video is always under 1 minute, most are around 30 seconds.

    Currently everything happens on the same server, both the video processing and the video serving. I can try to show how it works :

    1. User uploads some videos
    2. Servers stores the videos in a new random folder
    3. Combine videos and convert to mp4 (ffmpeg)
    4. Move final video(random name) to directory containing processed videos
    5. Store the name of the video file in the database (for website to serve it)
    6. Delete directory used to process the videos

    I want to rebuild the website’s architecture to make it able to scale and handle heavy load. I have never done this before and I am currently making a plan how to do this. My plan is at the moment :

    1. Seperate servers for processing videos and viewing videos (all VPS in the start)
    2. Utilize content delivery network for serving static files
    3. Utilize load balancers both for servers proccesing and serving

    I don’t really know what I should do with database(s). Can I do with one database or should use more ? They do not need to store sensitive information, since the auth in done through an API. They only need store information about the videos. I have experience with postgresql, mysql and redis, but I am not limited to those. What would you recommend in terms of scaleability ?

    I will appriciate all the feedback I can get regarding my plan and what to do about databases. I know this might be a bit vague, so please ask me if I have forgotten anything imporant. Thanks for reading.