People changing things that don’t need changing
Recently, Amarok decided to change the way they store URL’s in it’s database, meaning that it’s now a PITA to try and get a song to play, as for some reason - they all now start with ./ - instead of just /.
So now I have to go hacking away to make katapult use the proper URLs. This is going to be even more fun as it will also need to detect the version of amarok. - Yay!
Lets just hope KURL::isRelativeURL (const QString &_url) works well enough to determine the type of path amarok is returning 
September 15th, 2006 at 6:14 pm
Um, dynamic collection? Hello McFly?
September 15th, 2006 at 6:43 pm
Yes, I was wondering why Katapult was starting the wrong song
I do understand your frustration, and I hope you won’t be discouraged from continued development; Katapult is a favorite of mine, and I’ll patiently wait for the fix. Thanks for your work.
September 15th, 2006 at 10:15 pm
The only people who decide what needs changing in Amarok’s database are the Amarok devs. If you want to use Amarok’s database, you have to use the schema we decided on. And there was a good reason to change the way URL’s are stored, Dynamic Collection.
We are happy to help you solve your problem. Just ask us what we changed and what you have to do to get Katapult running again by e-mail or in #amarok. But please don’t expect us to remove Dynamic Collection just because it breaks Katapult.
September 15th, 2006 at 10:33 pm
This change was not for no reason: since 1.4.2, Amarok has a feature called ‘dynamic collection’. This means that file systems may be added and removed to Amarok’s collection without a full collection rescan. However, e.g. USB connected drives might not be mounted at the same mount point each time they are connected. Thus, only the path relative to the file system root is stored in the collection, not an absolute path.
September 16th, 2006 at 12:31 am
Be careful when you do this, you could get yourself into some more trouble :).
You need to prepend the device path which can be determined from the device id in the tags table. For example, you might have two paths which look pretty similar:
./music/file1.mp3
./music/file2.mp3
However, if the device ids are different, it means they are stored somewhere completely different: eg:
/home/music/file1.mp3
/media/usb/music/file2.mp3
September 20th, 2006 at 10:28 am
I have to agree with you, this seems like a stupid decision and change. Amarok lacks quality control.