Recherche avancée

Médias (2)

Mot : - Tags -/kml

Autres articles (111)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Supporting all media types

    13 avril 2011, par

    Unlike most software and media-sharing platforms, MediaSPIP aims to manage as many different media types as possible. The following are just a few examples from an ever-expanding list of supported formats : images : png, gif, jpg, bmp and more audio : MP3, Ogg, Wav and more video : AVI, MP4, OGV, mpg, mov, wmv and more text, code and other data : OpenOffice, Microsoft Office (Word, PowerPoint, Excel), web (html, CSS), LaTeX, Google Earth and (...)

  • Support de tous types de médias

    10 avril 2011

    Contrairement à beaucoup de logiciels et autres plate-formes modernes de partage de documents, MediaSPIP a l’ambition de gérer un maximum de formats de documents différents qu’ils soient de type : images (png, gif, jpg, bmp et autres...) ; audio (MP3, Ogg, Wav et autres...) ; vidéo (Avi, MP4, Ogv, mpg, mov, wmv et autres...) ; contenu textuel, code ou autres (open office, microsoft office (tableur, présentation), web (html, css), LaTeX, Google Earth) (...)

Sur d’autres sites (6205)

  • Revision d1cff2deb1 : Code cleanup in bitstream code. Lower case variable names, less code. Change-I

    9 avril 2013, par Dmitry Kovalev

    Changed Paths : Modify /vp9/encoder/vp9_bitstream.c Code cleanup in bitstream code. Lower case variable names, less code. Change-Id : I1abc8f592ad2343ab5c76fe2d16262741a4a894a

  • FFmpeg Auto Level, Auto Color etc similar to YouTube's Auto-Fix

    22 juin 2019, par Umer

    I used to use YouTube Auto-Fix which presumably auto fixed levels, color, contrast and added a bit of vibrance (it was almost always a bit high saturated which i kinda liked).

    I am looking for an alternate in ffmpeg. I tried using -vf pp=al but it only lightens the video.

    Any ideas ?

    P.S. I can do this in Premiere/After Effects but am looking for a ffmpeg solution.

  • How to Add PulseAudio Server to quay.io/browser/google-chrome-stable Docker Image for Audio Support with Screen Recording ?

    17 avril, par Ahmed Seddik Bouchiba

    I’m trying to set up an environment for recording the screen of a Chrome browser running in a Docker container, and I need to enable audio support. I’m using the quay.io/browser/google-chrome-stable:133.0.6943.98-6 image for the browser and quay.io/aerokube/xvfb:21.1 for the virtual framebuffer to capture the screen.

    


    However, I’m facing an issue where audio is not supported in the Chrome Docker image, which I need for recording. The setup involves using FFmpeg in a separate container to stream the recorded video, but without audio from the browser, this setup isn’t complete.

    


    I’m looking for guidance on how to add a PulseAudio server to the Chrome image to enable audio support. Specifically :

    


    How can I configure the Docker image quay.io/browser/google-chrome-stable:133.0.6943.98-6 to support PulseAudio?

Are there any considerations or best practices when adding PulseAudio to a headless browser Docker container?

Is it possible to run the PulseAudio server in a separate container and link it to the Chrome container, or should it be included directly in the Chrome container?


    


    Any help on adding PulseAudio support to this Chrome Docker image would be greatly appreciated !

    


    Additional Context :

    


    The goal is to run a headless Chrome browser with audio support to record the browser’s activities (both video and audio) and stream it using FFmpeg.

I’m using Docker Compose to orchestrate the containers but haven’t figured out how to integrate PulseAudio into the setup effectively.


    


    Thanks in advance !