[prev in list] [next in list] [prev in thread] [next in thread] 

List:       amarok-bugs-dist
Subject:    [Bug 147369] New: adding replaygain tags makes music appear as
From:       Justin Sheckler <self () jaykayess ! com>
Date:       2007-06-29 17:24:19
Message-ID: 20070629192418.147369.self () jaykayess ! com
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147369         
           Summary: adding replaygain tags makes music appear as newly-added
           Product: amarok
           Version: 1.4.6
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: amarok-bugs-dist kde org
        ReportedBy: self jaykayess com


Version:           1.4.6 (using KDE 3.5.6, Kubuntu (feisty) 4:3.5.6-0ubuntu14)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.20-16-generic

Actually, any change to the modification time for a track causes it to show up in the \
collection as newly-added, even if the track's been in your collection for months.  \
It's just that replaygain tagging is the most common and annoying example.  If I scan \
my entire collection with replaygain, suddenly I lose the ability to sort my music by \
newest.

I understand why this happens technically, it just doesn't make sense to me.  It \
seems like Amarok should order the tracks in your collection by the time the file \
first appeared; not the last time it was modified.  Just because an external program \
changes the tags on a track that already exists, it doesn't mean that the music is \
brand-new. _______________________________________________
Amarok-bugs-dist mailing list
Amarok-bugs-dist@kde.org
https://mail.kde.org/mailman/listinfo/amarok-bugs-dist


[prev in list] [next in list] [prev in thread] [next in thread]