-
Notifications
You must be signed in to change notification settings - Fork 7
Local files support #3
Comments
There is currently no way to play directly from the disk, however you can set up an http server to serve those files and use a network FileTrack (see docs/FileTrack.md) |
If this is something you need then I can work on this issue |
Was thinking about doing the same thing after making this issue. I believe that should work, but I'd love to see it natively supported in the future. |
May I know why you are using this as opposed to lavaplayer (lavalink)? |
Lavalink has this problem where the track would start playing briefly before the bot becomes fully connected since it doesn't emit a ready event. Sometimes it just stops sending the audio out of nowhere. I've tried other packages like djs/opus and they all cause memory leaks and fragmentation, and have inferior audio quality. |
See docs/FileTrack.md on how to use it For security purposes, you may want to prevent users from attempting to play local files on your system if you allow them to play from any arbitrary url if(track.isLocalFile) return; |
I forgot to mention that local file support is added, let me know if you have any issues |
I've been able to run it perfectly on local Ubuntu 20 but on Ubuntu 18 I'm getting this error for some reason.. |
I don't have experience with docker. Could you paste the error message from building ffmpeg from source? |
Also if your bot serves many people, its recommended to install ffmpeg from source to avoid the infinite loop problem |
Another thing is it may be required to update the npm packages via |
I didn't get any errors from that, the error was emitted from the TrackPlayer instance after calling start(). |
No problem 👍 |
Hello,
I have a sound pad bot that plays a lot of audio files directly from disk to reduce load times. Is it possible to implement local files support or is there already a way to do it?
Thank you!
The text was updated successfully, but these errors were encountered: