Recherche avancée

Médias (1)

Mot : - Tags -/embed

Autres articles (78)

  • Amélioration de la version de base

    13 septembre 2013

    Jolie sélection multiple
    Le plugin Chosen permet d’améliorer l’ergonomie des champs de sélection multiple. Voir les deux images suivantes pour comparer.
    Il suffit pour cela d’activer le plugin Chosen (Configuration générale du site > Gestion des plugins), puis de configurer le plugin (Les squelettes > Chosen) en activant l’utilisation de Chosen dans le site public et en spécifiant les éléments de formulaires à améliorer, par exemple select[multiple] pour les listes à sélection multiple (...)

  • Creating farms of unique websites

    13 avril 2011, par

    MediaSPIP platforms can be installed as a farm, with a single "core" hosted on a dedicated server and used by multiple websites.
    This allows (among other things) : implementation costs to be shared between several different projects / individuals rapid deployment of multiple unique sites creation of groups of like-minded sites, making it possible to browse media in a more controlled and selective environment than the major "open" (...)

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

  • libavcodec/8bps : Check that line lengths fit within the buffer

    22 août 2022, par Michael Niedermayer
    libavcodec/8bps : Check that line lengths fit within the buffer

    Fixes : Timeout
    
Fixes : undefined pointer arithmetic
    
Fixes : 50330/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_EIGHTBPS_fuzzer-5436287485607936
    

    Found-by : continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpeg
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavcodec/8bps.c

  • doc/ffplay : put keystrokes to decrease and increase volume on the same line

    20 avril 2022, par Stefano Sabatini
    doc/ffplay : put keystrokes to decrease and increase volume on the same line

    Fix trac issue http://trac.ffmpeg.org/ticket/7832
    • [DH] doc/ffplay.texi

  • avformat/rtpdec_mpeg4 : Fix integer parameters size check in SDP fmtp line

    24 juillet 2019, par Olivier Maignial
    avformat/rtpdec_mpeg4 : Fix integer parameters size check in SDP fmtp line

    === PROBLEM ===
    

    I was trying to record h264 + aac streams from an RTSP server to mp4 file. using this command line :
    
    ffmpeg -v verbose -y -i "rtsp ://<ip>/my_resources" -codec copy -bsf:a aac_adtstoasc test.mp4
    

    FFmpeg then fail to record audio and output this logs :
    
    [rtsp @ 0xcda1f0] The profile-level-id field size is invalid (40)
    
    [rtsp @ 0xcda1f0] Error parsing AU headers
    
    ...
    
    [rtsp @ 0xcda1f0] Could not find codec parameters for stream 1 (Audio : aac, 48000 Hz, 1 channels) : unspecified sample format
    

    In SDP provided by my RTSP server I had this fmtp line :
    
    a=fmtp:98 streamType=5 ; profile-level-id=40 ; mode=AAC-hbr ; config=1188 ; sizeLength=13 ; indexLength=3 ; indexDeltaLength=3 ;
    

    In FFmpeg code, I found a check introduced by commit 24130234cd9dd733116d17b724ea4c8e12ce097a. It disallows values greater than 32 for fmtp line parameters.
    
RFC-4566 (SDP : Session Description Protocol) do not give any limit of size on interger parameters given in an fmtp line.
    

    However, In RFC-6416 (RTP Payload Format for MPEG-4 Audio/Visual Streams) give examples of "profile-level-id" values for AAC, up to 55.
    

    === FIX ===
    

    As each parameter may have its own min and max values
    
I propose to introduce a range for each parameter.
    
For this patch I used RFC-3640 and ISO/IEC 14496-1 as reference for validity ranges.
    

    This patch fix my problem and I now can record my RTSP AAC stream to mp4.
    
It has passed the full fate tests suite sucessfully.
    

    Signed-off-by : Olivier Maignial <olivier.maignial@smile.fr>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libavformat/rtpdec_mpeg4.c

Navigation