• Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Preserve timestamps when updating play count

    Scheduled Pinned Locked Moved
    Feature Suggestions
    2
    3
    232
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      nitro322
      last edited by

      I appreciate the option to save play count to the song's tags. I just noticed that when it writes the tag, though, the file's modification time is updated. That's reasonable default behavior since the file is being modified, but for automatic background operations like that I'd rather it preserve the original modification time. That when when looking at my files I can see the last time they were really modified or changed in some meaningful way, vs. just having been played in Strawberry.

      Please consider adding an option to preserve modification time for play count updates. Minor request to be sure, but would be appreciated.

      Thanks.

      rlkeeneyR 1 Reply Last reply Reply Quote 1
      • rlkeeneyR
        rlkeeney @nitro322
        last edited by

        @nitro322 This would be a problem for backups. When the tag is added the file is modified. If the modified timestamp is preserved my backup will skip the file and if I need to restore the tag is lost.

        N 1 Reply Last reply Reply Quote 0
        • N
          nitro322 @rlkeeney
          last edited by

          @rlkeeney You can backup based on checksums or other attributes aside from modification time. Or use a filesystem like ZFS that allows snapshot-based backups, which makes the whole thing irrelevant.

          But regardless, this is why I asked for an option to preserve modification time, not making it the default / sole behavior. I'm sure there are a lot of users that prefer the behavior as-is, or have workflows based around the current behavior like you described. But having an option to preserve timestamps for those of us that prefer that behavior would be appreciated.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Powered by NodeBB | Contributors