Greetings, fellow Amarok users, my first post here is a plea for help!

I was using a shared MySQL database for 2 installations of Amarok 1.4 and it was working perfectly. I've recently upgraded one installation to Amarok 2, and the new version of Amarok does not work as expected.

In the collection, I can see the correct artists and albums, but expanding an album will not show the tracks. I can't add tracks from the collection to the playlist, I can only populate the playlist via the file browser. I also can't edit track metadata via the collection browser.

Searches in the collection show the correct combination of artists and albums, but again no tracks.

Amarok's internal database functions correctly, and I exported my MySQL DB to sqlite and imported that in order to use my library now.

This appears to be a problem with how Amarok 2 is accessing a MySQL DB created with Amarok 1 in mind, help?

media-sound/amarok-2.2.2.90 USE="embedded ipod opengl (-aqua) -cdda -daap -debug (-kdeenablefinal) -lastfm -mp3tunes -mtp -semantic-desktop"
dev-db/mysql-5.0.84-r1 USE="berkdb community embedded perl ssl -big-tables -cluster -debug -extraengine -latin1 -max-idx-128 -minimal -profiling (-selinux) -static -test"

a rather slow forum we have here....
any suggestions for other locations to post this question?

ascendant512 wrote:a rather slow forum we have here....
any suggestions for other locations to post this question?

We are addicted to this here, sorry:

http://ronpbutler.com/img/examples/slurm.png

markey wrote:

ascendant512 wrote:a rather slow forum we have here....
any suggestions for other locations to post this question?

We are addicted to this here, sorry:

http://ronpbutler.com/img/examples/slurm.png

ah yes
oh well

Did you try doing a full collection rescan (Settings menu -> Configure Amarok -> Collection), then restart Amarok?

Mamarok wrote:Did you try doing a full collection rescan (Settings menu -> Configure Amarok -> Collection), then restart Amarok?

Thanks for the reply!
I have tried this, and it had no effect. I noticed that it rescanned the collection fairly quickly, though this just may be an effect of Amarok 2, and not a symptom.

Like I said, the library shows the correct number of tracks and the right artists and albums.

I'm having the same problem. Wonder if its Gentoo related?

rzrgenesys187 wrote:I'm having the same problem. Wonder if its Gentoo related?

Are you using MySQL and all that? Maybe we'll get some attention! Post your versions of stuff please.

I'm using Kubuntu 9.1 and I have the same problem.
When I upgraded to Kubuntu 9.1 and Amarok2, I inadvertently entered the credentials for my Amarok 1.4 mysql database and Am2 promptly wiped it out. I then did a rescan in which it entered the info for my collection, I believe it got that right because the song count seemed accurate. I thought, "wow, they fixed it!" Because earlier versions of Amarok 2 used to choke before it could complete a scan. (I have a gazillion tracks)

Now then, Just as Ascendant posted, I can see the collection Artist and Album but not the individual songs. If I right click on an album and try to add to playlist, nothing happens. I can however open existing playlists and streaming audio. I can surf files and add songs to the playlist that way.

If I do a search, the search will return a correct list of results, but there again, Only the artist and album are listed. Expanding the album does nothing, cannot see the songs nor add to the playlist by right clicking or dragging.

This is worthless. I might have to go back to recompiling source for Amarok 1.4 again. I can't explain without expletives how frustrating it is to have the improved product be so inferior to the old.

I will make a last ditch effort of completely dropping all the database tables and let it recreate the database and do the re-scan of the collection. Hopefully it will be done by tomorrow and I will post back the results.

I'm not sure why this is happening for you, but one thing you can do, is quit Amarok (control Q). Then in the console, run

Code: Select all

amarokcollectionscanner

Once it has finished, open Amarok and let it do its thing -- likely another brief scan. Then quit Amarok *again*. Finally, open it up and you should have full access to your collection once more. If not, try restarting KDE.

Hope this helps,

Valorie

