I hear you.
My music collection is just under 10,000 songs and 91gb (slightly less if I properly de-dupped it).
I was thinking of coding some software that could manage it all.
I've created SQL Server databases will millions of records in it before, and with dedicated hardware it's fast; under 10 seconds for a full scan of millions.
30,000 rows in a table is nothing to SQL Server.
and loading up a saved playlist would be instant.
There are a lot of nice players out there, just need something to manage the collection, search and compose a playlist to pass on to the player to play.
Eventually I might be forced to build something out of sheer necessity, thus far I've gotten by by sorting my music into artist operating-system folders, and correctly named files; and managing small playlists in foobar manually.
Metadata is another ball of wax. Correcting it isn't something that interests me from a coding perspective.
I'm not a pretty-pictures type of person, I'm not interested in looking at album covers and/or album names. Bare metal filename is good-enough for me to know what it is. (Maybe I've just lived too many decades without that stuff... LOL)
But when I read things like "the software slowed at just 5,000 or 50,000 songs" it makes me sigh and cringe at the programmers who make such drivel... the boss probably hired some know-nothing, someone fresh out of school to make it.
Files and File Info shouldn't be used as a replacement for rows in a db. (good god! pulls hair out!)
My music collection is just under 10,000 songs and 91gb (slightly less if I properly de-dupped it).
I was thinking of coding some software that could manage it all.
I've created SQL Server databases will millions of records in it before, and with dedicated hardware it's fast; under 10 seconds for a full scan of millions.
30,000 rows in a table is nothing to SQL Server.
and loading up a saved playlist would be instant.
There are a lot of nice players out there, just need something to manage the collection, search and compose a playlist to pass on to the player to play.
Eventually I might be forced to build something out of sheer necessity, thus far I've gotten by by sorting my music into artist operating-system folders, and correctly named files; and managing small playlists in foobar manually.
Metadata is another ball of wax. Correcting it isn't something that interests me from a coding perspective.
I'm not a pretty-pictures type of person, I'm not interested in looking at album covers and/or album names. Bare metal filename is good-enough for me to know what it is. (Maybe I've just lived too many decades without that stuff... LOL)
But when I read things like "the software slowed at just 5,000 or 50,000 songs" it makes me sigh and cringe at the programmers who make such drivel... the boss probably hired some know-nothing, someone fresh out of school to make it.
Files and File Info shouldn't be used as a replacement for rows in a db. (good god! pulls hair out!)