-
-
Notifications
You must be signed in to change notification settings - Fork 672
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
Play-dl support #534
Comments
I seriously doubt Lavalink will ever switch from Lavaplayer because the whole purpose is to provide a separate Lavaplayer node. Besides that, it wouldn’t work anyway seeing that’s an npm package and Lavalink is written in either java or kotlin (i forget) |
I'm not opposed to having multiple downloader libraries. The big issue is that play-dl is a JS library which is difficult to integrate into a JVM application like Lavalink. It might be possible with something like GraalVM, but that would require users to switch to that specific JVM. https://www.graalvm.org/reference-manual/js/JavaInteroperability/ The downloaded audio would then go through Lavaplayer to be processed. Significant changes would have to be made to Lavalink to make all of this possible.
Both! They are interoperable JVM languages. |
check this out https://github.com/AmandaDiscord/Volcano its 1:1 replacement for lavalink which runs on js and ytdl. It mirrors the lavalink api so no code needs to be rewritten |
would not recommend tbh |
play-dl is basically unstable through my experience. I cannot be so sure that changing downloader to Node.js based library will improve the quality of Lavalink. |
Use play-dl for extracting YT videos.
https://www.npmjs.com/package/play-dl
The text was updated successfully, but these errors were encountered: