Recherche avancée

Sur d’autres sites (12429)

• Own music discord bot : FFmpeg/avconv not found. Can someone help me ?

  23 mai 2020, par CreepyGamerCat

  I guess the code is right because the bot finds a song and also joins a voice channel, but it can't play songs, because of this error. The ffmpeg.exe, ffmplay.exe, ffm.probe.exe and YouTube-dl.exe files are in the same folder. (directory : desktop>Discord Bot>node_modules>bin.) Maybe this is a wrong folder, I forgot a important file or whatever. I hope you can help. I use Visual Studio Code in JavaScript.

  


• FFMPEG.wasm Cannot Add Album Cover To MP3 File

  5 juillet 2022, par Shaan Khan

  for a project I'm working on I'm trying to split a video into multiple audio clips whilst adding metadata for each individual track. Whilst doing this, whilst I've added most of the metadata including title & artist, I'm unable to add an album cover via FFMPEG.wasm. Whilst my command works fine with regular FFMPEG.wasm, I'm unable to get it to work via the webassembly version.

  


  I'm aware that my album cover is correctly being assigned via FS.readfile and that my command in theory should work, but I'm unable to figure out why it isn't working. Is this a FFMPEG.wasm limitation and if so, is there any workaround for this ?

  


  

  • Normal FFMPEG Command

  


  


  ffmpeg -i "song.mp3" -i albumCover.jpg -map 0:0 -map 1:0 -y -codec:a libmp3lame -ac 2 -ar 48000 -ab 320k -ss 00:00:00 -t 00:00:20 -id3v2_version 3  -metadata title="SongOne" -metadata album_artist="Artist Name" -metadata album="Youtube Name" -metadata track="1" "output.mp3"


  


  

  • FFMPEG WASM Implementation

  


  


    let commandArray = [
      "-i",
      "song.mp3",
      "-i",
      "albumCover.jpg",
      "-map",
      "0:0",
      "-map",
      "1:0",
      "-y",
      "-codec:a",
      "libmp3lame",
      "-ac",
      "2",
      "-ar",
      "48000",
      "-ab",
      "320k",
      "-ss",
      startTime.toString(),
    ];

    if (duration != "-1") {
      commandArray.push("-t", duration.toString());
    }

    commandArray.push(
      "-id3v2_version",
      "3",
      "-metadata",
      `title="${title}"`,
      "-metadata",
      `album_artist="${artist}`,
      "-metadata",
      `album="${albumInfo.name}"`,
      "-metadata",
      `track="1"`,
      `${timestamp.songName} - ${timestamp.artistName}.mp3`
    );


  


• ffmpeg processes pile up until they crash

  9 mars 2021, par Ultra Cookie

  I am coding a bot which streams music using ytdl and @discordjs/opus. It uses ffmpeg for that and when I end the dispatcher the process doesn't get killed. After a while this piles up and the process list looks like this :

  


  0     0 27864 27863  20   0 120348 14380 sock_a Sl+  pts/2      0:01 /root/bot/node_modules/ffmpeg-static/ffmpeg -i - -analyzeduration 0 -loglevel 0 -f s16le -ar 48000 -ac 2 pipe:1
0     0 27887     1  20   0 120104 13496 sock_a Sl+  pts/2      0:00 /root/bot/node_modules/ffmpeg-static/ffmpeg -i - -analyzeduration 0 -loglevel 0 -f s16le -ar 48000 -ac 2 pipe:1
0     0 27893     1  20   0 120040 13676 sock_a Sl+  pts/2      0:00 /root/bot/node_modules/ffmpeg-static/ffmpeg -i - -analyzeduration 0 -loglevel 0 -f s16le -ar 48000 -ac 2 pipe:1
0     0 27900     1  20   0 120048 13676 sock_a Sl+  pts/2      0:00 /root/bot/node_modules/ffmpeg-static/ffmpeg -i - -analyzeduration 0 -loglevel 0 -f s16le -ar 48000 -ac 2 pipe:1
0     0 27906     1  20   0 120048 13676 sock_a Sl+  pts/2      0:00 /root/bot/node_modules/ffmpeg-static/ffmpeg -i - -analyzeduration 0 -loglevel 0 -f s16le -ar 48000 -ac 2 pipe:1
0     0 27913     1  20   0 103740 13792 sock_a S+   pts/2      0:00 /root/bot/node_modules/ffmpeg-static/ffmpeg -i - -analyzeduration 0 -loglevel 0 -f s16le -ar 48000 -ac 2 pipe:1



  


  This is just a preview the actual list is much longer... I don't know how I can prevent this.

  


  Code that might be helpful :

  


  Play:
connection.play(ytdl(song.url, { quality: "highestaudio", highWaterMark: 1024 * 1024 * 30, type: "opus" })).on("finish", () => {play next song});

Skip:
connection.dispatcher.end();