Please forgive me if this is not the appropriate place for this question.
I am running Amarok 2.1.1 (Qt 4.5.2, KDE 4.3.00, MySQL 5.1.37) on Fedora 11. I have a reasonably large collection of MP3s that I've built up over the years, housed on a central server on my network and mounted on my PC via NFS. I can point Amarok to the collection and scan it, and *most* of the files are picked up for the "local collection." However, there are some that do not show at all.
I thought that it might have been the program used to encode the tracks, but I'm finding certain albums which are incomplete - I can see tracks 1-5, for example, but not tracks 6-10, and the entire album was ripped at once. Some entire albums don't show. I thought it might be the tags, perhaps some errant information, but making sure to standardise them doesn't seem to help. No matter what I do, I can't seem to find these tracks.
As is traditional in cases such as this, this used to work in F10, though I can't remember the pertinent Amarok versions. Are there any suggestions? Please let me know if there's more information that I can provide.
Thank you, -Don Levey
On Mon, 14 Sep 2009 14:30:15 -0400, Don wrote:
Please forgive me if this is not the appropriate place for this question.
I am running Amarok 2.1.1 (Qt 4.5.2, KDE 4.3.00, MySQL 5.1.37) on Fedora 11. I have a reasonably large collection of MP3s that I've built up over the years, housed on a central server on my network and mounted on my PC via NFS. I can point Amarok to the collection and scan it, and *most* of the files are picked up for the "local collection." However, there are some that do not show at all.
I thought that it might have been the program used to encode the tracks, but I'm finding certain albums which are incomplete - I can see tracks 1-5, for example, but not tracks 6-10, and the entire album was ripped at once. Some entire albums don't show. I thought it might be the tags, perhaps some errant information, but making sure to standardise them doesn't seem to help. No matter what I do, I can't seem to find these tracks.
As is traditional in cases such as this, this used to work in F10, though I can't remember the pertinent Amarok versions. Are there any suggestions? Please let me know if there's more information that I can provide.
1) Is it reproducible with individual albums? Can you copy all tracks of an affected album to a different location and reproduce the problem there?
2) Have you run amarokcollectionscanner in a terminal yet to see what output it gives for an album that is affected?
Michael Schwendt wrote:
- Is it reproducible with individual albums? Can you copy all tracks
of an affected album to a different location and reproduce the problem there?
Yep - there seems to be something about the tracks, I guess.
- Have you run amarokcollectionscanner in a terminal yet to see
what output it gives for an album that is affected?
Not yet; I'm about to... OK, I ran it. I tested on a directory in which I know I've had problems, (has two subdirectories, each with one album) and I see no error or differences between working and non-working tracks. I then went up one level to the entire collection, but there was too much information. I did see a run of "invalid sample rate" errors but these didn't reference a file.
Does this make sense?
-Don
On Monday 14 September 2009 19:47:46 Don Levey wrote:
Michael Schwendt wrote:
- Is it reproducible with individual albums? Can you copy all tracks
of an affected album to a different location and reproduce the problem there?
Yep - there seems to be something about the tracks, I guess.
- Have you run amarokcollectionscanner in a terminal yet to see
what output it gives for an album that is affected?
Not yet; I'm about to... OK, I ran it. I tested on a directory in which I know I've had problems, (has two subdirectories, each with one album) and I see no error or differences between working and non-working tracks. I then went up one level to the entire collection, but there was too much information. I did see a run of "invalid sample rate" errors but these didn't reference a file.
Does this make sense?
-Don
Don, if this turns out to be complicated, there is a dedicated list (not too high traffic, compared with this one) at https://mail.kde.org/mailman/listinfo/amarok
Anne
I had to install taglib-extras to get some of my files to show up - I'm not sure why. The KDE 4.3 version is definitely much better.
-Bill
Anne Wilson wrote:
On Monday 14 September 2009 19:47:46 Don Levey wrote:
Michael Schwendt wrote:
- Is it reproducible with individual albums? Can you copy all tracks
of an affected album to a different location and reproduce the problem there?
Yep - there seems to be something about the tracks, I guess.
- Have you run amarokcollectionscanner in a terminal yet to see
what output it gives for an album that is affected?
Not yet; I'm about to... OK, I ran it. I tested on a directory in which I know I've had problems, (has two subdirectories, each with one album) and I see no error or differences between working and non-working tracks. I then went up one level to the entire collection, but there was too much information. I did see a run of "invalid sample rate" errors but these didn't reference a file.
Does this make sense?
-Don
Don, if this turns out to be complicated, there is a dedicated list (not too high traffic, compared with this one) at https://mail.kde.org/mailman/listinfo/amarok
This was an excellent suggestion. It turns out that the solution was here: http://mail.kde.org/pipermail/amarok/2009-July/008876.html
By simply 'touch'-ing the affected directories, the collection scanner picked up the missing tracks. All seems OK now, thanks! -Don
On Thursday 17 September 2009 14:05:16 Don Levey wrote:
Anne Wilson wrote:
On Monday 14 September 2009 19:47:46 Don Levey wrote:
Michael Schwendt wrote:
- Is it reproducible with individual albums? Can you copy all tracks
of an affected album to a different location and reproduce the problem there?
Yep - there seems to be something about the tracks, I guess.
- Have you run amarokcollectionscanner in a terminal yet to see
what output it gives for an album that is affected?
Not yet; I'm about to... OK, I ran it. I tested on a directory in which I know I've had problems, (has two subdirectories, each with one album) and I see no error or differences between working and non-working tracks. I then went up one level to the entire collection, but there was too much information. I did see a run of "invalid sample rate" errors but these didn't reference a file.
Does this make sense?
-Don
Don, if this turns out to be complicated, there is a dedicated list (not too high traffic, compared with this one) at https://mail.kde.org/mailman/listinfo/amarok
This was an excellent suggestion. It turns out that the solution was here: http://mail.kde.org/pipermail/amarok/2009-July/008876.html
By simply 'touch'-ing the affected directories, the collection scanner picked up the missing tracks. All seems OK now, thanks!
I've now added that to http://userbase.kde.org/Amarok
Anne
On 09/17/2009 07:09 AM, Rex Dieter wrote:
taglib-extras is a dependency of amarok already
oh, good. I'll chalk it up to one of my yum metadata problems then.
-Bill