Announcement

Collapse
No announcement yet.

An old "friend" is back: Album split in 2 albums

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • An old "friend" is back: Album split in 2 albums

    >> Did that join all tracks on one album again? I would expect this to
    >> "fix" the database. And thereafter touch some tracks should no longer
    >> cause splitting the album.

    >
    > I expected this, too - but it didn't. Scanner recognized all (13) tracks
    > as scanned but still kept them in 2 different albums as before


    Hmm... thinking about this again it might not work indeed: what the
    change does is not compare the literal title (because there's often too
    much encoding confusion...), but it uses the same "title search" value
    we're using in other places, which is kind of a normalized title. But
    these are the same now for old and new. Therefore it's possible it
    doesn't re-assign, as the album title would match any of the two.

    I guess changing the album title of all tracks, rescan, change back,
    rescan, would "fix" your database without the need for a full wipe & rescan.

    As for the artwork: the artwork ID is based on the artwork file's
    timestamp. As for embedded artwork this timestamp is the same as the
    music file's timestamp, it did change. And thus triggers new pre-caching
    of that artwork. It does not compare the actual file content, only the
    file's timestamp.

  • #2
    An old "friend" is back: Album split in 2 albums

    An old bug seems to be back - unfortunately I recognized it only 2 scans afterwards so I didn't save the actual log files, but maybe You still know what was the problem:

    - I have an existing album
    - I change the title tag (in this case adding "(Radio Edit)" to the existing track #3 - no other changes, no renaming
    - I do a "new & changed"-scan
    - I have 2 albums by the same artist with the same name in my db - one containing only track #3, and one containing tracks #1-2 and #4-12

    Do You remember the issue (and maybe the solution) and/or can You reproduce it or should I try (will start to keep logs with my next scans again)?

    Thanks,
    Frank

    Comment


    • #3
      Originally posted by frank1969
      An old bug seems to be back - unfortunately I recognized it only 2 scans afterwards so I didn't save the actual log files, but maybe You still know what was the problem:

      - I have an existing album
      - I change the title tag (in this case adding "(Radio Edit)" to the existing track #3 - no other changes, no renaming
      - I do a "new & changed"-scan
      - I have 2 albums by the same artist with the same name in my db - one containing only track #3, and one containing tracks #1-2 and #4-12

      Do You remember the issue (and maybe the solution) and/or can You reproduce it or should I try (will start to keep logs with my next scans again)?

      Thanks,
      Frank
      Which LMS version are you running? Some work was done on "new and changed" scans in recent 8.3 versions.

      Sent from my Pixel 3a using Tapatalk
      Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
      Bedroom: Radio
      Bathroom: Radio

      Comment


      • #4
        Originally posted by slartibartfast
        Which LMS version are you running? Some work was done on "new and changed" scans in recent 8.3 versions.
        Always the latest nightly (checking before every scan), so those scans were done with 8.3.0 r1647754697 on Windows 11.

        I remember Michael fixed this issue some weeks ago - now it seems to be back...
        Last edited by frank1969; 2022-03-27, 13:27.

        Comment


        • #5
          This happens to me quite a bit. I put a skip sentinel file in the album folder, scan again, then remove the sentinel and scan a final time. That typically "fixes" it.

          Something similar happens when I edit tags: the album might not be split, but the revised tags "append" to the old ones rather than replace them.

          Would be great if "new/changed rescan" could completely flush and rebuild the database entry for any detected files.

          I'm running a current 8.3 beta on Windows.

          Comment


          • #6
            Originally posted by frank1969
            Always the latest nightly (checking before every scan), so those scans were done with 8.3.0 r1647754697 on Windows 11.

            I remember Michael fixed this issue some weeks ago - now it seems to be back...
            I tried editing a track title tag and a "new and changed" scan didn't pick it up even though the file modified date is today.

            Edit. I was being an idiot and didn't copy the changed file across to the main library [emoji1787].


            Sent from my Pixel 3a using Tapatalk
            Last edited by slartibartfast; 2022-03-27, 14:12.
            Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
            Bedroom: Radio
            Bathroom: Radio

            Comment


            • #7
              Originally posted by slartibartfast
              Which LMS version are you running? Some work was done on "new and changed" scans in recent 8.3 versions.

              Sent from my Pixel 3a using Tapatalk
              When I finally managed to change a title tag I didn't see the album being split in two. Are you absolutely sure you didn't change something else?

              Sent from my Pixel 3a using Tapatalk
              Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
              Bedroom: Radio
              Bathroom: Radio

              Comment


              • #8
                In the past, this would happen to me, when everything appeared the same, but one file had a "disc total" tag field, or something similar that made that track different. (this might happen if I re-ripped just one track at the time of ripping the disk)
                Home: Pi4B-8GB/pCP8.2.x/4TB>LMS 8.3.x>Transporter, Touch, Boom, Radio (all ethernet)
                Cottage: rPi4B-4GB/pCP8.2.x/4TB>LMS 8.3.x>Touch>Benchmark DAC I, Boom, Radio w/Battery (Radio WIFI)
                Office: Win11(64)>foobar2000
                The Wild: rPi3B+/pCP7.x/4TB>LMS 8.1.x>hifiberry Dac+Pro (LMS & Squeezelite)
                Controllers: iPhone14Pro & iPadAir5 (iPeng), CONTROLLER, Material Skin, or SqueezePlay 7.8 on Win10(64)
                Files: Ripping: dBpoweramp > FLAC; Post-rip: mp3tag, PerfectTunes, TuneFusion; Streaming: Spotify

                Comment


                • #9
                  Originally posted by garym
                  In the past, this would happen to me, when everything appeared the same, but one file had a "disc total" tag field, or something similar that made that track different. (this might happen if I re-ripped just one track at the time of ripping the disk)
                  Yes, I know this constellation so I take care of "what I Do". The proof is, that all other files still show "last changes" on 2022-03-09, only the changed one has 2022-03-26.
                  Double-checked it using mp3tag - there are only 2 tags that are different in this album/folder, what are "title" and "track". All other files show the same (or no) value(s)...

                  Comment


                  • #10
                    Originally posted by frank1969
                    Yes, I know this constellation so I take care of "what I Do". The proof is, that all other files still show "last changes" on 2022-03-09, only the changed one has 2022-03-26.
                    Double-checked it using mp3tag - there are only 2 tags that are different in this album/folder, what are "title" and "track". All other files show the same (or no) value(s)...
                    title is song title. track is track number. Be sure and look at "extended tags" in mp3tag, in order to see all tag fields that might exist. I think you probably are looking at extended tags, but just in case.
                    Home: Pi4B-8GB/pCP8.2.x/4TB>LMS 8.3.x>Transporter, Touch, Boom, Radio (all ethernet)
                    Cottage: rPi4B-4GB/pCP8.2.x/4TB>LMS 8.3.x>Touch>Benchmark DAC I, Boom, Radio w/Battery (Radio WIFI)
                    Office: Win11(64)>foobar2000
                    The Wild: rPi3B+/pCP7.x/4TB>LMS 8.1.x>hifiberry Dac+Pro (LMS & Squeezelite)
                    Controllers: iPhone14Pro & iPadAir5 (iPeng), CONTROLLER, Material Skin, or SqueezePlay 7.8 on Win10(64)
                    Files: Ripping: dBpoweramp > FLAC; Post-rip: mp3tag, PerfectTunes, TuneFusion; Streaming: Spotify

                    Comment


                    • #11
                      Originally posted by garym
                      title is song title. track is track number. Be sure and look at "extended tags" in mp3tag, in order to see all tag fields that might exist. I think you probably are looking at extended tags, but just in case.
                      Yes, I was looking at extended tags.

                      The way I work is the following:
                      I have defined a set of - I guess 12 - tags I only use ALBUM;ALBUMARTIST;ARTIST;COMPOSER;COPYRIGHT;GENRE; LYRICIST;MEDIATYPE;PICTURE;TITLE;TRACK;YEAR
                      When I add a new file to the database I use a predefined action that removes all tags except ALBUM;ALBUMARTIST;ARTIST;COMPOSER;COPYRIGHT;GENRE; LYRICIST;MEDIATYPE;PICTURE;TITLE;TRACK;YEAR .
                      So there should no user tag in db (except i made a mistake).

                      When I try to find errors, first thing is to call "extended tags" in mp3tag to see, if there is (for any reason) any other tag than the 12 defined. This wasn't the case.
                      So next step is to see, what tags have different values (mp3tag shows this in one glance). This usually should only be ARTIST;COMPOSER;LYRICIST;TITLE;TRACK .
                      So I double checked is with this album - there are no duets, and I didn't add the composers and lyricsts, so ARTIST was identical and COMPOSER and LYRICST was empty. So TITLE and TRACK were the only tags with different values...

                      But once again:
                      I remember Michael found this bug a few weeks ago and fixed it and I could confess it was fixed. So I hope it is only a "little regression"...

                      Comment


                      • #12
                        Originally posted by frank1969
                        Yes, I was looking at extended tags.

                        The way I work is the following:
                        I have defined a set of - I guess 12 - tags I only use ALBUM;ALBUMARTIST;ARTIST;COMPOSER;COPYRIGHT;GENRE; LYRICIST;MEDIATYPE;PICTURE;TITLE;TRACK;YEAR
                        When I add a new file to the database I use a predefined action that removes all tags except ALBUM;ALBUMARTIST;ARTIST;COMPOSER;COPYRIGHT;GENRE; LYRICIST;MEDIATYPE;PICTURE;TITLE;TRACK;YEAR .
                        So there should no user tag in db (except i made a mistake).

                        When I try to find errors, first thing is to call "extended tags" in mp3tag to see, if there is (for any reason) any other tag than the 12 defined. This wasn't the case.
                        So next step is to see, what tags have different values (mp3tag shows this in one glance). This usually should only be ARTIST;COMPOSER;LYRICIST;TITLE;TRACK .
                        So I double checked is with this album - there are no duets, and I didn't add the composers and lyricsts, so ARTIST was identical and COMPOSER and LYRICST was empty. So TITLE and TRACK were the only tags with different values...

                        But once again:
                        I remember Michael found this bug a few weeks ago and fixed it and I could confess it was fixed. So I hope it is only a "little regression"...
                        It still works for me so the mystery is why it doesn't work for you.

                        Sent from my Pixel 3a using Tapatalk
                        Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
                        Bedroom: Radio
                        Bathroom: Radio

                        Comment


                        • #13
                          An old "friend" is back: Album split in 2albums

                          > - I have an existing album
                          > - I change the title tag (in this case adding "(Radio Edit)" to the
                          > existing track #3 - no other changes, no renaming
                          > - I do a "new & changed"-scan
                          > - I have 2 albums by the same artist with the same name in my db - one
                          > containing only track #3, and one containing tracks #1-2 and #4-12


                          You have changed the _track_ title, and it created a new album? That
                          would definitely be a new issue. Previously we dealt with changing the
                          album titles. A track title change should really not change the album
                          attribution etc. unless editing/saving the metadata at the same time
                          changed other album or artist related data in the file, eg. by replacing
                          some characters in a name.

                          I know, you can't grant me access to your database. But would you be
                          able to export all the track, contributor, album related data for this
                          one particular album from the database? Can you export from SQLite to
                          some text file (with delimiters)? Please no Excel or other format which
                          might have its own ideas about formatting. Just the raw text content.
                          Michael

                          "It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
                          (LMS: Settings/Information)

                          Comment


                          • #14
                            Originally posted by mherger
                            > - I have an existing album
                            > - I change the title tag (in this case adding "(Radio Edit)" to the
                            > existing track #3 - no other changes, no renaming
                            > - I do a "new & changed"-scan
                            > - I have 2 albums by the same artist with the same name in my db - one
                            > containing only track #3, and one containing tracks #1-2 and #4-12


                            You have changed the _track_ title, and it created a new album? That
                            would definitely be a new issue. Previously we dealt with changing the
                            album titles. A track title change should really not change the album
                            attribution etc. unless editing/saving the metadata at the same time
                            changed other album or artist related data in the file, eg. by replacing
                            some characters in a name.

                            I know, you can't grant me access to your database. But would you be
                            able to export all the track, contributor, album related data for this
                            one particular album from the database? Can you export from SQLite to
                            some text file (with delimiters)? Please no Excel or other format which
                            might have its own ideas about formatting. Just the raw text content.
                            Ah, this was the one I thought about

                            I overlooked, it's about album title (eg. though You meant #title tags from an album, not the #album tag) - thought it was about changing (track) titles for I had this issue with track titles often before myself and thought it was fixed.

                            Unfortunately this time I can't "give You anything", for after recognizing the issue I renamed the filename of the changed file and did a rescan, so it is already fixed and I can't see anything in the db.
                            But from now one I will once again keep a copy of library and log-files so I have it "at my hand" if it happens again.

                            Comment


                            • #15
                              Originally posted by frank1969
                              Ah, this was the one I thought about

                              I overlooked, it's about album title (eg. though You meant #title tags from an album, not the #album tag) - thought it was about changing (track) titles for I had this issue with track titles often before myself and thought it was fixed.

                              Unfortunately this time I can't "give You anything", for after recognizing the issue I renamed the filename of the changed file and did a rescan, so it is already fixed and I can't see anything in the db.
                              But from now one I will once again keep a copy of library and log-files so I have it "at my hand" if it happens again.
                              I thought the album title was the album tag. Am I wrong? An album doesn't have tags of its own, the tracks in the album have the album title in the album tag.

                              Sent from my Pixel 3a using Tapatalk
                              Living Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
                              Bedroom: Radio
                              Bathroom: Radio

                              Comment

                              Working...
                              X
                              😀
                              🥰
                              🤢
                              😎
                              😡
                              👍
                              👎