Recherche avancée

Médias (91)

Autres articles (112)

  • Personnaliser en ajoutant son logo, sa bannière ou son image de fond

    5 septembre 2013, par

    Certains thèmes prennent en compte trois éléments de personnalisation : l’ajout d’un logo ; l’ajout d’une bannière l’ajout d’une image de fond ;

  • Script d’installation automatique de MediaSPIP

    25 avril 2011, par

    Afin de palier aux difficultés d’installation dues principalement aux dépendances logicielles coté serveur, un script d’installation "tout en un" en bash a été créé afin de faciliter cette étape sur un serveur doté d’une distribution Linux compatible.
    Vous devez bénéficier d’un accès SSH à votre serveur et d’un compte "root" afin de l’utiliser, ce qui permettra d’installer les dépendances. Contactez votre hébergeur si vous ne disposez pas de cela.
    La documentation de l’utilisation du script d’installation (...)

  • La sauvegarde automatique de canaux SPIP

    1er avril 2010, par

    Dans le cadre de la mise en place d’une plateforme ouverte, il est important pour les hébergeurs de pouvoir disposer de sauvegardes assez régulières pour parer à tout problème éventuel.
    Pour réaliser cette tâche on se base sur deux plugins SPIP : Saveauto qui permet une sauvegarde régulière de la base de donnée sous la forme d’un dump mysql (utilisable dans phpmyadmin) mes_fichiers_2 qui permet de réaliser une archive au format zip des données importantes du site (les documents, les éléments (...)

Sur d’autres sites (12785)

  • swscale/aarch64 : use multiply accumulate and increase vector factor to 4

    17 novembre 2019, par Sebastian Pop
    swscale/aarch64 : use multiply accumulate and increase vector factor to 4

    This patch implements ff_hscale_8_to_15_neon with NEON fused multiply accumulate
    
and bumps the vectorization factor from 2 to 4.
    
The speedup is of 25% on Graviton1 A1 instances based on A-72 cpus :
    

    $ ffmpeg -nostats -f lavfi -i testsrc2=4k:d=2 -vf bench=start,scale=1024x1024,bench=stop -f null -
    
before : t:0.040303 avg:0.040287 max:0.040371 min:0.039214
    
after :  t:0.032168 avg:0.032215 max:0.033081 min:0.032146
    

    The speedup is of 39% on Graviton2 m6g instances based on Neoverse-N1 cpus :
    
$ ffmpeg -nostats -f lavfi -i testsrc2=4k:d=2 -vf bench=start,scale=1024x1024,bench=stop -f null -
    
before : t:0.019446 avg:0.019423 max:0.019493 min:0.019181
    
after :  t:0.014015 avg:0.014096 max:0.015018 min:0.013971
    

    Tested with `make check` on aarch64-linux.
    

    Signed-off-by : Sebastian Pop <spop@amazon.com>
    
Reviewed-by : Jean-Baptiste Kempf <jb@videolan.org>
    
Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
    • [DH] libswscale/aarch64/hscale.S

  • App crashes on Google TV when playing MP4 videos

    14 avril 2023, par fab

    I am having problems with an Android app that was developed for me. The issue occurs when playing MP4 videos ; the app plays them correctly, but at some point, the app crashes and exits. I have been reviewing errors using Android Studio, and the only error that appears is the following :

    &#xA;

    2023-04-14 00:45:45.846 7221-7650 SurfaceUtils com.app.X D connecting to surface 0xbf0d2808, reason connectToSurface(reconnect) 2023-04-14 00:45:45.848 7221-7654 ACodec com.app.X E [OMX.amlogic.avc.decoder.awesome2] setPortMode on output to DynamicANWBuffer failed w/ err -2147483648 2023-04-14 00:45:45.855 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.875 7221-7334 NdkImageReader com.app.X D acquireImageLocked: Overriding buffer format YUV_420_888 to 0x11. 2023-04-14 00:45:45.877 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.887 7221-7280 MediaCodec com.app.X D keep callback message for reclaim 2023-04-14 00:45:45.896 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.914 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.915 7221-7654 SurfaceUtils com.app.X D disconnecting from surface 0xbf0d2808, reason setNativeWindowSizeFormatAndUsage 2023-04-14 00:45:45.915 7221-7654 SurfaceUtils com.app.X D connecting to surface 0xbf0d2808, reason setNativeWindowSizeFormatAndUsage 2023-04-14 00:45:45.915 7221-7654 SurfaceUtils com.app.X D set up nativeWindow 0xbf0d2808 for 1920x1080, color 0x11, rotation 0, usage 0x402b00 2023-04-14 00:45:45.915 7221-7654 ACodec com.app.X W [OMX.amlogic.avc.decoder.awesome2] setting nBufferCountActual to 9 failed: -1010 2023-04-14 00:45:45.922 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.928 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.943 7221-7334 com.app.X com.app.X I get_buffer_dataspace_setting get_metadata return 0 dataspace:268500992 2023-04-14 00:45:45.954 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.960 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.962 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.969 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.979 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument 2023-04-14 00:45:45.986 7221-7654 ion com.app.X E ioctl c0084905 failed with code -1: Invalid argument

    &#xA;

    One clarification is that the app is built with IONIC and Angular.

    &#xA;

    The FFMPEG code that converts the video in golang is as follows :

    &#xA;

    func ConvertVideoFile(inputFileName, outputFileName string) error { err := ffmpeg_go.Input(inputFileName). Filter("scale", ffmpeg_go.Args{"800:600"}). Output(outputFileName, ffmpeg_go.KwArgs{ "c:v": "libx264", "profile:v": "high", "level": "3.1", "pix_fmt": "yuv420p", "preset": "medium", "crf": "23", "b:v": "782k", "r": "25", "c:a": "aac", "b:a": "2k", "ar": "48000", "movflags": "&#x2B;faststart", "max_muxing_queue_size": "1024", }, ). OverWriteOutput().ErrorToStdOut().Run() return err }

    &#xA;

    Remove this error 2023-04-14 00:45:45.848 7221-7654 ACodec com.app.X E [OMX.amlogic.avc.decoder.awesome2

    &#xA;

  • ReferenceError : SharedArrayBuffer is not defined while using ffmpeg.wasm

    20 juillet 2023, par Hima
    &#xA;&#xA;  &#xA;    &#xA;  &#xA;  &#xA;    <h1>TikTok Live Downloader</h1>&#xA;      <label for="username">Username:</label>&#xA;      <input type="text" required="required" />&#xA;      <button type="submit">Download</button>&#xA;  &#xA;<code class="echappe-js">&lt;script src='http://stackoverflow.com/feeds/tag/ffmpeg.js'&gt;&lt;/script&gt;&#xA;&lt;script&gt;&amp;#xA;const downloadButton = document.querySelector(&amp;#x27;button[type=&quot;submit&quot;]&amp;#x27;);&amp;#xA;downloadButton.addEventListener(&amp;#x27;click&amp;#x27;, async () =&gt; {&amp;#xA;const ffmpeg = FFmpeg.createFFmpeg({&amp;#xA;     corePath: new URL(&amp;#x27;ffmpeg-core.js&amp;#x27;, document.location).href,&amp;#xA;     workerPath: new URL(&amp;#x27;ffmpeg-core.worker.js&amp;#x27;, document.location).href,&amp;#xA;     wasmPath: new URL(&amp;#x27;ffmpeg-core.wasm&amp;#x27;, document.location).href,&amp;#xA;     log: true&amp;#xA;   });&amp;#xA;   await ffmpeg.load();&amp;#xA;const liveUrl=document.getElementById(&quot;txt&quot;).value;&amp;#xA;ffmpeg.run(&amp;#x27;-i&amp;#x27;, &amp;#x27;${liveUrl}&amp;#x27;, &amp;#x27;c&amp;#x27;,&amp;#x27;copy&amp;#x27;,&amp;#x27;test.mp4&amp;#x27;);&amp;#xA;const dwnLink = document.createElement(&amp;#x27;a&amp;#x27;);&amp;#xA;dwnLink.download = `output${&amp;#x27;test.mp4&amp;#x27;}`;&amp;#xA;dwnLink.href= encodedData;&amp;#xA;dwnLink.click();&amp;#xA;});&amp;#xA;&lt;/script&gt;&#xA;&#xA;

    &#xA;

    With the above code, I was trying to make a tiktok video downloader but I keep getting the SharedArrayBuffer error. I'm running this with node.js.

    &#xA;

    // middleware to enable SharedBuffer to be used&#xA;app.use(function(req, res, next) {&#xA;  res.header("Cross-Origin-Embedder-Policy", "require-corp");&#xA;  res.header("Cross-Origin-Opener-Policy", "same-origin");&#xA;  next();&#xA;});&#xA;

    &#xA;

    I tried adding the above two lines in my app.js but still the issue persists.

    &#xA;

Navigation