Recherche avancée

Sur d’autres sites (3972)

• Docker : an error happened : ffmpeg exited with code 127

  18 mai 2021, par developerpolice

  As I mentioned above, when I run the container, I get an error. When I run it normally, it works, there is no problem.

  


  my container run code : docker run —rm -i -t -p 8080:4444 9fa71c8ca9ba

  


  the error i got ;
an error happened : ffmpeg exited with code 127

  


  APP.JS

  


  https://pastebin.ubuntu.com/p/znCRWz2rgx/

  


  Dockerfile :

  


  FROM node:10

COPY . /app
WORKDIR /app

RUN npm install
RUN npm install fluent-ffmpeg
RUN npm install os
RUN npm install express
RUN npm install --save @google-cloud/text-to-speech
RUN npm install --save @google-cloud/translate
RUN export GOOGLE_APPLICATION_CREDENTIALS="dogwood-cipher-307314-4074350f02b8.json"


CMD ["node", "app.js"]


  


• Use FFmpeg with Swift [on hold]

  3 juin 2016, par grotesk

  I’m trying to use FFmpeg in my iOS app that is written in swift. I used this script FFmpeg iOS Build Script to build the library for iOS.
  My problem now is that I get FFmpeg working but still have some flaws i don’t understand. Maybe someone of you got already the same problems and could help me.

  If I want to use AV_NOPTS_VALUE or AV_TIME_BASE_Q i’m getting a "Use of unresolved identifier" although it is defined in avutil.h.
  I tried to define it myself, but this doesn’t solve all problems.

  I’m trying to translate this streamer Streamer Example Code to swift, i have access to all functions but not to AV_NOPTS_VALUE, i had to define it myself as let AV_NOPTS_VALUE: UInt64 = 0x8000000000000000.

• AAC : Fix M/S stereo encoding

  3 mars 2015, par Claudio Freire

  AAC : Fix M/S stereo encoding
  This patch fixes a pointer arithmetic bug in adjust_frame_information that resulted in heavily corrupted audio when using M/S encoding. Also, a backup copy of untransformed coefficients has to be kept around or attempts at re-processing the frame (which happens when hevavily overspending bits during transients) will result in re-encoding of the coefficients and subsequent corruption of the resulting stream.
  A/B testing shows the bug as corrected, but still cannot prove that M/S coding is a win at least in numbers. Limited listening tests do show improvement on M/S encoded samples in lower bitrates, but they’re hidden among the other artifacts that remain to be corrected in the encoder.
  Some of the regressions flagged in the report do show poor stereo image (but not buggy), so M/S encoding is clearly not good enough yet to be defaulted to auto.
  In numbers, Patched against Unpatched, stereo_mode auto :
    Files : 114
  
    Bitrates : 6
  
    Tests : 683
    Serious Regressions : 0 (0%)
  
    Regressions : 0 (0%)
  
    Improvements : 227 (33%)
  
    Big improvements : 92 (13%)
  
    Worst regression - mybloodrusts.wv - 256k
  
      - StdDev : 28.61       pSNR : -0.43     maxdiff : 1372.00
  
    Best improvement - 60.wv - 384k
  
      - StdDev : -369.57     pSNR : 45.02     maxdiff : -13322.00
  
    Average          - StdDev : -80.56       pSNR : 2.49      maxdiff : -8858.00
  Patched against Unpatched stereo_mode ms_off shows no difference.
  Patched stereo_mode auto vs Unpatched stereo_mode ms_off shows a small average improvement, just not too significant :
    Serious Regressions : 0 (0%)
  
    Regressions : 10 (1%)
  
    Improvements : 45 (6%)
  
    Big improvements : 2 (0%)
  
    Worst regression - Illinois.wv - 256k
  
      - StdDev : 33.20       pSNR : -2.03     maxdiff : 477.00
  
    Best improvement - song_of_circomstances.flac - 384k
  
      - StdDev : -3.97       pSNR : 7.61      maxdiff : -826.00
  
    Average          - StdDev : -10.25       pSNR : 0.20      maxdiff : -281.00
  Signed-off-by : Michael Niedermayer <michaelni@gmx.at>
  

  • [DH] libavcodec/aac.h
  • [DH] libavcodec/aaccoder.c
  • [DH] libavcodec/aacenc.c