I have an extensive fully and accurately tagged music collection including use of the Release Date where for classical music is the original publication or first performance. Plex server/library has mapped all these pre-1900 date to a date between 1900 and current. (1875>2016, 1762>1998, etc). With option to ‘use local metadata’ all other mapping to the Plex library is otherwise perfect.
My other primary media players & servers (like MediaMonkey) fully support Release Date (and Year) prior to 1900. My collection has over 1500 mp3 with dates prior to 1900 and not only has it never been an issue, it is a feature to be able to play music from any year or decade prior to 1900.
Because these earlier dates are mapped to an incorrect date by Plex that results in ruining the use of music by decade for all files. (could be little better if pre-1900 dates were all mapped to 1900 or ‘unavailable’ for example)
It would be very helpful if this could be fixed as Plex is otherwise looking to be able to replace and better my current media server (as Plex lets me play music and show slideshow at simultaneously and supports mobile apps).
Right now the oldest dates I have tagged are in the 1520s.
(I think a solution would be transparent to those who typically stick to the current century or so as the server only shows date/decade folders for which there are tagged files. )
I have been primarily using ‘Plex Music Scanner’ with ‘Personal Media Artists’ agent as I only want to use local/tagged metadata and ‘Plex Music’ with ‘Plex Music’ agent runs slow scanning files for a sound imprint ID only to try to add information I already have tagged or otherwise don’t want.
But this suggests there is a difference so I set up a test library with ‘Plex Music/Plex Music’ and ran it overnight (it only completed some my >18,000 mp3), but of those it did add to library they have an accurate ‘Year’ field! (although I’ve started to notice some are off by 1yr ) However the ‘Release Date’ field still doesn’t map correctly with unexpected dates for pre 1900.
Is it possible to get a sample file/track that you know causing this issue. Also can you please confirm the exact server version you are currently using.