Recherche avancée

Sur d’autres sites (9409)

• ffmpeg stream videos from two cams have a same device name

  21 novembre 2020, par junsang

  There are two cameras have a same device name Microsoft® LifeCam Studio(TM).
  
ffmpeg -list_deivces true -f dshow -i dummy prints the below output.

  



  C:\Users\user>ffmpeg -list_devices true -f dshow -i dummy
ffmpeg version git-2020-02-05-e6891d1 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.2.1 (GCC) 20200122
  configuration: --enable-gpl --enable-version3 --enable-sdl2 --enable-fontconfig --enable-gnutls --enable-iconv --enable-libass --enable-libdav1d --enable-libbluray --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libopus --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libtheora --enable-libtwolame --enable-libvpx --enable-libwavpack --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libzimg --enable-lzma --enable-zlib --enable-gmp --enable-libvidstab --enable-libvorbis --enable-libvo-amrwbenc --enable-libmysofa --enable-libspeex --enable-libxvid --enable-libaom --enable-libmfx --enable-ffnvcodec --enable-cuvid --enable-d3d11va --enable-nvenc --enable-nvdec --enable-dxva2 --enable-avisynth --enable-libopenmpt --enable-amf
  libavutil      56. 39.100 / 56. 39.100
  libavcodec     58. 67.101 / 58. 67.101
  libavformat    58. 37.100 / 58. 37.100
  libavdevice    58.  9.103 / 58.  9.103
  libavfilter     7. 74.100 /  7. 74.100
  libswscale      5.  6.100 /  5.  6.100
  libswresample   3.  6.100 /  3.  6.100
  libpostproc    55.  6.100 / 55.  6.100
[dshow @ 000001d5c5108dc0] DirectShow video devices (some may be both video and audio devices)
[dshow @ 000001d5c5108dc0]  "Microsoft┬« LifeCam Studio(TM)"
[dshow @ 000001d5c5108dc0]     Alternative name "@device_pnp_\\?\usb#vid_045e&pid_0811&mi_00#8&6ae46e6&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global"
[dshow @ 000001d5c5108dc0]  "Microsoft┬« LifeCam Studio(TM)"
[dshow @ 000001d5c5108dc0]     Alternative name "@device_pnp_\\?\usb#vid_045e&pid_0811&mi_00#8&e544916&0&0000#{65e8773d-8f56-11d0-a3b9-00a0c9223196}\global"
[dshow @ 000001d5c5108dc0] DirectShow audio devices
[dshow @ 000001d5c5108dc0]  "Desktop Microphone (6- Microsoft┬« LifeCam Studio(TM))"
[dshow @ 000001d5c5108dc0]     Alternative name "@device_cm_{33D9A762-90C8-11D0-BD43-00A0C911CE86}\wave_{D5F4881A-6E88-4563-8BA0-081CFD50E353}"
[dshow @ 000001d5c5108dc0]  "Desktop Microphone (5- Microsoft┬« LifeCam Studio(TM))"
[dshow @ 000001d5c5108dc0]     Alternative name "@device_cm_{33D9A762-90C8-11D0-BD43-00A0C911CE86}\wave_{84674B28-DC68-4AC0-8331-D687C7B7D69C}"
[dshow @ 000001d5c5108dc0]  "Digital Audio (S/PDIF) (High Definition Audio Device)"
[dshow @ 000001d5c5108dc0]     Alternative name "@device_cm_{33D9A762-90C8-11D0-BD43-00A0C911CE86}\wave_{CDD24485-59D2-4BED-B6FC-B7447251C7E2}"


  



  Because the two cameras have a same device name, I couldn't stream two videos using this simple command at a same time : ffplay -f dshow -i video=Microsoft® LifeCam Studio(TM).
  
So I used pin names following the ffmpeg dshow example.
The only thing I could check was Could not find video device with name [video=~~pin name~~] among source devices of type video.

  



  What ffplay command makes enable to stream both videos ?

  


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