Thanks Valorie, I did that initially, but this time on a bit deeper level

Okay, I figured it out. At least in my case. I dropped all the tables in my database and let am2 recreate new ones. Initially, I noticed that I dropped 36 tables and when Am2 recreated it's tables, it only created 25. Hmmm. Further investigation shows that the extra tables were left-overs from Am1.4

Am2 had new tables with slightly different names along side the old ones. One of the exceptions being the tracks table which holds all of the actual track names. I suspect that Am2 was ramming new data into the old table and there was some slight layout difference. I've got old sql dumps and I can figure that out later.

I followed that up by doing a complete full scan

Bottom line is that now I've got track names showing up and can add them to the playlist. I restarted Amarok and it still works. Yay.

Hi, Sparken, thanks for your input into solving this problem!

I'm trying to see if I can manage to do this without losing my song ratings. I do seem to have a amarok.tracks table. Here is my table list, can you post yours for comparison?

Code: Select all

Current database: amarok

+----------------------+
| Tables_in_amarok     |
+----------------------+
| admin                |
| album                |
| albums               |
| amazon               |
| artist               |
| artists              |
| bookmark_groups      |
| bookmarks            |
| composer             |
| composers            |
| devices              |
| directories          |
| embed                |
| genre                |
| genres               |
| images               |
| labels               |
| lyrics               |
| playlist_groups      |
| playlist_tracks      |
| playlists            |
| podcastchannels      |
| podcastepisodes      |
| podcastfolders       |
| related_artists      |
| statistics           |
| statistics_permanent |
| statistics_tag       |
| tags                 |
| tags_labels          |
| tracks               |
| uniqueid             |
| urls                 |
| urls_labels          |
| year                 |
| years                |
+----------------------+
36 rows in set (0.18 sec)

You Bet! At least you are thinking ahead. I completely forgot about my ratings! Grrrr..

Here are the tables in the new database:

Code: Select all

+----------------------+
| Tables_in_amarok     |
+----------------------+
| admin                |
| albums               |
| amazon               |
| artists              |
| bookmark_groups      |
| bookmarks            |
| composers            |
| devices              |
| directories          |
| genres               |
| images               |
| labels               |
| lyrics               |
| playlist_groups      |
| playlist_tracks      |
| playlists            |
| podcastchannels      |
| podcastepisodes      |
| statistics           |
| statistics_permanent |
| statistics_tag       |
| tracks               |
| urls                 |
| urls_labels          |
| years                |
+----------------------+
25 rows in set (0.00 sec)

Before I wiped it, I had the same listing as you do now. The extra obsolete tables in and of themselves should be a non-issue. But as you may have noticed, Amarok 2 uses the same tracks table which is where the problem probably exists. I think I looked at the tracks table and didn't see anything odd, but I just deleted it anyway. SHould have saved a description so I could compare the broken to the working. But you can do that since your table is still intact. Here is a description of the new and working table:

Code: Select all

describe tracks;
+---------------+--------------+------+-----+---------+----------------+
| Field         | Type         | Null | Key | Default | Extra          |
+---------------+--------------+------+-----+---------+----------------+
| id            | int(11)      | NO   | PRI | NULL    | auto_increment |
| url           | int(11)      | YES  | UNI | NULL    |                |
| artist        | int(11)      | YES  | MUL | NULL    |                |
| album         | int(11)      | YES  | MUL | NULL    |                |
| genre         | int(11)      | YES  | MUL | NULL    |                |
| composer      | int(11)      | YES  | MUL | NULL    |                |
| year          | int(11)      | YES  | MUL | NULL    |                |
| title         | varchar(255) | YES  | MUL | NULL    |                |
| comment       | text         | YES  |     | NULL    |                |
| tracknumber   | int(11)      | YES  |     | NULL    |                |
| discnumber    | int(11)      | YES  | MUL | NULL    |                |
| bitrate       | int(11)      | YES  | MUL | NULL    |                |
| length        | int(11)      | YES  | MUL | NULL    |                |
| samplerate    | int(11)      | YES  |     | NULL    |                |
| filesize      | int(11)      | YES  | MUL | NULL    |                |
| filetype      | int(11)      | YES  |     | NULL    |                |
| bpm           | float        | YES  |     | NULL    |                |
| createdate    | int(11)      | YES  | MUL | NULL    |                |
| modifydate    | int(11)      | YES  |     | NULL    |                |
| albumgain     | float        | YES  |     | NULL    |                |
| albumpeakgain | float        | YES  |     | NULL    |                |
| trackgain     | float        | YES  |     | NULL    |                |
| trackpeakgain | float        | YES  |     | NULL    |                |
+---------------+--------------+------+-----+---------+----------------+
23 rows in set (0.00 sec)


