Recherche avancée

Médias (1)

Mot : - Tags -/artwork

Autres articles (71)

  • Des sites réalisés avec MediaSPIP

    2 mai 2011, par

    Cette page présente quelques-uns des sites fonctionnant sous MediaSPIP.
    Vous pouvez bien entendu ajouter le votre grâce au formulaire en bas de page.

  • Librairies et binaires spécifiques au traitement vidéo et sonore

    31 janvier 2010, par

    Les logiciels et librairies suivantes sont utilisées par SPIPmotion d’une manière ou d’une autre.
    Binaires obligatoires FFMpeg : encodeur principal, permet de transcoder presque tous les types de fichiers vidéo et sonores dans les formats lisibles sur Internet. CF ce tutoriel pour son installation ; Oggz-tools : outils d’inspection de fichiers ogg ; Mediainfo : récupération d’informations depuis la plupart des formats vidéos et sonores ;
    Binaires complémentaires et facultatifs flvtool2 : (...)

  • Possibilité de déploiement en ferme

    12 avril 2011, par

    MediaSPIP peut être installé comme une ferme, avec un seul "noyau" hébergé sur un serveur dédié et utilisé par une multitude de sites différents.
    Cela permet, par exemple : de pouvoir partager les frais de mise en œuvre entre plusieurs projets / individus ; de pouvoir déployer rapidement une multitude de sites uniques ; d’éviter d’avoir à mettre l’ensemble des créations dans un fourre-tout numérique comme c’est le cas pour les grandes plate-formes tout public disséminées sur le (...)

Sur d’autres sites (5991)

  • NVIDIA Version Outdated Error when mine is updated

    21 février 2021, par Agent Merlot

    I'm trying to encode stuff with my NVIDIA GeForce MX150 (Driver Version : 461.09).

    


    import os
os.system(f'ffmpeg -i "Cells at Work Season 2 - Episode 07 - English Subbed.mp4" -c:a copy -c:v hevc_nvenc "07.mp4"')

    


    Whenever I'm trying to run it, I'm getting this error.

    


    [hevc_nvenc @ 0000017a8bdf7e40] Cannot load nvEncodeAPI64.dll
[hevc_nvenc @ 0000017a8bdf7e40] The minimum required Nvidia driver for nvenc is 436.15 or newer
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
Conversion failed!

    


    What bugs me is that it says that I need 436.15 or newer, and mine is 461.09. That means it should work, right ? Can anyone help ?

    


  • 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 :

    


    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
dyld: Library not loaded: /usr/local/opt/libass/lib/libass.9.dylib
  Referenced from: /Users/martinbarker/Documents/projects/digify-new/dist/mas/Digify.app/Contents/Resources/ffmpeg
  Reason: no suitable image found.  Did find:
    file system sandbox blocked open() of '/usr/local/opt/libass/lib/libass.9.dylib'
    /usr/local/opt/libass/lib/libass.9.dylib: stat() failed with errno=1
    file system sandbox blocked open() of '/usr/local/lib/libass.9.dylib'
    file system sandbox blocked open() of '/usr/local/Cellar/libass/0.15.0/lib/libass.9.dylib'
    at makeError (/Users/martinbarker/…eca/lib/error.js:59)
    at handlePromise (/Users/martinbarker/…/execa/index.js:114)
    at async file:/Users/ma…js/newindex.js:1151


    


    I think this line is important ; file system sandbox blocked open() of '/usr/local/opt/libass/lib/libass.9.dylib' 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.

    


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

    


    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.

    


    git clone https://git.ffmpeg.org/ffmpeg.git ffmpeg-mac && cd ffmpeg-mac && ./configure pkg_config='pkg-config --static' --pkg-config-flags='--static' --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 && make && cd ..


    


    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/ && npm run build-mas && sh mas-sign-script.sh, the production build (once approved) fails with the above included error.

    


  • OpenCV : Cannot open camera with CAP_FFMPEG even though ffmpeg is installed

    24 février 2021, par cildiracagim

    Initializing a camera video capture using CAP_FFMPEG fails even though I have ffmpeg installed :

    


    cv::VideoCapture vcap;
vcap.open(0, cv::CAP_FFMPEG);

// After these, vcap.isOpened() returns false.


    


    However, it works perfectly when I open a file in the same way :

    


    cv::VideoCapture vcap;
vcap.open(argv[1], cv::CAP_FFMPEG);

/* Correctly opens the video file at path argv[1],
vcap.isOpened() returns true. */


    


    The problem occurs in both OpenCV versions installed in my system : 4.5.1 and 3.2.0. Version 3.2.0 came installed in my Linux distribution but I have compiled 4.5.1 myself. During compilation, I have verified that CMake succesfully recognized the ffmpeg installation in my system. I guess the problem is not related to OpenCV not recognizing ffmpeg since I can open and work on video files without any problems on both OpenCV versions.

    


    Any help is greatly appreciated.