I have tough question for you: how good your service in understanding convoluted metadata and non-traditional formats?
I have about 2.5Tb of Music, and I can not import it to any media management / streaming self-hosted service (including Subsonic and all other DLNA servers & Ko).
Problem is... Metadata. Messy metadata.
Typical solution imports 1/2 of my collection Ok, 1/4 with mangled metadata and 1/4 without metadata at all or can not import completely.
Typical pain points:
(1) Metadata contains "Unknown Artist - Track01", but filenames are Ok and all information can be extracted from file names.
(2) It is FLAC, one file per Album, internal CUE and additional CUE file which references (absent) WAV file in same folder. Typical software duplicate such albums and one copy works, and other is "Not found" - and you must try to play to distinguish two. Some software can not understand embedded CUE at all, and show this as one big track + not-working album (because it can not find WAV referenced by CUE).
(3) FLAC, file per track, with per-track metadata, and CUE which reference all these files to add proper between-track pauses. Typical result: two identical albums. Often such CUE is rejected as "invalid" (because such CUE are "non-standard" extension invented by Exact Audio Copy software), and then it is Ok, but - see next item.
(4) FLAC, flile per track, files doesn't contain any metadata, but there is CUE which reference all these files. It works Ok, if CUE is not rejected as invalid, and, again becomes "Unknown Author - Unknown Album - Track N" if CUE was rejected (often).
(5) Same as 2-4 with APE, WavePack or TTA (do you know this format?) instead of FLAC.
(6) Such monstrosity as ISO9660 image which contains WavePack file (one, whole album), CUE, LOG, some JPEGs. With extension ".iso.wv". Looks like only foobar2000 on Windows can show such container properly, as one album packed with WavePack.
(7) ID3v1 with some non-latin characters in some 8 bit codepage (typically Win-1251 Cyrillic, but not always).
(8) ID3v1 with UTF-8 characters.
(9) ID3v2 with non-UTF-8 national characters.
(10) CUE files in single-byte codepages and not UTF-8 / CUE files in UTF-8. Different variants cause problems for different software.
I'm really struggle to "publish" my collection to listen to it on-the-go...
I have about 2.5Tb of Music, and I can not import it to any media management / streaming self-hosted service (including Subsonic and all other DLNA servers & Ko).
Problem is... Metadata. Messy metadata.
Typical solution imports 1/2 of my collection Ok, 1/4 with mangled metadata and 1/4 without metadata at all or can not import completely.
Typical pain points:
(1) Metadata contains "Unknown Artist - Track01", but filenames are Ok and all information can be extracted from file names.
(2) It is FLAC, one file per Album, internal CUE and additional CUE file which references (absent) WAV file in same folder. Typical software duplicate such albums and one copy works, and other is "Not found" - and you must try to play to distinguish two. Some software can not understand embedded CUE at all, and show this as one big track + not-working album (because it can not find WAV referenced by CUE).
(3) FLAC, file per track, with per-track metadata, and CUE which reference all these files to add proper between-track pauses. Typical result: two identical albums. Often such CUE is rejected as "invalid" (because such CUE are "non-standard" extension invented by Exact Audio Copy software), and then it is Ok, but - see next item.
(4) FLAC, flile per track, files doesn't contain any metadata, but there is CUE which reference all these files. It works Ok, if CUE is not rejected as invalid, and, again becomes "Unknown Author - Unknown Album - Track N" if CUE was rejected (often).
(5) Same as 2-4 with APE, WavePack or TTA (do you know this format?) instead of FLAC.
(6) Such monstrosity as ISO9660 image which contains WavePack file (one, whole album), CUE, LOG, some JPEGs. With extension ".iso.wv". Looks like only foobar2000 on Windows can show such container properly, as one album packed with WavePack.
(7) ID3v1 with some non-latin characters in some 8 bit codepage (typically Win-1251 Cyrillic, but not always).
(8) ID3v1 with UTF-8 characters.
(9) ID3v2 with non-UTF-8 national characters.
(10) CUE files in single-byte codepages and not UTF-8 / CUE files in UTF-8. Different variants cause problems for different software.
I'm really struggle to "publish" my collection to listen to it on-the-go...