Amarok 2 transition from 1.x

Rich rich at hq.vsaa.lv
Tue Apr 1 13:47:19 UTC 2008


On 2008.04.01. 14:33, Jeff Mitchell wrote:
> Some comments:
> 
>> Sometimes when updating from 1.x to 1.x+1 the collections got wiped out.
> 
> Statistics should have been saved, though.  There was actually a bug in 
> versions prior to somewhere mid-1.4 (not sure of the exact version) 
> where the entire database could be wiped if you were using MySQL -- not 
> just on upgrade, but at any time that you opened Amarok.  You might have 
> run into that.
> 
>> Or certain scripts can bugger up your collection (mp3fixer does this for 
>> me, after fixing a file it rescans the collection and somehow it loses 
>> 20% of the tracks; how is this allowed to happen?).

last i tried mp3fixer, it did something similar to my tracks. markey 
said it is unsupported & outdated, so, unless somebody fixed it... don't 
use it.
given that in 1.4 branch last change to it is at 2007-06-11, i'd avoid 
that script.

> No idea, since I've never used mp3fixer.  What do you mean by "loses" 
> tracks?  They don't show up in the collection anymore?  You lose ratings 
> for those tracks?
...
-- 
  Rich



More information about the Amarok mailing list