Feature Request: Use database for song information storage

[iMelsom]

Right now only song title and artist is variables available, but by adding an database we could also have extended data:

• artist
• co-artist (s)
• album
• song title
• atlernate song titles
• Personal tags

[jramboz]

Using a DB might also help address the large libraries issues. I know that's how most karaoke programs tend to operate. But it seems like it might be a pretty big overhaul to switch to this.

[dpitcock]

Setting up and using a db doesn't seem like a big issue here. SQLlite or MySql would work. The problem is parsing the data, especially from the sources we have. Mp3's with CDG have the metadata possible, but youtube source files do not, that is not even including the titles of the videos being wrong, excess wording, misspellings, etc.

[BramWerbrouck]

Using a database could be very handy to order the song list alphabetically not only on the first letter (I mean depending if you used TITLE - ARTIST or ARTIST - TITLE). You could just store the title, artist, path,.. this way you can choose on what you want to order. The only problem here is that you have to still use the same sequence of naming the files

also, when using a database, you would be able to get ‘favorite’ songs, you could track wich song is played the most and you can order on this..

[eddiemartinez22]

I would love to see a way to import large libraries by either "artist - title" or "disc id - artist -title". Something along those lines to make the browse function a little cleaner. Currently, I have a lot of DISCID's listed in alphabetical order. It's not a huge issue but a nice to have. The program works great and I appreciate all the effort that's been put in. Thanks!