Recherche avancée

Médias (0)

Mot : - Tags -/flash

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

Autres articles (107)

  • Encoding and processing into web-friendly formats

    13 avril 2011, par

    MediaSPIP automatically converts uploaded files to internet-compatible formats.
    Video files are encoded in MP4, Ogv and WebM (supported by HTML5) and MP4 (supported by Flash).
    Audio files are encoded in MP3 and Ogg (supported by HTML5) and MP3 (supported by Flash).
    Where possible, text is analyzed in order to retrieve the data needed for search engine detection, and then exported as a series of image files.
    All uploaded files are stored online in their original format, so you can (...)

  • Contribute to documentation

    13 avril 2011

    Documentation is vital to the development of improved technical capabilities.
    MediaSPIP welcomes documentation by users as well as developers - including : critique of existing features and functions articles contributed by developers, administrators, content producers and editors screenshots to illustrate the above translations of existing documentation into other languages
    To contribute, register to the project users’ mailing (...)

  • Ajouter notes et légendes aux images

    7 février 2011, par

    Pour pouvoir ajouter notes et légendes aux images, la première étape est d’installer le plugin "Légendes".
    Une fois le plugin activé, vous pouvez le configurer dans l’espace de configuration afin de modifier les droits de création / modification et de suppression des notes. Par défaut seuls les administrateurs du site peuvent ajouter des notes aux images.
    Modification lors de l’ajout d’un média
    Lors de l’ajout d’un média de type "image" un nouveau bouton apparait au dessus de la prévisualisation (...)

Sur d’autres sites (7247)

  • swscale/aarch64 : add vscale specializations

    13 août 2022, par Swinney, Jonathan
    swscale/aarch64 : add vscale specializations

    This commit adds new code paths for vscale when filterSize is 2, 4, or
    
8. By using specialized code with unrolling to match the filterSize we
    
can improve performance.
    

    On AWS c7g (Graviton 3, Neoverse V1) instances :
    
                                 before   after
    
yuv2yuvX_2_0_512_accurate_neon :  558.8    268.9
    
yuv2yuvX_4_0_512_accurate_neon :  637.5    434.9
    
yuv2yuvX_8_0_512_accurate_neon :  1144.8   806.2
    
yuv2yuvX_16_0_512_accurate_neon : 2080.5   1853.7
    

    Signed-off-by : Jonathan Swinney <jswinney@amazon.com>
    
Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] libswscale/aarch64/output.S
    • [DH] libswscale/aarch64/swscale.c

  • Error : ffmpeg exited with code 1 on AWS Lambda

    16 juin 2022, par Hassnain Alvi

    I am using fluent-ffmpeg nodejs package to run ffmpeg for audio conversion on AWS Lambda. I am using this FFmpeg layer for lambda.&#xA;Here is my code

    &#xA;

      const bitrate64 = ffmpeg("file.mp3").audioBitrate(&#x27;64k&#x27;);&#xA;    bitrate64.outputOptions([&#xA;        &#x27;-preset slow&#x27;,&#xA;    &#x27;-g 48&#x27;,&#xA;    "-map", "0:0",&#xA;        &#x27;-hls_time 6&#x27;,&#xA;        &#x27;-master_pl_name master.m3u8&#x27;,&#xA;        &#x27;-hls_segment_filename 64k/fileSequence%d.ts&#x27;&#xA;    ])&#xA;    .output(&#x27;./64k/prog_index.m3u8&#x27;)&#xA;    .on(&#x27;progress&#x27;, function(progress) {&#xA;        console.log(&#x27;Processing 64k bitrate: &#x27; &#x2B; progress.percent &#x2B; &#x27;% done&#x27;)&#xA;    })  &#xA;    .on(&#x27;end&#x27;, function(err, stdout, stderr) {&#xA;        console.log(&#x27;Finished processing 64k bitrate!&#x27;)&#xA;    })&#xA;    .run() &#xA;

    &#xA;

    after running it via AWS lambda I get following error message

    &#xA;

    ERROR   Uncaught Exception  &#xA;{&#xA;    "errorType": "Error",&#xA;    "errorMessage": "ffmpeg exited with code 1: Conversion failed!\n",&#xA;    "stack": [&#xA;        "Error: ffmpeg exited with code 1: Conversion failed!",&#xA;        "",&#xA;        "    at ChildProcess.<anonymous> (/var/task/node_modules/fluent-ffmpeg/lib/processor.js:182:22)",&#xA;        "    at ChildProcess.emit (events.js:198:13)",&#xA;        "    at ChildProcess.EventEmitter.emit (domain.js:448:20)",&#xA;        "    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)"&#xA;    ]&#xA;}&#xA;</anonymous>

    &#xA;

    I don't get any more info so I am not sure what's going on. Can anyone tell me what's wrong here and how can I enable more detailed logs ?

    &#xA;

  • avformat/hls : Be more picky on extensions

    16 janvier, par Michael Niedermayer
    avformat/hls : Be more picky on extensions

    This blocks disallowed extensions from probing
    
It also requires all available segments to have matching extensions to the format
    
mpegts is treated independent of the extension
    

    It is recommended to set the whitelists correctly
    
instead of depending on extensions, but this should help a bit,
    
and this is easier to backport
    

    Fixes : CVE-2023-6602 II. HLS Force TTY Demuxer
    
Fixes : CVE-2023-6602 IV. HLS XBIN Demuxer DoS Amplification
    

    The other parts of CVE-2023-6602 have been fixed by prior commits
    

    Found-by : Harvey Phillips of Amazon Element55 (element55)
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] doc/demuxers.texi
    • [DH] libavformat/hls.c

Navigation