Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-2019

Saving tracks to SMB share on Windows 10 results in ever more nested folders

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Normal Normal
    • 2.5.3
    • None
    • None
    • None
    • Windows 10 locally, Synology shared remotely

      I just did a fresh install of Picard on Windows 10.  I set up "Move files when saving", with the destination directory "\\synology\music", with a nearly-stock renaming script (which I've been using on my Macbook just fine):

      ```

      $if($eq(%compilation%,1),Compilations,$if2(%albumartist%,%artist%,Unknown Artist))/

      $if(%album%,%album%/,)

      $if($gt(%totaldiscs%,1),%discnumber%-,)$if($and(%albumartist%,%tracknumber%),$num(%tracknumber%,2) ,)$if(%_multiartist%,%artist% - ,)%title%
      ```

      If I drag and drop an album into Picard (one that's already got all the correct metadata) from, say, \\synology\music\Artist\Album, then I try to save those tracks, it will move all the files in the album to \\synology\music\Artist\Album\Artist\Album.  If I save it again, it will move it to \\synology\music\Artist\Album\Artist\Album\Artist\Album, etc...

      If anyone else runs into this, as a workaround you can go to you server in the Windows File Explorer, right click on the share an pick "Map Network Drive..." to assign a drive letter to the network share (e.g. I assigned "X:" to \\synology\music") and then you can use this as your target directory in File Renaming and it will work correctly.

            outsidecontext Philipp Wolfer
            jwalton jwalton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

                Version Package
                2.5.3