I know I’ve made other request concerning original release dates, but those are more aesthetics. This one is functional. I did search through the settings for this, but did not find anything.
Use the original release date tag when building a decades mix instead of the regular release date tag.
Problem solved:
Most people tag libraries based on the releases they own. So I might have a record that original came out in the 50s, but the version I own came out in the 90s. Maybe it was remastered, has extra tracks, etc.
By using the regular release date tag, this causes two problems. It puts a 50s record in my 90s mix. Also, it keeps this record out of my 50s mix.
Brought benefits:
Allows for much more accurate decades mix as it builds them based on when the actual music was released instead of when that version was released.
Other application solutions:
I believe original date has other applications as explained in previous requests, but this one is just focused on in practice request.
As far as I know, it is standard practice to use the original release date as the default if two release dates are available as tags.
This also seems to make logical sense to me.
If, as in your case, this is not desired, the developer would have to create an additional settings menue.
As an alternative, I have disabled the non-editable decade mix function and created an additional smart playlist for my most important decades and pin these playlists to the startpage. With smartplaylist you can choose between original and special release date as desired.
How-to: Create a Smart Playlist according to your wishes. In the 3-dot menu there is the sub-item “Add to start page”.
Maybe I’m misunderstanding what you mean here, but using the Original Date Is what I would desire. Right now, it does not use original dates. (For me, at least).
Funny. For me it’s the other way around: the original release date is used. However, the alternative with smart playlist shown above would be exactly the same to solve your problem.
The default field for all MP3 tags is not the field for the original release date, but the field for the release year of the current release. Many taggers don’t even have the ability to edit this field. I used to use Winamp and now MusicBee, so it works.
The “original release date” tag is very useful, e.g. if, as you write, an old release is remastered later.
What you achieve: You listen to the Rolling Stones in a 60s playlist even though it is the remaster from 2020.
What you prevent: You don’t hear the Rolling Stones in a 2020 playlist because the original was released in the 60s.
Have you used a tag inspector to check which values are actually entered in the various fields? Maybe that will clear up your problem.
Yea I use picard for everything. They’re tagged correctly, at least as far as mbz goes.
I know we’ve talked about aritst added dates, i don’t think we have about orignal release tags, but i guess i just dont know what exactly to tell lms isn’t being ported over correctly.
As you can see here lms is providing both dates. And symfonium is displaying both dates from lms:
Just tried this with a playlist of Years from “2010” to “2024” and it inlcuded any reissues of older albums that happened to be released during those years. Do you mind screenshotting the rules you make for your playlist? And which provider are you using?
, i don’t think we have about orignal release tags
Yes we have many, many times, each time you asked about OG dates and years.
There’s different tags, year, release date and original date.
If you want to change the year in Symfonium it needs to be done at your provider level as it’s what is used for decade mixes …
Symfonium properly generate the year from original date first if present the release date then year unless you enable an option to force the year tag to be first for the files it scan itself else it use the year from the provider.
You need to see with @itm how it’s handled in LMS.
About the smart playlist of course if you use year as filter it will use the year … To use original date filter on original date.
The year field is populated using the date, not original date.
I see navidrome seems to report the year using original date, but only for albums. It uses the regular date field to populate year for tracks.
@Bigmack3000 I think we are talking about different things.
With Smartplaylist there is only one year to choose from. If your mp3 has different years, the original release year is prirorized.
Both rules must apply:
Rule 1: Year greater than 1999
Rule 2: Year less than 2011
->and you have all mp3s from the year 2000-2010 in your playlist
But if an mp3 has an original release year outside these years, it will not appear in the playlist. But this is also logical.
However, if a track from the 50s still appears in this 2000s list, then an incorrect year has been entered somewhere in the tag field, probably in the original release year. To check this, you need a tag inspector (not this screenshot from above) that lists all the tag details of your MP3.
This is the only way to find the error.
But, what do i do to make a playlist out of them from the album page after that?
Would it not be easier for users to add original date as an option in smart playlist as well? There are so many other choices, but its missing from it currently:
