Feature-Request: "Load multiple local tracks"

[Tomato6966]

Description

loadtracks by providing a folder of mp3 files (I wouldn't allow nested requests just for the folder .mp3|.mov|*.ogg|etc.etc.

when doing /loadtracks?identifier=/home/path/to/folder/ it loads all existing possible files which load the tracks
when doing /loadtracks?identifier=/home/path/to/folder/*.mp3 it only loads files ending with .mp3 (aka glob support)

LoadType should be: "playlist"

Environmental Variable Suggestion:
localfilespages, each page allows to load up to 100 tracks

How I'd do it on nodejs manually, which isn't quite fast...

import { readdir } from "fs/promises";
// makeRequest is for my lavalink server, which uses this lavaplayer repository.
async function loadFolderPlaylist(path) {
  const files = await readdir(path).then(files => files.filter(fileName => /(.mp3|.mov)/igu.test(fileName)));
  const tracks = await Promise.all(files.map(async file => await makeRequest(`/loadtracks?identifier=${path}/${file}`)));
  return Utils.BuildPlaylistResponse(tracks)
}

[topi314]

If you're gonna open a feature request you don't follow the bug report template

[freyacodes]

What do you hope to gain from having Lavalink index a directory instead of what you're already doing?

[Tomato6966]

It should be easier and quicker
Also wouldn't it be cool to support that?

[freyacodes]

You're already sending asynchronous requests by the looks of it. I don't see any speed gain here. In fact, unless we'd be careful to make it internally asynchronous it would actually be significantly slower.

Also wouldn't it be cool to support that?

Local track support is an afterthought to begin with

[Tomato6966]

hmm ok

[topi314]

The only advantage I can see here is that if your node is remote you usually don't have access to the filesystem, like this you can just load a folder without exactly knowing which files are in there