Recherche avancée

Sur d’autres sites (10805)

• I am getting this "Error : FFmpeg/avconv not found !"

  5 septembre 2024, par Fhabbulous

  I am trying to create a discord bot, however receive this error every time I try to run a youtube link.

  


  Error: FFmpeg/avconv not found!
    at Function.getInfo (C:\Users\-\discord-bot\node_modules\prism-media\src\core\FFmpeg.js:130:11)
    at Function.create (C:\Users\-\discord-bot\node_modules\prism-media\src\core\FFmpeg.js:143:38)
    at new FFmpeg (C:\Users\-\discord-bot\node_modules\prism-media\src\core\FFmpeg.js:44:27)
    at AudioPlayer.playUnknown (C:\Users\-\discord-bot\node_modules\discord.js\src\client\voice\player\BasePlayer.js:47:20)
    at VoiceConnection.play (C:\Users\-\discord-bot\node_modules\discord.js\src\client\voice\util\PlayInterface.js:71:28)
    at Object.play (C:\Users\-\discord-bot\commands\play.js:78:8)
    at Object.execute (C:\Users\-\discord-bot\commands\play.js:48:16)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:14004) UnhandledPromiseRejectionWarning: DiscordAPIError: Cannot send an empty message
    at RequestHandler.execute (C:\Users\-\discord-bot\node_modules\discord.js\src\rest\RequestHandler.js:170:25)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:14004) 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 unhandl
ed promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:14004) [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.


  


  I installed ffmpeg with npm install -g ffmpeg-binaries to try and install it globally. I also added ffmpeg to PATH, but that did not seem to work.

  


  Anyway to fix it ?

  


• FFMEG : run code after complete conversion

  26 octobre 2019, par Сергей Барахтенко

  There is a code that runs FFMPEG

  shell_exec($this->config->item('ffmpeg') . ' -i ' . $path . ' ' . $cmd . ' 1>' . $folder . '/log.txt 2>&1 ');

  And there is the following line, which should, taking into account the peculiarities of the PHP language, work out immediately after shell_exec

  $params = array(
  
      'status' => 'ready'
  
  );
  
  $result = $this->model->editVideo($video_key, $params); 

  This line simply updates the status of the video in the database

  My question is, why doesn’t the further php code work after completion shell_exec ? What could be the catch ?

• Revision 9265bad906 : Merge changes from topic 'x86inc' * changes : Only use .text sections for aout

  10 août 2015, par James Zern

  Merge changes from topic ’x86inc’

  * changes :
  Only use .text sections for aout
  Use newer x86inc.asm
  Use .text instead of .rodata on macho
  Copy PIC handling code from x86_abi_support
  Set ’private_extern’ visibility for macho targets
  Avoid ’amdnop’ when building with nasm
  Catch all elf formats
  Expand PIC default to macho64 and respect CONFIG_PIC from libvpx
  Use libvpx defines to set name mangling rules
  Customize x86inc.asm for libvpx