discord-player: [BUG] Error: write EPIPE

When I use !filter this error is sent - Error: opus stream: write EPIPE But filter was added.

To Reproduce

  1. Use any filter

Expected behavior 2. No error 3.

Please complete the following information:

  • Node Version: node 12.22.1
  • Library Version: discord-player 4.0.5
  • Discord.js Version: discord.js 12.5.3

Additional context I don’t know what script to send, please write in the comments if you need one And also, if I don’t use const ytdl = require ('ytdl-core'); I have a stream destroy error or something …

Full Error: Error: opus stream: write EPIPE at WriteWrap.onWriteComplete [as oncomplete] (internal/stream_base_commons.js:94:16) { errno: 'EPIPE', code: 'EPIPE', syscall: 'write' }

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 47 (12 by maintainers)

Most upvoted comments

Hello, you can catch that error with Player#error event. Also, in some cases, using filter: "audioonly" fixed the issue.

You can supply the filter option from PlayerOptions

const player = new Player(client, {
    ytdlDownloadOptions: {
        filter: "audioonly"
    }
})

Handling error event in v5 will catch this error. I can’t say that v5 will get rid of this completely because this can happen due to several reasons but it should reduce this error 👍

using nodejs v14 fixed the problem?

So far it did for me, haven’t seen the message in 2 days and before updating to v14 it was thrown almost every 2 songs

update to node.js 14x or up @NotroDev

I am hosting the bot in cloud platform and I am getting this issue whenever I add any playlist to play either it is YT or Spotify. Screenshot_2021-05-09-18-11-18-945_com.discord.jpg

And yes this err is not generating in windows.

Yes so this seems to be the same as #392 I suggest you to log the error in the console so it won’t be spamming the text channel, it’s either a fffmpeg problem with the linux pipes, or maybe in the discord-player code it could be somehow dispatched, but I’m not sure so as I said use the error event to log throw it on console or just to ignore it.