![]() Registered Member ![]()
|
Hi,
I had some big problems to build my collection since my update from Amarok 1.3.* to >1.4.2,1.4.3 and recent SVN). The behaviour of the Amarok collection builder was similar to the one described in these threads :
The story I have a 6000 song collections, on a local hard drive in (ext3). Amarok was working fine until I upgrade to 1.4.3, then, after having removed my .kde/share/config/amarok and .kde/share/apps/amarok, amarok was unable to build my collection. When I tried to isolate the problem on a subset of my mp3, It reported the following errors:
So I decided to experiement with this Arno song file with 18 errors, I tried to build up a collection only with this file, it worked, then I built up a collection with thousands of copies of this file and it worked also. So I switched to the first songs reported as errors and I discovers that these songs have chinese file names, especially one, the home/longwei/debug_amarok/selected/d/daolang/2002/04-��ķë�ϯ-2002��ĵ����ѩ-���.ogg which title cannot even be modified manually by konqueror. Like previously I built up a collection only with this file, amarok was not able to build the collection and chrashed. I changed the names of the file then it worked. My conclusion is that my amarok collection builder was crashing on some specific annoying files with strange caracters in the filename. The problem then was to isolate the files and this was made impossible by the fact that when this error occurs the collection reports errors on other files which are not problematic, their only problem is to have french accents.
Consequently in order to identify the songs wich file name cause problem, I had to browse manually my entire collection, changed the file names of all the mp3 with exotic characters (french, accents, chinese, korean, ....). I was finally able to build up my collection. I hope this helps, If some amarok developpers are interested in the files which cause problem. There might be some other solutions linked to charset of filename like in this report bug : http://bugs.kde.org/show_bug.cgi?id=135243 (Collection scan aborts due to too many errors on smb-shares). |
Registered users: Bing [Bot], Google [Bot], kde-naveen, Sogou [Bot], Yahoo [Bot]