I think really strange.

I have two directories where i get my collection.

They are my Local Disc partitioned, one is directory "/home/daniel/Música/"
Its in

Code: Select all

/dev/sda6     ext3     25G   22G  2,2G  91% /home

And another partition is "/pub/music"

Code: Select all

/dev/sda8      jfs   6,1G  5,0G  1,2G  82% /pub

Dont matter what kind of disc i make changes, only new tags or tags updated, amarok dont work.

When i add new tracks amarok recognize, if i rename file, amarok knows, because the filename are show correct.

I use EasyTag to try modify mp3Tags without sucess.
And when i use amarok to modify Tags, the changes are recognize on Kid3 or EasyTag ... 0o

I follow your steps and the same happens to me. I don't detect this problem before because I always move music outside my library before do changes with another program.

When I finish with my changes I moved again to the library and Amarok detects changes but, without moving files, Amarok don't detect external changes. But sometimes don't works on first try.

I don't know if could be difficult add a tag verification on playing music because Amarok seems to use db for all data displayed and databases sometimes fails.

I don't know if this helps but I'm using a symlink ~/music linked to /storage/storage/music

Ignacio can you say how is the $amarok --version do you have?

yermandu wrote:Ignacio can you say how is the $amarok --version do you have?

I'm using current git version.

Qt: 4.5.2
KDE: 4.3.1 (KDE 4.3.1) "release 163"
Amarok: 2.2-GIT

Great!, one of my most hated Amarok bugs is now fixed , this little **** corrupt my db so many times until I located the problem.

* Fixed issue where files or folders with the same name but different case sensitivity were not scanned and/or retained. (BR 197384)

http://bugs.kde.org/show_bug.cgi?id=197384

I put here because could be related to this discussion.

I've tested the rescan issue by retagging artist and/or title of some tracks in my collection. I thought first, that Amarok really doesn't do a rescan, but it started shortly after.
Renamed tracks seem to be recognized faster, but this could be subjective.
In general: it works.
I really don't know, why it doesn't work in Ignacio's and yermandu's setup.
And they seem to be the only one, who have this problem.
Sorry.

m0nk

Well, another possibility is that the bug is external to Amarok and it is related to the file changes detection method.

How Amarok know that files are changed externally?

Have you read my former posts in this thread?

m0nk

Dieter Schroeder wrote:Have you read my former posts in this thread?

m0nk

Do you mean "Amarok 2 rescans, when the timestamp of the folder, containing the tracks with added/edited tags, gets updated.". Yes, I read it, but this don't explain witch method is using Amarok to detect this change. It is reading all folders in db and check timestamps?, there is a system event?, Amarok calls a running daemon?...

I think that I not expressed well , I'm sure is clear that english is not my language.

Amarok uses dbus methods to detect changes in the filesystem. If they are relevant, Amarok rescans.
Btw. Tried 2.2-beta1, which is out now.

m0nk

Dieter Schroeder wrote:Amarok uses dbus methods to detect changes in the filesystem. If they are relevant, Amarok rescans.
Btw. Tried 2.2-beta1, which is out now.

m0nk

Have you read I'm running git version. I thought that git version is newer than beta1 version. I'm wrong?.

Correct, GIT is newer (will become beta2).
My fault, sorry.

m0nk

Dieter Schroeder wrote:I've tested the rescan issue by retagging artist and/or title of some tracks in my collection. I thought first, that Amarok really doesn't do a rescan, but it started shortly after.
Renamed tracks seem to be recognized faster, but this could be subjective.
In general: it works.
I really don't know, why it doesn't work in Ignacio's and yermandu's setup.
And they seem to be the only one, who have this problem.
Sorry.

m0nk

Well Dieter, you test in your computer and retagging works fines, ...
Could someone also test retagging working? For us leave a question.

Maybe the issue can be in us computer or database and not with amarok.

Well, at least for my case, I catch the bug and seems to be a db query cache problem or something similar. I'm using current git, updated and compiled before doing the test.

I'm using EasyTag for changing tags because this program has "Update modification time of parent directory of the file (recommended when using Amarok)" option and Kid3 don't have a similar option.

The test was doing using the next song (all with english characters to avoid encoding bugs):
~/music/mp3/kpop/After School/New School Girl/02 AH.mp3
Artist: After School
Title: AH
Album: New School Girl

I follow the next steps.
1) Run Amarok.
2) Execute EasyTag and select file.
3) Rename Title from "AH" to "AH AH".
4) Save changes.
5) Wait for Amarok detects changes.
6) Amarok scans and...
7) Nothing happens, title is not changed. If I added mp3 to playlist and edit properties Amarok displays old title.

And now the funny thing
9) Close Amarok.
10) Run Amarok again.
11) Voila, now title displays "AH AH" .

So, conclusion is that db was updated but query result was not. I this problem is related to MySQL query cache or a coded query optimization is beyond my knowledge.

Maybe there's a little misunderstanding. The tags in playlists, the album applet etc., anything except the collection browser don't get an update after a rescan.
So if you have the track "AH" from "After School" in your playlist, it will remain "AH" even after the scan until you remove it and add it as "AH AH" from the collection browser.
If that is clear, maybe you can tell me the version of your mysql and libmysqlclient rpms.


m0nk