Recherche avancée

Médias (1)

Mot : - Tags -/portrait

Autres articles (71)

  • Les vidéos

    21 avril 2011, par

    Comme les documents de type "audio", Mediaspip affiche dans la mesure du possible les vidéos grâce à la balise html5 .
    Un des inconvénients de cette balise est qu’elle n’est pas reconnue correctement par certains navigateurs (Internet Explorer pour ne pas le nommer) et que chaque navigateur ne gère en natif que certains formats de vidéos.
    Son avantage principal quant à lui est de bénéficier de la prise en charge native de vidéos dans les navigateur et donc de se passer de l’utilisation de Flash et (...)

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

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

Sur d’autres sites (13058)

  • How to correct crop image using FFMPEG&XILINX

    17 mai 2023, par Dmytro

    I use AWS vt1 with Xilinx SDK and FFMPEG. All from the AWS box with pre-built SDK and so on.
I need to extract frames from fullHD but scale it to 480p
I stuck with it. Could someone help with the correct options ?

    


    I have this Python-based code :

    


    
        # If the video is greater than 480p, resize the frames to 480p
        if height > 480:
            command = [
                ffmpeg_path,
                '-c:v', 'mpsoc_vcu_h264',
                '-i', temp_video,
                '-filter_complex',
                'multiscale_xma=outputs=1: out_1_width=848: out_1_height=480: out_1_rate=half:[b]; [b]xvbm_convert[b1]',
                '-pix_fmt', 'yuv420p',
                '-ss', str(median_time),
                '-map', '[b1]',
                '-vframes', '1',
                '-q:v', '2',
                '-f', 'image2pipe',
                '-vcodec', 'mjpeg',
                '-y', '-'
            ]
        else:  # Preserve the original resolution
            command = [
                ffmpeg_path,
                '-c:v', 'mpsoc_vcu_h264',
                '-i', temp_video,
                '-vf', 'xvbm_convert',
                '-pix_fmt', 'yuv420p',
                '-ss', str(median_time),
                '-vframes', '1',
                '-q:v', '2',
                '-f', 'image2pipe',
                '-vcodec', 'mjpeg',
                '-y', '-'
            ]
            output = subprocess.run(command, capture_output=True)
            frame = output.stdout



    


    The second option with '-vf', 'xvbm_convert', work perfectly.
But the issue with the first.

    


  • Is it possible to fetch some key-frames of a video by using the HTTP Range header

    9 décembre 2020, par pvd

    I've read the SO problem , and it seems not applying to my specific case.

    


    Is it possible to fetch some key-frames of a video from web server by the HTTP Range header ? For example, for a 30 seconds duration video, we'd like to analysis the I-frame around 00:00:02, 00:00:15, 00:00:28.

    


    I need to analysis the videos from internal web server to detect if there's specific watermarks in it and some other analysis.

    


    Since the first I-frame might be invalid sometimes(Logo for example), we were planning to extract the I-frame from the 00:00:02, the middle I-frame, and the last 2nd second I-frame.

    


    For example, for a 30 seconds duration video, we'd like to analysis the I-frame around 00:00:02, 00:00:15, 00:00:28.

    


    We could make it works while download the whole video, since most of the data we downloaded from the server are not being used. I was wondering if maybe we could only use the HTTP Range header to download partial data and analysis it ?

    


  • aarch64 : NEON intrinsics dct_unquantize_h263.

    17 mai 2014, par James Yu
    aarch64 : NEON intrinsics dct_unquantize_h263.

    Intrinsics only used on aarch64 since the existing ARMv7 NEON asm
    
is slightly faster (Cortex-A9, gcc-4.8, micro-benchmarks and full
    
decoding time).
    

    Signed-off-by : James Yu <james.yu@linaro.org>
    
Signed-off-by : Janne Grunau <janne-libav@jannau.net>
    • [DBH] libavcodec/mpegvideo.c
    • [DBH] libavcodec/mpegvideo.h
    • [DBH] libavcodec/neon/Makefile
    • [DBH] libavcodec/neon/mpegvideo.c

Navigation