Recherche avancée

Médias (0)

Mot : - Tags -/content

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

Autres articles (64)

  • MediaSPIP version 0.1 Beta

    16 avril 2011, par

    MediaSPIP 0.1 beta est la première version de MediaSPIP décrétée comme "utilisable".
    Le fichier zip ici présent contient uniquement les sources de MediaSPIP en version standalone.
    Pour avoir une installation fonctionnelle, il est nécessaire d’installer manuellement l’ensemble des dépendances logicielles sur le serveur.
    Si vous souhaitez utiliser cette archive pour une installation en mode ferme, il vous faudra également procéder à d’autres modifications (...)

  • Mise à jour de la version 0.1 vers 0.2

    24 juin 2013, par

    Explications des différents changements notables lors du passage de la version 0.1 de MediaSPIP à la version 0.3. Quelles sont les nouveautés
    Au niveau des dépendances logicielles Utilisation des dernières versions de FFMpeg (>= v1.2.1) ; Installation des dépendances pour Smush ; Installation de MediaInfo et FFprobe pour la récupération des métadonnées ; On n’utilise plus ffmpeg2theora ; On n’installe plus flvtool2 au profit de flvtool++ ; On n’installe plus ffmpeg-php qui n’est plus maintenu au (...)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

Sur d’autres sites (10861)

  • Compile ffmpeg for WinRT with libvpx ?

    7 janvier 2018, par Sean O'Neil

    Following this guide :
    https://trac.ffmpeg.org/wiki/CompilationGuide/WinRT

    Can anyone tell me if it’s possible to build and include libvpx into this ?

  • vdpau : use the correct namespace for the union

    10 juillet 2013, par Luca Barbato
    vdpau : use the correct namespace for the union
    

    Vdp is used by libvdpau, use AVVDPAU as used for the rest.

    Reported-by : Alexis Ballier <aballier@gentoo.org>

    • [DBH] libavcodec/vdpau.h
  • ffmpeg crashes in electron on mac apple store ; no suitable image found file system sandbox blocked open() of 'libass'

    20 février 2021, par Martin

    I am trying to release an electron app on the Mac Apple Store (mas), my electron app uses ffmpeg to render videos. In order to release my app on the mac apple store, It needs to be sandboxed, and by default ffmpeg makes calls to external libraries so I need to statically build ffmpeg and package it with my app. I have successfully built my app, submitted it to the app store, had it approved, and downloaded/used it but my ffmpeg fails with this errir :

    &#xA;

    Uncaught (in promise) Error: Command was killed with SIGABRT (Aborted): /Users/martinbarker/Documents/projects/digify-new/dist/mas/Digify.app/Contents/Resources/ffmpeg -i /Users/martinbarker/Downloads/Steve Leach With The Crystal Grass Orchestra – Ocean Potion/9. Get Out In The Sun.flac -i /Users/martinbarker/Downloads/Steve Leach With The Crystal Grass Orchestra – Ocean Potion/10. Golden Hues.flac -y -filter_complex concat=n=2:v=0:a=1 -c:a libmp3lame -b:a 320k /Users/martinbarker/Downloads/Steve Leach With The Crystal Grass Orchestra – Ocean Potion/output-261020.mp3&#xA;dyld: Library not loaded: /usr/local/opt/libass/lib/libass.9.dylib&#xA;  Referenced from: /Users/martinbarker/Documents/projects/digify-new/dist/mas/Digify.app/Contents/Resources/ffmpeg&#xA;  Reason: no suitable image found.  Did find:&#xA;    file system sandbox blocked open() of &#x27;/usr/local/opt/libass/lib/libass.9.dylib&#x27;&#xA;    /usr/local/opt/libass/lib/libass.9.dylib: stat() failed with errno=1&#xA;    file system sandbox blocked open() of &#x27;/usr/local/lib/libass.9.dylib&#x27;&#xA;    file system sandbox blocked open() of &#x27;/usr/local/Cellar/libass/0.15.0/lib/libass.9.dylib&#x27;&#xA;    at makeError (/Users/martinbarker/…eca/lib/error.js:59)&#xA;    at handlePromise (/Users/martinbarker/…/execa/index.js:114)&#xA;    at async file:/Users/ma…js/newindex.js:1151&#xA;

    &#xA;

    I think this line is important ; file system sandbox blocked open() of &#x27;/usr/local/opt/libass/lib/libass.9.dylib&#x27; but I'm not sure what I should change with my static ffmpeg build so that it works in production and so that I can avoid the above error.

    &#xA;

    My code is available on the branch mas-attempt-after-redesign here : https://github.com/MartinBarker/digify/tree/mas-attempt-after-redesign

    &#xA;

    Inside my package.json I have the command download-ffmpeg which clones the ffmpeg repo, runs a configure command with some flags, and then builds ffmpeg into a folder called 'ffmpeg-mac', this folder gets packaged with the app for the mac apple store build.

    &#xA;

    git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg-mac &amp;&amp; cd ffmpeg-mac &amp;&amp; ./configure pkg_config=&#x27;pkg-config --static&#x27; --pkg-config-flags=&#x27;--static&#x27; --libdir=/usr/local/lib --extra-version=ntd_20150128 --disable-shared --disable-lzma --enable-gpl --enable-pthreads --enable-nonfree --enable-libass --enable-libfdk-aac  --enable-libmp3lame  --enable-libx264 --enable-static --enable-filters --enable-runtime-cpudetect &amp;&amp; make &amp;&amp; cd ..&#xA;

    &#xA;

    You can see in the above ffmpeg command the flag --enable-libass, but even though I have that flag included, after I build and sign my mac apple store build by running sudo rm -rf dist/mas/ &amp;&amp; npm run build-mas &amp;&amp; sh mas-sign-script.sh, the production build (once approved) fails with the above included error.

    &#xA;