Recherche avancée

Médias (91)

Autres articles (69)

  • Websites made ​​with MediaSPIP

    2 mai 2011, par

    This page lists some websites based on MediaSPIP.

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

  • Les statuts des instances de mutualisation

    13 mars 2010, par

    Pour des raisons de compatibilité générale du plugin de gestion de mutualisations avec les fonctions originales de SPIP, les statuts des instances sont les mêmes que pour tout autre objets (articles...), seuls leurs noms dans l’interface change quelque peu.
    Les différents statuts possibles sont : prepa (demandé) qui correspond à une instance demandée par un utilisateur. Si le site a déjà été créé par le passé, il est passé en mode désactivé. publie (validé) qui correspond à une instance validée par un (...)

Sur d’autres sites (16159)

  • armv6 : Accelerate ff_fft_calc for general case (nbits != 4)

    16 juillet 2014, par Ben Avison
    armv6 : Accelerate ff_fft_calc for general case (nbits != 4)

    The previous implementation targeted DTS Coherent Acoustics, which only
    
requires nbits == 4 (fft16()). This case was (and still is) linked directly
    
rather than being indirected through ff_fft_calc_vfp(), but now the full
    
range from radix-4 up to radix-65536 is available. This benefits other codecs
    
such as AAC and AC3.
    

    The implementaion is based upon the C version, with each routine larger than
    
radix-16 calling a hierarchy of smaller FFT functions, then performing a
    
post-processing pass. This pass benefits a lot from loop unrolling to
    
counter the long pipelines in the VFP. A relaxed calling standard also
    
reduces the overhead of the call hierarchy, and avoiding the excessive
    
inlining performed by GCC probably helps with I-cache utilisation too.
    

    I benchmarked the result by measuring the number of gperftools samples that
    
hit anywhere in the AAC decoder (starting from aac_decode_frame()) or
    
specifically in the FFT routines (fft4() to fft512() and pass()) for the
    
same sample AAC stream :
    

                  Before          After
    
              Mean   StdDev   Mean   StdDev  Confidence  Change
    
Audio decode  2245.5 53.1     1599.6 43.8    100.0%      +40.4%
    
FFT routines  940.6  22.0     348.1  20.8    100.0%      +170.2%
    

    Signed-off-by : Martin Storsjö <martin@martin.st>
    • [DH] libavcodec/arm/fft_init_arm.c
    • [DH] libavcodec/arm/fft_vfp.S

  • Error Installing ffmpeg-binaries 4.0.0 in Heroku Build

    30 juillet 2020, par Confused Cyclonine

    I have been writing a Discord.js bot that uses the ffmpeg-binaries 4.0.0 to play sounds in voice channels. I have been able to run my bot locally through the node.js terminal, but when I tried to deploy it using Heroku, I got this error :

    &#xA;

           Error: Cannot find module &#x27;/tmp/build_8393acf9_/node_modules/lzma-native/binding-v3.0.8-node-v64-linux-x64/lzma_native.node&#x27;&#xA;           at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)&#xA;           at Function.Module._load (internal/modules/cjs/loader.js:506:25)&#xA;           at Module.require (internal/modules/cjs/loader.js:636:17)&#xA;           at require (internal/modules/cjs/helpers.js:20:18)&#xA;           at /tmp/build_8393acf9_/node_modules/lzma-native/index.js:13:14&#xA;           at Object.<anonymous> (/tmp/build_8393acf9_/node_modules/lzma-native/index.js:597:3)&#xA;           at Module._compile (internal/modules/cjs/loader.js:688:30)&#xA;           at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)&#xA;           at Module.load (internal/modules/cjs/loader.js:598:32)&#xA;           at tryModuleLoad (internal/modules/cjs/loader.js:537:12)&#xA;       npm ERR! code ELIFECYCLE&#xA;       npm ERR! errno 1&#xA;       npm ERR! ffmpeg-binaries@4.0.0 install: `node install`&#xA;       npm ERR! Exit status 1&#xA;       npm ERR! &#xA;       npm ERR! Failed at the ffmpeg-binaries@4.0.0 install script.&#xA;       npm ERR! This is probably not a problem with npm. There is likely additional logging output above.&#xA;</anonymous>

    &#xA;

    I have tried to install and reinstall the ffmpeg-binaries but it doesn't seem to help.

    &#xA;

    Can someone please tell me how to fix this ? Thank you !

    &#xA;

  • Merge commit ’33237123c83bf4f8345e6ac889ad2e7dbd303d0e’

    10 août 2013, par Michael Niedermayer
    Merge commit ’33237123c83bf4f8345e6ac889ad2e7dbd303d0e’

    * commit ’33237123c83bf4f8345e6ac889ad2e7dbd303d0e’ :
    
  libavutil : Enable the MSVC DLL symbol loading workaround in shared builds as well
    

    Merged-by : Michael Niedermayer <michaelni@gmx.at>
    • [DH] libavutil/internal.h

Navigation