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

Option to preserve file date and time

XMLWordPrintable

      Moved from http://bugs.musicbrainz.org/ticket/5260 and http://bugs.musicbrainz.org/ticket/70

      "From: Charles Brisebois c.brisebois@rogers.com Sent: Saturday, December 31, 2005 5:18 PM To: support@musicbrainz.org Subject: edit file options

      It would be nice if MusicBrainz allowed an option to edit/rename the files WITHOUT affecting the filedate & time. With very large collections, the dates (and years) associated with the files are important. MusicBrainz changes this by default to current date when renaming / editing tags. "

      While some might believe this behavior (preserve file timestamp when changing metadata) incorrect, I agree with the original reporter - I believe it to be correct (or, at least, valid). It depends on what one wishes to be reflected by the file modification time - when "the data payload was last edited", or when "the data payload and/or metadata were last edited". Both are valid IMHO. For example, many(but not all) image library/metadata manipulation programs (Google Picasa, for example) do not change the file timestamps when adding/editing metadata for images.

      There are merits to both methods - however, what this is asking for is not a change in default behavior, but rather just an option to support the preserve-timestamp method that many people use.

      Attached patch by 'fuzz' moved from the other ticket (not verified)

        1. picard-preserve_timestamp(1).patch
          4 kB

          [PICARD-31] Option to preserve file date and time

          Lukáš Lalinský added a comment -

          https://github.com/musicbrainz/picard/commit/8ff30f17b13fe6ba72698c9b50cd708412fffc08

          Lukáš Lalinský added a comment - https://github.com/musicbrainz/picard/commit/8ff30f17b13fe6ba72698c9b50cd708412fffc08

          voiceinsideyou added a comment -

          Unfortunately the codebase has moved on since this patch, so it will likely require some integration work to merge it. I will try and have a look at it in a week or so; but it might miss 1.0 depending on when luks and bitmap decide to release it.

          voiceinsideyou added a comment - Unfortunately the codebase has moved on since this patch, so it will likely require some integration work to merge it. I will try and have a look at it in a week or so; but it might miss 1.0 depending on when luks and bitmap decide to release it.

          DJ Marcus added a comment -

          Hello!

          BTW - I'm the creator of one of the old tickets (5260), and the text above in quotes is from the original (from 2005) ticket by Charles. The rest of the text (not between the quotes, but quoted/indented) is mine. Mentioning that in case there were any questions from people on why some users would like this functionality.

          Please let me know what I can do to help. As far as I know, fuzz's patch resolves it, and it just needs its turn to be included in an upcoming release...right?

          Thanks!

          DJ Marcus added a comment - Hello! BTW - I'm the creator of one of the old tickets (5260), and the text above in quotes is from the original (from 2005) ticket by Charles. The rest of the text (not between the quotes, but quoted/indented) is mine. Mentioning that in case there were any questions from people on why some users would like this functionality. Please let me know what I can do to help. As far as I know, fuzz's patch resolves it, and it just needs its turn to be included in an upcoming release...right? Thanks!

          voiceinsideyou added a comment -

          Patch by fuzz

          voiceinsideyou added a comment - Patch by fuzz

            voiceinsideyou voiceinsideyou
            voiceinsideyou voiceinsideyou
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:

                Version Package
                1.0