Recherche avancée

Médias (1)

Mot : - Tags -/vidéo

Autres articles (97)

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

  • Multilang : améliorer l’interface pour les blocs multilingues

    18 février 2011, par

    Multilang est un plugin supplémentaire qui n’est pas activé par défaut lors de l’initialisation de MediaSPIP.
    Après son activation, une préconfiguration est mise en place automatiquement par MediaSPIP init permettant à la nouvelle fonctionnalité d’être automatiquement opérationnelle. Il n’est donc pas obligatoire de passer par une étape de configuration pour cela.

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

Sur d’autres sites (8498)

  • What's the easiest way to convert ogg to webm on Node without ffmpeg ?

    12 mars 2023, par Evert

    I'm working on a Telegram bot that can receive voice messages and then let OpenAI's Whisper transcribe them and then respond using OpenAI's chat completions API.

    


    Anyway, Whisper does accept a webm file as an input, but not an ogg file. Even though ironically, from what I've read, a webm container can contain a pure ogg file as its soundtrack.

    


    I can't use ffmpeg, because I'm deploying this as a serverless function (on Vercel for now) and I have no guarantee that ffmpeg will be installed there. But I was thinking, since webm is simply a container file which can contain the raw ogg opus codec as the soundtrack, wouldn't it be possible to just take the binary audio data that I can get from Telegram, using const audioData = await response.arrayBuffer(), and just add some bytes to the beginning and end of it that represent the webm container ?

    


    If yes, then can someone please tell me which bytes I'd need to add exactly ?

    


  • Revision 29748 : Mise à jour de l’ensembles des fonctions ... on peut passer maintenant à ...

    8 juillet 2009, par kent1@… — Log

    Mise à jour de l’ensembles des fonctions ... on peut passer maintenant à l’encodage multiple

  • ffmpeg - how to build paths on windows

    7 décembre 2016, par Thomas

    I am building a command line for ffmpeg and I am going crazy. It seems like the tool has an abnormal path system and I can’t find any reliable documentation.

    Using Windows, I have a movie file at : "d :\test\movie.mp4"
    if we take the following command :

    fmpeg -i <myfile> -vf "select=gt(scene\,0.5), scale=640:360" -vsync vfr thumbnails%03d.png
    
</myfile>

    I tried to build the the following ways :

    d:\test\movie.mp4
    
d:\\test\movie.mp4
    
d\\:\\test\movie.mp4
    
d:\\:/test/movie.mp4

    It seems like only the 4th one work when called from a C# program, but doesn’t work in command line.

    Is there any documentation that explains this properly ? from what I gather, the drive letter has to be followed by double slashed then the column and I can’t figure out the reason.

Navigation