It seems that amarok can't play file when '#' is in filepath (in this case # is in directory name).
Once such file is about to be played there is no sound, no progressbar, no error message.
Application does not hang, I can switch to next song in the playlist.
Also ID3 tag of that file can be read and set without problems.

Below some tech details:

Code: Select all

$ amarok -v
Qt: 4.5.2
KDE: 4.3.2 (KDE 4.3.2)
Amarok: 2.2.0


Code: Select all

$ uname -srvm
Linux 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:05:01 UTC 2009 x86_64


It's generally a bad idea to have special chars in path/filemnames. Simply avoid them, especially chars that (could) have special meaning in Linux.
I replace them strictly and have no problems with my collection.
Correct tagging and naming of tracks could avoid a lot of topics in this forum.

m0nk

Dieter Schroeder wrote:It's generally a bad idea to have special chars in path/filemnames. Simply avoid them, especially chars that (could) have special meaning in Linux.
I replace them strictly and have no problems with my collection.
Correct tagging and naming of tracks could avoid a lot of topics in this forum.

m0nk

Name is valid so it's a bug. About correct tagging, at this time, I'm not sure was correct and was incorrect and Amarok has, at least, a bug with encoding detection reading ID3 tags.

If Amarok don't support some kind of files names there are two solutions:
1) Document the behaviour and raise a warning when a file with no propher name was detected.
2) Support the file.

The third alternative, take care manually that your file names are valid to Amarok, is not an option.

That's an old Phonon bug, it's actually already fixed in Phonon SVN.


See here:

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

I'm not talking about tags.
I'm not talking about bugs, althought this is none (in Amarok).
I just stated, that bad naming of files can cause problems, not only in Amarok, but generally.
So I can't see, why this couldn't be an option.

m0nk

Dieter Schroeder wrote:I'm not talking about tags.
I'm not talking about bugs, althought this is none (in Amarok).
I just stated, that bad naming of files can cause problems, not only in Amarok, but generally.
So I can't see, why this couldn't be an option.

m0nk

You are right about tags. I think that I read chars but understand tags. My English is really bad and sometimes misunderstood text. So sorry, my comment about tags was totally off-topic.

About files names, if the simple explanation that system avoid that file name and Amarok can't (really Phonon as Mark explain to us) is not valid for you, I don't have enough English skills to explain you the difference between a bad file name and a good file name.