Recherche avancée

Médias (0)

Mot : - Tags -/images

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

Autres articles (64)

  • Les images

    15 mai 2013

  • Publier sur MédiaSpip

    13 juin 2013

    Puis-je poster des contenus à partir d’une tablette Ipad ?
    Oui, si votre Médiaspip installé est à la version 0.2 ou supérieure. Contacter au besoin l’administrateur de votre MédiaSpip pour le savoir

  • Récupération d’informations sur le site maître à l’installation d’une instance

    26 novembre 2010, par

    Utilité
    Sur le site principal, une instance de mutualisation est définie par plusieurs choses : Les données dans la table spip_mutus ; Son logo ; Son auteur principal (id_admin dans la table spip_mutus correspondant à un id_auteur de la table spip_auteurs)qui sera le seul à pouvoir créer définitivement l’instance de mutualisation ;
    Il peut donc être tout à fait judicieux de vouloir récupérer certaines de ces informations afin de compléter l’installation d’une instance pour, par exemple : récupérer le (...)

Sur d’autres sites (9233)

  • Can no longer get ffmpeg to run in Terminal on macOS

    31 décembre 2023, par Chewie The Chorkie

    Here's a command I tried to run which always worked :

    


    Mac-mini:images Admin$ ffmpeg -r 30  -f image2 -s 1080x1080 -i %d.png -vcodec h264 -crf 25  -pix_fmt yuv420p zVideo.mp4


    


    The output I get is :

    


    dyld[94095]: Library not loaded: /usr/local/opt/theora/lib/libtheoraenc.1.dylib
  Referenced from: <20EBE016-0DD0-3F29-96CD-D22BC2E40B38> /usr/local/Cellar/ffmpeg/6.1.1/bin/ffmpeg
  Reason: tried: '/usr/local/opt/theora/lib/libtheoraenc.1.dylib' (no such file), '/System/Volumes/Preboot/Cryptexes/OS/usr/local/opt/theora/lib/libtheoraenc.1.dylib' (no such file), '/usr/local/opt/theora/lib/libtheoraenc.1.dylib' (no such file)
Abort trap: 6


    


    I've tried reinstalling ffmpeg, installing the command line tools from Xcode, and Xcode itself.

    


  • I can't understand how to use ffmpeg in javascript (if it's even possible)

    28 juin, par Laimonas Rupeika

    Straight to the problem, I want to use ffmpeg in my javascript project for video editing. So I found cdn : <code class="echappe-js">&lt;script src=&quot;https://cdn.jsdelivr.net/npm/@salomvary/ffmpeg.js-umd@3.1.9001/ffmpeg-mp4.min.js&quot;&gt;&lt;/script&gt; which references to "https://github.com/Kagami/ffmpeg.js", which is ffmpeg port to javascript as I understand ?&#xA;I don't get any errors on import, but if I try loading ffmpeg :

    &#xA;

    // Initialize FFmpeg after the GAPI client is loaded&#xA;  const ffmpeg = createFFmpeg({ log: true });&#xA;&#xA;  // // Load the FFmpeg library&#xA;  await ffmpeg.load();&#xA;

    &#xA;

    I get error : Uncaught (in promise) ReferenceError: createFFmpeg is not defined at initializeGapiClient (index:89:18) and it also messes my whole project. So if possible, how can I use ffmpeg in pure javascript, not Node.js. Should I download ffmpeg library files and then include them in project, I'm totally lost at this.

    &#xA;

  • aacdec : move from scalefactor ranged arrays to flat arrays

    14 mai 2024, par Lynne
    aacdec : move from scalefactor ranged arrays to flat arrays

    AAC uses an unconventional system to send scalefactors
    
(the volume+quantization value for each band).
    
Each window is split into either 1 or 8 blocks (long vs short),
    
and transformed separately from one another, with the coefficients
    
for each being also completely independent. The scalefactors
    
slightly increase from 64 (long) to 128 (short) to accomodate
    
better per-block-per-band volume for each window.
    

    To reduce overhead, the codec signals scalefactor sizes in an obtuse way,
    
where each group's scalefactor types are sent via a variable length decoding,
    
with a range.
    
But our decoder was written in a way where those ranges were carried through
    
the entire decoder, and to actually read them you had to use the range.
    

    Instead of having a dedicated array with a range for each scalefactor,
    
just let the decoder directly index each scalefactor.
    

    This also switches the form of quantized scalefactors to the format
    
the spec uses, where for intensity stereo and regular, scalefactors
    
are stored in a scalefactor - 100 form, rather than as-is.
    

    USAC gets rid of the complex scalefactor handling. This commit permits
    
for code sharing between both.
    • [DH] libavcodec/aac/aacdec.c
    • [DH] libavcodec/aac/aacdec.h
    • [DH] libavcodec/aac/aacdec_dsp_template.c

Navigation