Recherche avancée

Médias (0)

Mot : - Tags -/xmlrpc

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

Autres articles (72)

  • Use, discuss, criticize

    13 avril 2011, par

    Talk to people directly involved in MediaSPIP’s development, or to people around you who could use MediaSPIP to share, enhance or develop their creative projects.
    The bigger the community, the more MediaSPIP’s potential will be explored and the faster the software will evolve.
    A discussion list is available for all exchanges between users.

  • MediaSPIP v0.2

    21 juin 2013, par

    MediaSPIP 0.2 est la première version de MediaSPIP stable.
    Sa date de sortie officielle est le 21 juin 2013 et est annoncée ici.
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Comme pour la version précédente, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

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

  • hevc : Simplify logical check

    2 octobre 2015, par Vittorio Giovara
    hevc : Simplify logical check

    The intended meaning is "if this block is the first block in a slice then
    
its left boundary is a slice boundary". Silence a logical-not-parentheses
    
warning from gcc.
    • [DBH] libavcodec/hevc.c

  • avcodec/cbs_h2645 : Treat slices without data as invalid

    9 décembre 2019, par Andreas Rheinhardt
    avcodec/cbs_h2645 : Treat slices without data as invalid

    Slices that end after their header (meaning slices after the header
    
without any data before the rbsp_stop_one_bit or possibly without any
    
rbsp_stop_one_bit at all) are invalid and are now dropped. This ensures
    
that one doesn't run into two asserts in cbs_h2645_write_slice_data().
    

    Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
    
Fixes : 19629/clusterfuzz-testcase-minimized-ffmpeg_BSF_H264_METADATA_fuzzer-5676822528524288
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/cbs_h2645.c

  • Proportion for the values of maxrate, mnrate and bufsize for encoding videos for streaming purpose and past duration too large warning

    15 décembre 2015, par himanshu nautiyal

    can you please tell me about minrate, maxrate and bufsize. And is it necessary to give maxrate and minrate for encoding videos for streaming purpose. Actually I understood the meaning and functions of minrate, maxrate and bufsize through ffmpeg documents but I am not finding any solution of what would be difference in between the values of these three.

    for example : I am using this command
    ffmpeg -y -i testing.mp4 -c:a libfdk_aac -ac 2 -ab 128k -c:v libx264 -r 24 -g 24 -b:v 2m -maxrate 1m -bufsize 1m -vf scale=1920*1080 aa.mp4

    but I am not sure if this -b:v 2m -maxrate 1m bufsize 1m is in correct propotions or not. My output is fine but I don’t want any problem on working real time. Moreover, I am also getting the following warning

    Past duration 0.634361 too large
    Past duration 0.674370 too large
    Past duration 0.714363 too large 0kB time=00:00:01.32 bitrate= 0.3kbits/s

    Past duration 0.754372 too large
    Past duration 0.794365 too large
    Past duration 0.834373 too large
    Past duration 0.874367 too large
    Past duration 0.914360 too large
    Past duration 0.954369 too large

    thanks in advance

Navigation