-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The song seems to loads but doesnt play🐛 #1644
Comments
the console doesnt show any error whatsoever also |
Also also, this installation used to work about 4-5 days ago just fine for the last year, this issue only appeared as of today to my knowledge |
/node_modules/@discordjs/rest/dist/index.js:719 |
I have the same problem. Even a repull of the imges does not bring any change. |
Yup, can confirm. Bot no longer works. |
Same issue. EDIT: the problem is that makeResource() uses play-dl which seems to have a problem today and be stuck on buffering. EDIT2: for example changing play-dl to ytdl-core (install firsst) starts the resource replay:
|
interesting, that would be a very decent fix until the bot gets a proper update (ran npm install ytdl-core and edited my song.ts according to your fix, works flawlessly) |
Confirming, @crackodille fix works However its very breakupy, and buffery, it constantly stops and speedups |
any updates on this? |
I've ran a long video, and bot seems to crash with the new package
|
I ASSUME this is the issue that causes the current problem on play-dl edit: I just read the comment in the pull request pointing to this issue, my bad lol |
how can i edit that in docker? |
any updates? same issue here :( no errors whatsoever, but it seems that the stream data is empty. |
It seems a lot of bots, api and other apps aiming to download YouTube videos rn are having problems, with the changes Google is pushing, i believe we'll have a rough road ahead We may need to look towards other sources such as SoundCloud soon for discord bots |
This has been an ongoing battle for many years with YouTube, including at one point Google/YouTube going after package authors and issuing DMCA takedowns on their projects here on GitHub. I'm honestly not surprised, and this seems to come in waves. Unfortunately for me, even the pull request version is not working, as I am getting 429 errors on the first try. It looks like this will be another long-winded fight with YouTube again. |
I have not tested this fork but someone in the comments of this issue submitted their fork of play-dl which works thru the ios extractor, seems to be a good workaround for now from my understanding |
youtube : use our plataform, it is the best |
Had a similar problem, my bot which used play-dl is no longer working. Interestingly, it seems to work fine for me when I try to play livestreams(like 24/7 lofi streams for example) |
Someone have 403 error too? |
The error is related to the node modules that are used. Currently it seems that the maintainers of the modules do not take proper action to adapt them. (no accusation) I have switched to writing my own bot with Python. If there is interest, the code can be made public. Unfortunately I have no hope that the required node modules will be fixed in time. |
Describe the bug
Everything goes as expected until the very moment you would expect the bot to start playing the sound, it logs in and replies to my /play command correctly but the green circle never appears, no sound is heard and /nowplaying shows the bot hanging at 00:00:00 time as if its paused, /resume, restarting, adding another song etc. doesnt rectify this issue, I feel it may have a problem obtaining the files from youtube.
How To Reproduce
Steps to reproduce the behavior:
1.run latest version
2./play any song
Expected behavior
self explanatory (id like it to play the song after it logs in and acknowledge the request)
Environment (add if possible)
OS: Debian GNU/Linux 11 (bullseye) aarch64
Host: Raspberry Pi 400 Rev 1.1
Kernel: 5.15.84-v8+
CPU: BCM2835 (4) @ 1.800GHz
No docker, runs on bare metal
Additional information & screenshots
I've updated the files using npm update twice, it would seem all packages are up to date
The text was updated successfully, but these errors were encountered: