Recherche avancée

Sur d’autres sites (4363)

• Anomalie #1934 : Liberons les dl, dd, dt !

  20 septembre 2011, par tetue -

  Les raccourcis à la mode SPIP — avec un tiret : « - ? » et « - ! » — sont assez limitatifs : ils présupposent qu’on n’a jamais qu’un ligne en face... Or j’ai souvent plusieurs paragraphes à caser dans le (dans les aussi) ! La syntaxe Markdown est éprouvée et semble offrir plus de possibilités. (...)

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

  


• Getting "moov atom not found" error on linux but not windows/mac ?

  22 juin 2020, par flynnstone9

  Hey I have a tool I built that makes a video for me and it works locally on a mac / windows machine. I setup a digital ocean ubuntu server to host my app and the final video is giving a "moov atom not found" when running ffprobe output.mp4.

  


  The way the video is being created is thru this cmd :

  


  


  ffmpeg -i 1.mp4 -i 3.mp4 -filter_complex "[0:v][0:a][1:v][1:a]concat=n=2:v=1:a=1" output.mp4

  


  


  I'm using slightly different versions of ffmpeg on linux v Mac. I was running 4.3-2ubuntu0 18.04.sav0 on linux and ffmpeg version 4.2.2 on Mac.

  


  Is this a linux specific issue or is it something with the video container I'm missing ?