Removing deleted playlists from database

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • frank1969
    Senior Member
    • Jun 2009
    • 797

    Removing deleted playlists from database

    > I deleted them in tracks-table (all) and started a new&changed-scan -
    > and they were imported again (and only once imported )) )


    So you're good again?

    Next time you encounter a problem please keep a copy of scanner.log and
    library.db for further investigation. How large would the latter be in
    your case?
  • frank1969
    Senior Member
    • Jun 2009
    • 797

    #2
    Old playlists are not removed when playlist directory is changed.

    EDIT:
    I obviously solved "my" problem by going into "tracks" table and deleting all entrys from D:\Playlist and D:\Playlist2.

    IMHO it stays an issue:
    When the playlist-directory in LMS is changed, the playlists from the "old" directory stay in (... and are to be found as url/files in the tracks table of library.db)

    ******************

    Is there any "easy" way to get rid of ALL playlists (and import them new).

    There was an error during my last re-scan so it couldn't see all playlists (only 60 of 1.259 - my fault).
    Running a new&changed" said it found 1.259 playlists (that's right) but didn't import any one of the missing.

    1. I tried to change the playlist-directory in LMS to an "empty" directory (D:\Test - including one "fake playlist" with one track) and do a "new&changed"-scan - hoping scanner will remove all playlists but the "fake one". It didn't. It added the fake one but removed nothing.

    2. I copyed all playlists to another dir than before ("D:\Playlists2" - btw it's another HDD than my music library) and linked this in LMS - after another new&changed it imported the missing ones (1.099) - but the existing ones (60) were "double" in (from "D:\Playlist" and "D:\Playlist2").

    3. I deleted all duplicates manually, linked LMS back to "D:\Playlist" - and now the duplicates (60) came back.

    I wonder if this behaviour has anything to do with those changes made to tracks url (for I learned playlists are "normal" tracks in "tracks" table)?

    So however: the only way I see is to "clean up" all playlists from LMS (and not by a full rescan - it takes a day ))) )

    Thanks for Your help!
    (If You think is caused by the changes to scanner, please give me a note, I start a bug report )
    Last edited by frank1969; 2022-02-04, 15:29.

    Comment

    • mherger
      Babelfish's Best Boy
      • Apr 2005
      • 24640

      #3
      Removing deleted playlists from database

      > Is there any "easy" way to get rid of ALL playlists (and import them
      > new).


      I think it should just work... easy as that :-).

      > There was an error during my last re-scan so it couldn't see all
      > playlists (only 60 of 1.259 - my fault).
      > Running a new&changed" said it found 1.259 playlists (that's right) but
      > didn't import any one of the missing.


      Unfortunately you didn't keep the log file of this scan, did you? Did
      you see any sign of progress, while it was processing the newly
      discovered playlists? Or did it discover, but not process them?

      I believe you are familiar with SQL? Did you check whether there was any
      sign of those playlists in the tracks table?

      > So however: the only way I see is to "clean up" all playlists from LMS
      > (and not by a full rescan - it takes a day ))) )


      I wonder whether deleting them in LMS would be any faster :-).

      Michael

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

      Comment

      • frank1969
        Senior Member
        • Jun 2009
        • 797

        #4
        Originally posted by mherger

        Unfortunately you didn't keep the log file of this scan, did you? Did
        you see any sign of progress, while it was processing the newly
        discovered playlists? Or did it discover, but not process them?
        I did not save them but I looked into them - scanner discovered them but did not process them in anyway (at least according to the logfiles)

        Originally posted by mherger

        I believe you are familiar with SQL? Did you check whether there was any
        sign of those playlists in the tracks table?
        Yes, I checked - they have been in playlist table with d:\playlist\...m3u resp. d:\playlist2\...m3u

        Originally posted by mherger

        > So however: the only way I see is to "clean up" all playlists from LMS
        > (and not by a full rescan - it takes a day ))) )
        I deleted them in tracks-table (all) and started a new&changed-scan - and they were imported again (and only once imported )) )

        Comment

        • frank1969
          Senior Member
          • Jun 2009
          • 797

          #5
          Originally posted by mherger


          So you're good again?

          Next time you encounter a problem please keep a copy of scanner.log and
          library.db for further investigation. How large would the latter be in
          your case?>
          Yes, everything is fine again - just wanna give You a note though if You know about these problem - it seemed to me, scanner only scanned the new dir (playlist2) and didn't scan the old one (playlist) for it wasn't linked to lms anymore?

          library.db is about 2,5 GB (with a lot of personal comments and annotations and chart positions... ;-))

          Comment

          Working...