Recherche avancée

Sur d’autres sites (8241)

• avfilter/vf_vmafmotion : Check dimensions

  29 mai 2021, par Michael Niedermayer

  avfilter/vf_vmafmotion : Check dimensions
  Fixes : out of array access
  
  Fixes : Ticket8241
  
  Fixes : Ticket8246
  
  Fixes : CVE-2020-22019
  
  Fixes : CVE-2020-22033
  Signed-off-by : Michael Niedermayer <michael@niedermayer.cc>
  

  • [DH] libavfilter/vf_vmafmotion.c

• FFMPEG "Segmentation fault" with stream source and watermark

  4 mars 2020, par Magikey

  I use release : 4.2.2 (static) from "https://johnvansickle.com/ffmpeg/"

  Final code will be on "Amazon AWS lambda"

  Goal : use a url stream and add watermak

  Link to video : ​https://feoval.fr/519.mp4

  Link to Watermak : ​https://feoval.fr/watermark.png

  ./ffmpeg -i "https://feoval.fr/519.mp4" -i "./watermark.png" -filter_complex "overlay=W-w-10:H-h-10:format=rgb" -f "mp4" -movflags "frag_keyframe+empty_moov" -pix_fmt "yuv420p" test.mp4

  return "Segmentation fault"

  I have the same error on my computer and on AWS Lambda server

  ./ffmpeg -i "https://feoval.fr/519.mp4" -f "mp4" -movflags "frag_keyframe+empty_moov" -pix_fmt "yuv420p" test.mp4

  work (but not watermak)

  ./ffmpeg -i "./519.mp4" -i "./watermark.png" -filter_complex "overlay=W-w-10:H-h-10:format=rgb" -f "mp4" -movflags "frag_keyframe+empty_moov" -pix_fmt "yuv420p" test.mp4

  work (but not with stream)

  Thanks you very much !

  Logs for the first case who return "Segmentation fault" :

  ...
  
  Stream mapping:
  
  Stream #0:0 (h264) -> overlay:main (graph 0)
  
  Stream #1:0 (png) -> overlay:overlay (graph 0)
  
  overlay (graph 0) -> Stream #0:0 (libx264)
  
  Stream #0:1 -> #0:1 (aac (native) -> aac (native))
  
  Press [q] to stop, ? for help
  
  [libx264 @ 0x742e480] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX
  
  [libx264 @ 0x742e480] profile High, level 3.1, 4:2:0, 8-bit
  
  [libx264 @ 0x742e480] 264 - core 159 r2991 1771b55 - H.264/MPEG-4 AVC codec - Copyleft 2003-2019 - ​http://www.videolan.org/x264.html - options: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
  
  Output #0, mp4, to 'test.mp4':
  
  Metadata:
  
  major_brand : mp42
  
  minor_version : 1
  
  compatible_brands: isommp41mp42
  
  encoder : Lavf58.29.100
  
  Stream #0:0: Video: h264 (libx264) (avc1 / 0x31637661), yuv420p, 480x848, q=-1--1, 30 fps, 15360 tbn, 30 tbc (default)
  
  Metadata:
  
  encoder : Lavc58.54.100 libx264
  
  Side data:
  
  cpb: bitrate max/min/avg: 0/0/0 buffer size: 0 vbv_delay: -1
  
  Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 44100 Hz, stereo, fltp, 128 kb/s (default)
  
  Metadata:
  
  creation_time : 2020-01-13T08:54:26.000000Z
  
  handler_name : Core Media Audio
  
  encoder : Lavc58.54.100 aac
  
  Segmentation fault (core dumped)

• FFMPEG not found error while attempting to implement ffmpeg into discord bot

  17 février 2020, par Ravenr_

  While implementing a music feature into my node.js discord.js discord bot, I got an error claiming that it cant find FFMPEG. I reinstalled ffmpeg 3 times to no avail.

  This is the full error

  2020-02-17T01:48:30.403766+00:00 app[worker.1]: (node:4) UnhandledPromiseRejectionWarning: Error: FFMPEG not found
  
  2020-02-17T01:48:30.403797+00:00 app[worker.1]:     at Function.selectFfmpegCommand (/app/node_modules/prism-media/src/transcoders/ffmpeg/Ffmpeg.js:46:13)
  
  2020-02-17T01:48:30.403798+00:00 app[worker.1]:     at new FfmpegTranscoder (/app/node_modules/prism-media/src/transcoders/ffmpeg/Ffmpeg.js:7:37)
  
  2020-02-17T01:48:30.403798+00:00 app[worker.1]:     at new MediaTranscoder (/app/node_modules/prism-media/src/transcoders/MediaTranscoder.js:10:19)
  
  2020-02-17T01:48:30.403799+00:00 app[worker.1]:     at new Prism (/app/node_modules/prism-media/src/Prism.js:5:23)
  
  2020-02-17T01:48:30.403799+00:00 app[worker.1]:     at new VoiceConnection (/app/node_modules/discord.js/src/client/voice/VoiceConnection.js:46:18)
  
  2020-02-17T01:48:30.403800+00:00 app[worker.1]:     at /app/node_modules/discord.js/src/client/voice/ClientVoiceManager.js:63:22
  
  2020-02-17T01:48:30.403800+00:00 app[worker.1]:     at new Promise (<anonymous>)
  
  2020-02-17T01:48:30.403801+00:00 app[worker.1]:     at ClientVoiceManager.joinChannel (/app/node_modules/discord.js/src/client/voice/ClientVoiceManager.js:45:12)
  
  2020-02-17T01:48:30.403801+00:00 app[worker.1]:     at VoiceChannel.join (/app/node_modules/discord.js/src/structures/VoiceChannel.js:130:30)
  
  2020-02-17T01:48:30.403802+00:00 app[worker.1]:     at Object.execute (/app/commands/play.js:31:64)
  
  2020-02-17T01:48:30.404044+00:00 app[worker.1]: (node:4) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
  
  2020-02-17T01:48:30.404052+00:00 app[worker.1]: (node:4) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
  
  </anonymous>

  This is the code

  const ytdl = require("ytdl-core");
  
  module.exports = {
  
      name: 'play',
  
      description: 'initiates music methods of the bot',
  
      execute(msg, args){
  
          var servers = {};
  
  
  
          function play(connection, msg){
  
              var server = servers[msg.guild.id];
  
  
  
              server.dispatcher = connection.playStream(ytdl(server.queue[0], {filter: "audioonly"}));
  
              server.queue.shift();
  
  
  
              server.dispatcher.on("end", function(){
  
                  if(server.queue[0]){
  
                      play(connection, msg);
  
                  }else{
  
                      connection.disconnect();
  
                  }
  
              });
  
  
  
  
  
          }
  
          if(!args[1]) return msg.channel.send("you need to provide a link");
  
          if(!msg.member.voiceChannel) return msg.channel.send("You must be in a voice channel to use this feature");
  
          if(!servers[msg.guild.id]) servers[msg.guild.id] = {
  
              queue: []
  
          }
  
          var server = servers[msg.guild.id];
  
          server.queue.push(args[1]);
  
          if(!msg.guild.voiceConnection) msg.member.voiceChannel.join().then(function(connection){
  
              play(connection, msg);
  
          })
  
      }
  
  }

  I have no idea what the issue is. I am using heroku to deploy if that matters at all.