If you save the data from your statistics table and tracks table, you should be able to update the new database with your saved statistics data. Shouldn't be too complicated with mysql. I'm no sql expert but I think I could figure the query out if put my mind to it.

Let me know if I can be of further assistance and also post back on what you find.

EDIT: whoops
I noticed that my tracks description is identical to yours. I know nearly nothing about mysql, but it doesn't seem all that difficult.
Can you post your playlist_tracks description? That's the only other table that looks like it affects the current playlist tracks. Here is the description of mine for reference:

Code: Select all

describe playlist_tracks;
+-------------+---------------+------+-----+---------+----------------+
| Field       | Type          | Null | Key | Default | Extra          |
+-------------+---------------+------+-----+---------+----------------+
| id          | int(11)       | NO   | PRI | NULL    | auto_increment |
| playlist_id | int(11)       | YES  | MUL | NULL    |                |
| track_num   | int(11)       | YES  |     | NULL    |                |
| url         | varchar(1000) | YES  |     | NULL    |                |
| title       | varchar(255)  | YES  |     | NULL    |                |
| album       | varchar(255)  | YES  |     | NULL    |                |
| artist      | varchar(255)  | YES  |     | NULL    |                |
| length      | int(11)       | YES  |     | NULL    |                |
| uniqueid    | varchar(128)  | YES  | MUL | NULL    |                |
+-------------+---------------+------+-----+---------+----------------+
9 rows in set (0.00 sec)

Looks the same to me. Here is mine.

Code: Select all

describe playlist_tracks;
+-------------+---------------+------+-----+---------+----------------+
| Field       | Type          | Null | Key | Default | Extra          |
+-------------+---------------+------+-----+---------+----------------+
| id          | int(11)       | NO   | PRI | NULL    | auto_increment |
| playlist_id | int(11)       | YES  | MUL | NULL    |                |
| track_num   | int(11)       | YES  |     | NULL    |                |
| url         | varchar(1000) | YES  |     | NULL    |                |
| title       | varchar(255)  | YES  |     | NULL    |                |
| album       | varchar(255)  | YES  |     | NULL    |                |
| artist      | varchar(255)  | YES  |     | NULL    |                |
| length      | int(11)       | YES  |     | NULL    |                |
| uniqueid    | varchar(128)  | YES  | MUL | NULL    |                |
+-------------+---------------+------+-----+---------+----------------+
9 rows in set (0.00 sec)                                               


I seem to recall looking at the tables and not being able to identify what specifically was causing the problem. One thing you could do is just create another database with a new name and configure amarok2 to use that and let it rescan the collection to the new db. I would be willing to bet it will work properly with the new db. Then you could just compare table to table until you find the needle in the haystack.

I suppose since Amarok is an open source project, we could dig around in the code and locate the actual query that Am2 is using to cull the track data for the left pane when local collection is selected. That would probably cast some light. Maybe it isn't the format of the tables, maybe Am2 kept some of the old data (like the track URL ) and that data no longer links up with newly generated URL data in other tables. Arg! I wish I had backed up my DB, now.