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

List:       amarok-bugs-dist
Subject:    [amarok] [Bug 327991] Album Artist tag not being read, Artist used instead, possibly ID3v2.4 failure
From:       Matěj Laitl <matej () laitl ! cz>
Date:       2014-05-12 20:58:05
Message-ID: bug-327991-71684-tAjcwJaOKU () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=327991

Matěj Laitl <matej@laitl.cz> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #8 from Matěj Laitl <matej@laitl.cz> ---
(In reply to comment #7)
> I have version 2.8 and the menu reads "Tools->Update Collection".  The
> settings dialog has "Full rescan".  Neither was apparently sufficient to
> correct the problem I originally described with the tags.  I had to move the
> MP3s out of the directory, do an update, and then move them back and update
> again for Amarok to discover the updated tags.  I did confirm that the
> modification time stamps on the MP3s were changing, so it's not that I've
> made updates while leaving the file time the same.

Amarok only watches directory mtime changes, not file mtime changes (as
watching tens of thousands of files is not feasible in Linux). Sane tools that
edit the mp3s save the changes using temporary files, which updates directory
mtimes. See
http://userbase.kde.org/Amarok/Manual/Organization/CollectionScanning

> In particular, it seems to me to be bad form that "Edit Track Details" loads
> cached values rather than inspecting the actual file and updating the
> database.  This would seem like rescannig the file here would be a good
> defensive measure against undetected changes that comes at little or no
> expense (provided that you haven't selected your entire collection for
> editing).

I would be opposed to this, this would be just an ugly work-around (with
side-effects), original problem (if any) needs to be solved.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
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]