Recherche avancée

Médias (0)

Mot : - Tags -/interaction

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (56)

  • Encodage et transformation en formats lisibles sur Internet

    10 avril 2011

    MediaSPIP transforme et ré-encode les documents mis en ligne afin de les rendre lisibles sur Internet et automatiquement utilisables sans intervention du créateur de contenu.
    Les vidéos sont automatiquement encodées dans les formats supportés par HTML5 : MP4, Ogv et WebM. La version "MP4" est également utilisée pour le lecteur flash de secours nécessaire aux anciens navigateurs.
    Les documents audios sont également ré-encodés dans les deux formats utilisables par HTML5 :MP3 et Ogg. La version "MP3" (...)

  • Les autorisations surchargées par les plugins

    27 avril 2010, par

    Mediaspip core
    autoriser_auteur_modifier() afin que les visiteurs soient capables de modifier leurs informations sur la page d’auteurs

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

  • ffmpeg : return no chosen output if an uninitialized stream is unavailable

    6 mai 2021, par Jan Ekström
    ffmpeg : return no chosen output if an uninitialized stream is unavailable
    

    Otherwise the rate emulation logic in `transcode_step` never gets
    hit, and the unavailability flag never gets reset, leading to an
    eternal loop with some rate emulation use cases.

    This change was missed during the rework of ffmpeg.c, in which
    encoder initialization was moved further down the time line in
    commit 67be1ce0c6de330b1c10d1d121819d8a74a7b1f5 . Previously,
    as the encoder initialization had happened earlier, this state was
    not possible (flow getting as far as hitting the rate emulation logic,
    yet not having the encoder initialized yet).

    Fixes #9160

    • [DH] fftools/ffmpeg.c
  • People who are using FFmpeg to stream out a live video/audio over RTSP - what is the RTSP-server you are using ?

    26 décembre 2019, par Joseph Matan

    I’m working with this RTSP-server in-order to stream RTSP from FFmpeg (however, this server doesn’t support the codec I need).

    This is the FFmpeg command I’m using, that works with the RTSP-server I’m using (just for example) :

    ffmpeg -f v4l2 -i /dev/video0 -c:v libx264 -intra -an -f rtsp -rtsp_transport tcp rtsp://192.168.1.10:8554/test

    Any suggestions for RTSP-servers that can work with the command above ?

    I’ve tried so many servers, but none of them supports what I need.
    Most of the servers works only on dead-sources (VOD), or directly from devices (like ip-cameras). The server I’m using, is great but don’t support many codecs...

  • Are there people interested in converting ffmpeg source to Go ?

    30 septembre 2018, par No One

    After seeing that Go compiler have been converted from C to Go I thought same for ffmpeg ? Don’t want to go deep into reasons as I think they are obvious. It was very hard to be so close to the have rich library as ffmpeg in other language. It was even hard to make bindings for that scale of library. I’m not enough advanced to start something like this myself, so is there anybody else interested in this ? If yes then where this question worth to be addressed, so people interested in this may have discussion ?

    (Seems not enough obvious so adding some details.)

    For applications which use large amount of commands with different complexity it is hard to read the code as it’s not actually a code. Instead, it’s commands which you will need to understand by reading docs from ffmpeg’s docs page. I had used ffmpeg before in Nodejs and there was lots of logic of manipulating command string. Also sometimes in windows it was ending with cmd limitations error. When you are working with some language it is nice to see whole logic in that language. So you know go ? than you know everything that is happening with this code without even going off from code and reading docs of another application.

    There may be some benefits from executing stuff in goroutines so you can handle concurrency in the way you want not in the way it is implemented in ffmpeg.

    Build faster with Go.

    Less code.

    Possibility to split code into smaller packages.

    Also if you are familiar why community converted compiler from C to Go than I think some reasons will fit too.