Recherche avancée

Médias (0)

Mot : - Tags -/flash

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

Autres articles (35)

  • Keeping control of your media in your hands

    13 avril 2011, par

    The vocabulary used on this site and around MediaSPIP in general, aims to avoid reference to Web 2.0 and the companies that profit from media-sharing.
    While using MediaSPIP, you are invited to avoid using words like "Brand", "Cloud" and "Market".
    MediaSPIP is designed to facilitate the sharing of creative media online, while allowing authors to retain complete control of their work.
    MediaSPIP aims to be accessible to as many people as possible and development is based on expanding the (...)

  • Submit bugs and patches

    13 avril 2011

    Unfortunately a software is never perfect.
    If you think you have found a bug, report it using our ticket system. Please to help us to fix it by providing the following information : the browser you are using, including the exact version as precise an explanation as possible of the problem if possible, the steps taken resulting in the problem a link to the site / page in question
    If you think you have solved the bug, fill in a ticket and attach to it a corrective patch.
    You may also (...)

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

  • avformat/id3v2 : Free buffer in decode_str()

    29 juin 2023, par Michael Niedermayer
    avformat/id3v2 : Free buffer in decode_str()

    Fixes : memleak
    
Fixes : 60058/clusterfuzz-testcase-minimized-ffmpeg_dem_IFF_fuzzer-5665259244093440
    

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

  • avcodec/vc1dec : Free sprite_output_frame on error

    16 décembre 2019, par Michael Niedermayer
    avcodec/vc1dec : Free sprite_output_frame on error

    Fixes : memleaks
    
Fixes : 19471/clusterfuzz-testcase-minimized-ffmpeg_AV_CODEC_ID_VC1IMAGE_fuzzer-5688035714269184
    

    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/vc1dec.c

  • libavcodec/vaapi_decode : fix the problem that init_pool_size nb_surface

    11 janvier 2022, par Wenbin Chen
    libavcodec/vaapi_decode : fix the problem that init_pool_size < nb_surface

    For vaapi if the init_pool_size is not zero, the pool size is fixed.
    
This means max surfaces is init_pool_size, but when mapping vaapi
    
frame to qsv frame, the init_pool_size < nb_surface. The cause is that
    
vaapi_decode_make_config() config the init_pool_size and it is called
    
twice. The first time is to init frame_context and the second time is to
    
init codec. On the second time the init_pool_size is changed to original
    
value so the init_pool_size is lower than the reall size because
    
pool_size used to initialize frame_context need to plus thread_count and
    
3 (guarantee 4 base work surfaces). Now add code to make sure
    
init_pool_size is only set once. Now the following commandline works :
    

    ffmpeg -hwaccel vaapi -hwaccel_device /dev/dri/renderD128 \

    - hwaccel_output_format vaapi -i input.264 \

    - vf "hwmap=derive_device=qsv,format=qsv" \

    - c:v h264_qsv output.264
    

    Signed-off-by : Wenbin Chen <wenbin.chen@intel.com>
    • [DH] libavcodec/vaapi_decode.c

Navigation