No, I think those are the Windows people who put / in the file names, because back then Windows wasn’t really restrictive about stupid file names. At least I think it isn’t possible anymore, but can’t confirm, because I don’t use Windows for around 15 years.
The long filename system allows a maximum length of 255 UCS-2 characters including spaces and non-alphanumeric characters (excluding the following characters, which have special meaning within the COMMAND.COM command interpreter of the operating system kernel: \ / : * ? " < > |).
I’ve used Spotify since about 2012, and have been considering setting up some *arr instances at some point in the future to remedy that. Music discovery is just so much easier on something like Spotify though.
Mine is Artist name - Song name [(Version)] (Year)[(Bitrate)]
Version is optional. It’s stuff like Radio edit, remastered, extended, etc.
Bitrate is optional as I switched to FLAC and rarely need to use MP3.
The worst one I have is something from Beatles in 32kbps HE-AAC at 22.5kHz SR with name written in Chinese. It is one of the oldest files I have.
I find it a little bit weird to put meta data in the file name. Meta data is already there and you can see it on your computer with the tool exiftool (if you’re on a Linux system).
But I think you’re not on a Linux system, because you would avoid white spaces then :D
Welp, not if you used to rip from YouTube. And the files ripped from Deezer have wrong year most of the time anyway because they used it for file creation date.
And when my music touches my computer it’s only because I am backing it up (as I should be doing). The only correct information is on CD rip of “The very best of Louis Armstrong” because I put that in myself using Kid3.
please use a dash between artist and song name you uncivilized person!
As someone who had one of these, I’m just surprised there’s any consistency at all
There is rock hard consistency!
I still use mp3s today (no spotify or similar bullshit) and stick to the name convention: [ARTIST_NAME]-[SONG_NAME].mp3
Mine are always [artist]/[album]/[tracknumber]-[title]
I used to use Ogg, but I’m switching to Opus because it’s a superior format.
slashes in file names is just barbaric, if you use a good and free operating system, too :)
Seems to me more like they’re just organizing their music collection into directories
we call them paths, ᏏᎡᏌᎻ
No, I think those are the Windows people who put / in the file names, because back then Windows wasn’t really restrictive about stupid file names. At least I think it isn’t possible anymore, but can’t confirm, because I don’t use Windows for around 15 years.
Long filename (LFN) Limits
Edit: Markdown Code format issue?
I’ve used Spotify since about 2012, and have been considering setting up some *arr instances at some point in the future to remedy that. Music discovery is just so much easier on something like Spotify though.
I still discover music the old way. I listen to it at a friends place or in the radio :D
Sonarr, Radarr, and related projects for, uh. Sailing the high seas. :-)
Mine is
Artist name - Song name [(Version)] (Year)[(Bitrate)]Version is optional. It’s stuff like Radio edit, remastered, extended, etc.
Bitrate is optional as I switched to FLAC and rarely need to use MP3.
The worst one I have is something from Beatles in 32kbps HE-AAC at 22.5kHz SR with name written in Chinese. It is one of the oldest files I have.
I find it a little bit weird to put meta data in the file name. Meta data is already there and you can see it on your computer with the tool exiftool (if you’re on a Linux system).
But I think you’re not on a Linux system, because you would avoid white spaces then :D
Welp, not if you used to rip from YouTube. And the files ripped from Deezer have wrong year most of the time anyway because they used it for file creation date.
And when my music touches my computer it’s only because I am backing it up (as I should be doing). The only correct information is on CD rip of “The very best of Louis Armstrong” because I put that in myself using Kid3.