Recherche avancée

Médias (1)

Mot : - Tags -/belgique

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

  • Participer à sa traduction

    10 avril 2011

    Vous pouvez nous aider à améliorer les locutions utilisées dans le logiciel ou à traduire celui-ci dans n’importe qu’elle nouvelle langue permettant sa diffusion à de nouvelles communautés linguistiques.
    Pour ce faire, on utilise l’interface de traduction de SPIP où l’ensemble des modules de langue de MediaSPIP sont à disposition. ll vous suffit de vous inscrire sur la liste de discussion des traducteurs pour demander plus d’informations.
    Actuellement MediaSPIP n’est disponible qu’en français et (...)

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

  • avfilter/drawutils : add support for full range

    2 mai 2018, par Paul B Mahol
    avfilter/drawutils : add support for full range

    Signed-off-by : Paul B Mahol <onemda@gmail.com>
    • [DH] libavfilter/drawutils.c
    • [DH] libavfilter/drawutils.h
    • [DH] libavutil/colorspace.h
    • [DH] tests/ref/fate/filter-pixfmts-pad

  • FFMPEG : Fixing frame rate with filter_complex movie filter

    4 mai 2018, par stevendesu

    With some help from @Gyan I came up with the following FFMPEG command which streams 4 videos simultaneously to 4 separate RTMP endpoints, looping the videos infinitely and keeping the audio and video synchronized :

    ffmpeg \
    
    -filter_complex \
    
        "movie=01.mp4:loop=0[v1];[v1]setpts=N/FRAME_RATE/TB[v1];
    
         amovie=01.mp4:loop=0[a1];[a1]asetpts=N/SR/TB[a1];
    
         movie=02.mp4:loop=0[v2];[v2]setpts=N/FRAME_RATE/TB[v2];
    
         amovie=02.mp4:loop=0[a2];[a2]asetpts=N/SR/TB[a2];
    
         movie=03.mp4:loop=0[v3];[v3]setpts=N/FRAME_RATE/TB[v3];
    
         amovie=03.mp4:loop=0[a3];[a3]asetpts=N/SR/TB[a3];
    
         movie=04.mp4:loop=0[v4];[v4]setpts=N/FRAME_RATE/TB[v4];
    
         amovie=04.mp4:loop=0[a4];[a4]asetpts=N/SR/TB[a4]" \
    
    -map "[v1]" -map "[a1]" \
    
        -c:a libfdk_aac \
    
        -c:v libx264 -preset ultrafast \
    
        -b:v 500k -b:a 32k \
    
        -f flv rtmp://output/01 \
    
    -map "[v2]" -map "[a2]" \
    
        -c:a libfdk_aac \
    
        -c:v libx264 -preset ultrafast \
    
        -b:v 500k -b:a 32k \
    
        -f flv rtmp://output/02 \
    
    -map "[v3]" -map "[a3]" \
    
        -c:a libfdk_aac \
    
        -c:v libx264 -preset ultrafast \
    
        -b:v 500k -b:a 32k \
    
        -f flv rtmp://output/03 \
    
    -map "[v4]" -map "[a4]" \
    
        -c:a libfdk_aac \
    
        -c:v libx264 -preset ultrafast \
    
        -b:v 500k -b:a 32k \
    
        -f flv rtmp://output/04

    This is almost perfect, except that it’s doubling my frame rate :

    frame=20822 fps= 46 q=32.0 q=34.0 q=29.0 q=32.0 size=   57617kB time=00:14:28.39 bitrate= 543.5kbits/s speed=1.92x

    Note the speed=1.92x bit. This is causing the live stream to play at double speed, as well.

    (the original video was approximately 24 fps)

  • avcodec/mediacodecdec : wait on first frame after input buffers are full

    25 avril 2018, par Aman Gupta
    avcodec/mediacodecdec : wait on first frame after input buffers are full

    The output_buffer_count==0 special case is no longer required, and
    
can cause spurious EAGAIN to surface to the user when input buffers
    
are filled up. Since the caller now knows if the decoder is accepting
    
new input (via current_input_buffer>=0), let the wait parameter
    
control whether we block or not.
    

    Signed-off-by : Aman Gupta <aman@tmm1.net>
    
Signed-off-by : Matthieu Bouron <matthieu.bouron@gmail.com>
    • [DH] libavcodec/mediacodecdec_common.c
    • [DH] libavcodec/mediacodecdec_common.h

Navigation