AnSniper 16 Posted May 24, 2022 Share Posted May 24, 2022 In the latest stable version, some albums can correctly identify the release date of the album, while others cannot. For example, after I get music metadata through other software and write songs, it can be correctly identified by importing into emby media library, but if I edit metadata through Mp3tag, emby seems to be unable to correctly identify the release date. I don't know if it's caused by Mp3tag or something? Is it because the release dates of the songs on the same album are different, so they can't match? The following are the conditions that can be correctly identified emby&mp3tag: Link to comment Share on other sites More sharing options...
Luke 37260 Posted May 24, 2022 Share Posted May 24, 2022 hi, I'm guessing after it's imported, if you edit the embedded information in the audio files, Emby Server will see the new release date for the track and update that, but it won't change the album release date. Link to comment Share on other sites More sharing options...
AnSniper 16 Posted May 24, 2022 Author Share Posted May 24, 2022 @卢克 However, if I manually fill in the song age information in the form of xxxx-xx-xx through Mp3tag and save it, it will not be recognized correctly in emby! I don't know whether this is caused by Mp3tag or whether emby doesn't match the date correctly??? Link to comment Share on other sites More sharing options...
AnSniper 16 Posted May 24, 2022 Author Share Posted May 24, 2022 (edited) @卢克 When the release date of the song information in the album is the same, can it be determined as the release date of the album? Or take the early Song release date as the album release date? Although I don't know if it's the same album, the release date is different. Edited May 24, 2022 by AnSniper Link to comment Share on other sites More sharing options...
AnSniper 16 Posted May 24, 2022 Author Share Posted May 24, 2022 In my case, as long as I modify the song metadata through Mp3tag once, no matter what I modify, emby can't correctly identify the release date of the album and song. Could it be due to the encoding of Mp3tag? I don't know how to write metadata information in dvtag, but it seems that the whole release date can be written in years, such as xxxx-xx-xx. Link to comment Share on other sites More sharing options...
Happy2Play 8356 Posted May 24, 2022 Share Posted May 24, 2022 I don't follow before MP3TAG change after tag change and library scan Manually edited date in the box Or edit via Extended tags Link to comment Share on other sites More sharing options...
AnSniper 16 Posted May 25, 2022 Author Share Posted May 25, 2022 (edited) On 5/25/2022 at 12:38 AM, Happy2Play said: I don't follow By comparing the discovery date and MP3 metadata that can't be displayed correctly, I know where my problem is. When I edit "tag" as "Id3v2.4 (ID3v1 Id3v2.4)" in Mp3tag and fill in xxxx-xx-xx format in "year", emby can perfectly identify the song and album release date. However, if Mp3tag edits "tag" to "Id3v2.3" (ID3v1 Id3v2.3), even if you fill in xxxx-xx-xx format in "year", emby can only match the year, not the specific release date. I don't know if it's due to the difference between the two versions, Edited May 25, 2022 by AnSniper Link to comment Share on other sites More sharing options...
Happy2Play 8356 Posted May 25, 2022 Share Posted May 25, 2022 12 minutes ago, AnSniper said: On 5/24/2022 at 9:38 AM, Happy2Play said: I don't follow By comparing the discovery date and MP3 metadata that can't be displayed correctly, I know where my problem is. When I edit "tag" as "Id3v2.4 (ID3v1 Id3v2.4)" in Mp3tag and fill in xxx-xx-xx format in "year", emby can perfectly identify the song and album release date. However, if Mp3tag edits "tag" to "Id3v2.3" (ID3v1 Id3v2.3), even if you fill in xxx-xx-xx format in "year", emby can only match the year, not the specific release date. I don't know if it's due to the difference between the two versions, I get the same resulted with either version in my tests. FFPROBE see it as the DATE tag and reads it. Link to comment Share on other sites More sharing options...
AnSniper 16 Posted May 25, 2022 Author Share Posted May 25, 2022 (edited) 3 minutes ago, Happy2Play said: I get the same resulted with either version in my tests. FFPROBE see it as the DATE tag and reads it. I have filled in Chinese in the metadata. Will this have an impact? In the old version (2.3), it seems that only the year can be obtained in emby, while in the new version (2.4), the release date and year can be obtained directly. Edited May 25, 2022 by AnSniper Link to comment Share on other sites More sharing options...
Solution Happy2Play 8356 Posted May 25, 2022 Solution Share Posted May 25, 2022 1 minute ago, AnSniper said: I have filled in Chinese in the metadata. Will this have an impact? In the old version (2.3), it seems that I can only get the year in emby, while in the new version (2.4), I can directly get the release date and year. It shouldn't as numbers are numbers. But multiple different versions may have fields that override each other/order of precedence. In the End it is a matter of what ffprobe sees. ffprobe -i "path to file" Link to comment Share on other sites More sharing options...
AnSniper 16 Posted May 25, 2022 Author Share Posted May 25, 2022 3 minutes ago, Happy2Play said: In the End it is a matter of what ffprobe sees. ffprobe -i "path to file" Although I don't quite understand the principle, I can solve my problem by using the new version (2.4). Thank you for your answer. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now