Recherche avancée

Sur d’autres sites (8832)

• aacenc_is : take absolute coefficient value upon energy calculations

  6 septembre 2015, par Rostislav Pehlivanov

  aacenc_is : take absolute coefficient value upon energy calculations
  This was an oversight when the IS system was being first implemented.
  
  The ener01 part was largely a result of trial and error and the fact
  
  that the sum of coef0 and coef1 could result in a zero was
  
  overlooked. Once ener01 turns to zero it’s used to divide the left
  
  channel energy which doesn’t turn out so well as it fills IS[]
  
  with -nan’s and inf’s which in turn confused the quantize_band_cost.
  Signed-off-by : Rostislav Pehlivanov <atomnuker@gmail.com>
  

  • [DH] libavcodec/aacenc_is.c
  • [DH] tests/fate/aac.mak

• NodeJS HLS stall initial m3u8 for playback

  7 mars 2016, par shreddish

  I have a nodejs server running, when user enters the follow address

  http://localhost:7070/udp/239.1.1.1:1234/out.m3u8

  My server starts an ffmpeg child process that connects to that UDP stream and converts it to HLS segmented files.

  In order to give FFMPEG a chance to begin and start creating the first out.m3u8 file I call the FFMPEG process and then immediately set a timeout of about 8 seconds before the server responds to the request for the .m3u8 file.

  Eventually the video will start to play but only get through 2-3 .ts files before playback stops and the browser stops requesting additional .ts files.

  When it’s stalled, if I hit refresh (since FFMPEG is still running) it doesn’t try to start ffmpeg and delay the response. Instead it just immediately serves up the files being requested and playback works fine.

  So I am thinking that clearly something to do with delaying my response for that long is mucking up the playback of the stream. Is there a better way to wait for FFMPEG to start generating the HLS files and respond ?

  Here is the part of the server that is delaying the response.

  // Check if ffmpeg is running yet, also check to see if user has switched to a different udp address
  
          if (filename == "out.m3u8" && (!ffmpegRunning || udpAddress != runningUDPAddress)) 
  
              {
  
                  runFFMPEG(filename, udpAddress);
  
                  setTimeout(function() { streamFile(req, res, uri, filename); return; }, 8000);
  
              }
  
              else
  
              {
  
                  streamFile(req, res, uri, filename);
  
              }

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