Recherche avancée

Sur d’autres sites (4460)

• avcodec : Set AV_CODEC_CAP_CHANNEL_CONF in more decoders

  9 septembre 2020, par Michael Niedermayer

  avcodec : Set AV_CODEC_CAP_CHANNEL_CONF in more decoders
  Suggested-by : Paul B Mahol <onemda@gmail.com>
  
  See : [FFmpeg-devel] [PATCH 1/3] avcodec/fastaudio : Check channels
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavcodec/ac3dec_fixed.c
  • [DH] libavcodec/ac3dec_float.c
  • [DH] libavcodec/adxdec.c
  • [DH] libavcodec/flacdec.c
  • [DH] libavcodec/mpegaudiodec_fixed.c
  • [DH] libavcodec/mpegaudiodec_float.c
  • [DH] libavcodec/pcm-dvd.c
  • [DH] libavcodec/ralf.c
  • [DH] libavcodec/s302m.c
  • [DH] libavcodec/shorten.c
  • [DH] libavcodec/siren.c

• lavf/mpegts : add supplementary audio descriptor

  20 février 2018, par Stefan Pöschel

  lavf/mpegts : add supplementary audio descriptor
  The supplementary audio descriptor is defined in ETSI EN 300 468 and
  
  provides more details regarding accessibility audio tracks, especially
  
  the normative annex J contains a detailed description of its use.
  Its language code (if present) overrides the language code of an also
  
  present ISO 639 language descriptor.
  Note that this also changes the priority of multiple descriptors with
  
  language from "the last descriptor with language within the ES loop" to
  
  "specific descriptor over general ISO 639 descriptor".
  Signed-off-by : Aman Gupta <aman@tmm1.net>
  

  • [DH] libavformat/mpegts.c

• AWS Lambda : "Unzipped size must be smaller than 106534017 bytes" after adding single file

  17 septembre 2023, par leon

  When trying to deploy my lambdas using AWS through the serverless framework I had no problems until I tried adding the ffmpeg binary.

  


  Now the ffmpeg binaries I have tried to add have ranged from 26 mb to 50 mb. Whichever I add, I get the following error :

  


  UPDATE_FAILED: WhatsappDocumentHandlerLambdaFunction (AWS::Lambda::Function)
Resource handler returned message: "Unzipped size must be smaller than 106534017 bytes (Service: Lambda, Status Code: 400, Request ID: ...)" (RequestToken: ..., HandlerErrorCode: InvalidRequest)


  


  The problem is that I did not add the file to this function. I added it to a completely different one.

  


  I have tried the following things :

  


  

  • Creating an "empty" function that only contains the ffmpeg binary and a function handler

  


  • Creating a layer that only contains the ffmpeg binary

  


  • Deleting the ffmpeg binary (the error goes away and deployment succeeds

  


  • Varying sizes of ffmpeg binaries between 26 and 50mb

  


  • Getting the ffmpeg-lambda-layer (https://github.com/serverlesspub/ffmpeg-aws-lambda-layer ; https://serverlessrepo.aws.amazon.com/applications/us-east-1/145266761615/ffmpeg-lambda-layer) and deploying it myself

  


  


  When trying every single one of these options I get the UPDATE_FAILED error in a different function that surely is not too big.

  


  I know I can deploy using a docker image but why complicate things with docker images when it should work ?

  


  I am very thankful for any ideas.