Recherche avancée

Sur d’autres sites (11226)

• swscale/aarch64 : use multiply accumulate and shift-right narrow

  9 décembre 2019, par Sebastian Pop

  swscale/aarch64 : use multiply accumulate and shift-right narrow
  This patch rewrites the innermost loop of ff_yuv2planeX_8_neon to avoid zips and
  
  horizontal adds by using fused multiply adds. The patch also uses ld1r to load
  
  one element and replicate it across all lanes of the vector. The patch also
  
  improves the clipping code by removing the shift right instructions and
  
  performing the shift with the shift-right narrow instructions.
  I see 8% difference on an m6g instance with neoverse-n1 CPUs :
  
  $ ffmpeg -nostats -f lavfi -i testsrc2=4k:d=2 -vf bench=start,scale=1024x1024,bench=stop -f null -
  
  before : t:0.014015 avg:0.014096 max:0.015018 min:0.013971
  
  after :  t:0.012985 avg:0.013013 max:0.013996 min:0.012818
  Tested with `make check` on aarch64-linux.
  Signed-off-by : Sebastian Pop <spop@amazon.com>
  
  Reviewed-by : Clément Bœsch <u@pkh.me>
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libswscale/aarch64/output.S

• avformat/hls : Be more picky on extensions

  16 janvier, par Michael Niedermayer

  avformat/hls : Be more picky on extensions
  This blocks disallowed extensions from probing
  
  It also requires all available segments to have matching extensions to the format
  
  mpegts is treated independent of the extension
  It is recommended to set the whitelists correctly
  
  instead of depending on extensions, but this should help a bit,
  
  and this is easier to backport
  Fixes : CVE-2023-6602 II. HLS Force TTY Demuxer
  
  Fixes : CVE-2023-6602 IV. HLS XBIN Demuxer DoS Amplification
  The other parts of CVE-2023-6602 have been fixed by prior commits
  Found-by : Harvey Phillips of Amazon Element55 (element55)
  
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] doc/demuxers.texi
  • [DH] libavformat/hls.c

• Error : ffmpeg exited with code 1 on AWS Lambda

  16 juin 2022, par Hassnain Alvi

  I am using fluent-ffmpeg nodejs package to run ffmpeg for audio conversion on AWS Lambda. I am using this FFmpeg layer for lambda.
Here is my code

  


    const bitrate64 = ffmpeg("file.mp3").audioBitrate('64k');
    bitrate64.outputOptions([
        '-preset slow',
    '-g 48',
    "-map", "0:0",
        '-hls_time 6',
        '-master_pl_name master.m3u8',
        '-hls_segment_filename 64k/fileSequence%d.ts'
    ])
    .output('./64k/prog_index.m3u8')
    .on('progress', function(progress) {
        console.log('Processing 64k bitrate: ' + progress.percent + '% done')
    })  
    .on('end', function(err, stdout, stderr) {
        console.log('Finished processing 64k bitrate!')
    })
    .run() 


  


  after running it via AWS lambda I get following error message

  


  ERROR   Uncaught Exception  &#xA;{&#xA;    "errorType": "Error",&#xA;    "errorMessage": "ffmpeg exited with code 1: Conversion failed!\n",&#xA;    "stack": [&#xA;        "Error: ffmpeg exited with code 1: Conversion failed!",&#xA;        "",&#xA;        "    at ChildProcess.<anonymous> (/var/task/node_modules/fluent-ffmpeg/lib/processor.js:182:22)",&#xA;        "    at ChildProcess.emit (events.js:198:13)",&#xA;        "    at ChildProcess.EventEmitter.emit (domain.js:448:20)",&#xA;        "    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)"&#xA;    ]&#xA;}&#xA;</anonymous>

  


  I don't get any more info so I am not sure what's going on. Can anyone tell me what's wrong here and how can I enable more detailed logs ?