error playing tracks from searches

[adrian]

I have one song with artist tag "Newton, Juice". If I navigate to the song I can play it without trouble.

But if I use search and type in "Juice" then a folder labeled "Juice Newton" pops up. If I select this folder I get "Error (click for info)" When I click, I get a 4 line error text in XML.

It appears the error is "No such object". If you need the full text I'll extract it somehow.

I tried searching for "Anderson" which produces many results. Some results are tracks. If I select the tracks they play. Other results are folders. If I select the folders I get the error again. I don't understand what distinguishes these two cases from each other.

This is using 8player from an iPad. I tried the same thing from BubbleUPnP under Android. This software gave me 3 choices when I did the search, track, artist or album. I selected the artist folder and got the same error, which this software presents without XML tags as simply "no such object". I went back and tried the two other choices and they both worked---no error. So I only get the error when I select the artist folder.

Code:

>props
alphaGroup=all=125
.autoUpdate=true
contentDir=/volume1/music/music
displayName=MinimServer[echidna]
http.port=9790
indexTags=Artist, Genre, Composer
.logFile=minimserver.log
.logLevel=info
mergeFolderAlbums=false
ohnet.debug=Default
ohnet.port=9791
showExtras=true
startupScan=true
tagCustom=Composer.displayRole={author,artist}
tagFormat=Artist.displayFormat={$composer^^: $artist}
tagOptions=Album.sortTags={Album, Artist}, all.ignore.sort={The,A,An,"}, Artist.reverseName.index.display, AlbumArtist.reverseName.index.display
.updateReminder=1

[simoncn]

When you get the "no such object" message on your control point, there should also be a warning message in the MinimServer log. What does this message say?

[adrian]

(20-05-2016 12:07)simoncn Wrote:  When you get the "no such object" message on your control point, there should also be a warning message in the MinimServer log. What does this message say?

MinimServer: 0$:artists$9374-3 isn't a valid object

I also noticed that the log file has 4879 lines that say "Warning: sort value conflict for filter <artist>" for five different values of <artist>. There are only a total of 4983 lines in the file, so most of the file consists of these messages. This doesn't seem related to the problem I posted about, but I wonder if it indicates something I should correct, and if so, how I figure out what to change.

Looking at other lines in the log I see other lines similar to the above, presumably due to the "no such object" problem when I experienced a couple days ago:

MinimServer: 0$:artists$9417-3 isn't a valid object
MinimServer: 0$:artists$9374-3 isn't a valid object
MinimServer: 0$:artists$9379-3 isn't a valid object
MinimServer: 0$:artists$3905-3 isn't a valid object
MinimServer: 0$:artists$6032-3 isn't a valid object
MinimServer: 0$:artists$3905-3 isn't a valid object
MinimServer: 0$:artists$9379-3 isn't a valid object
MinimServer: 0$:artists$9374-3 isn't a valid object

I also determined that the invalid object code seems to come up the same when I do the same search. (So it doesn't appear to be varying randomly or anything like that.)

[simoncn]

I think it is quite likely that the sort value conflict messages could be related to the "no such object" problem. If any of the artists in the sort value conflict messages is the same as the artist that is giving you "no such object", then it is almost certain that these are related.

Please zip your log file and attach it to a post here. This will give me a more complete picture of what is happening. Many thanks!

[adrian]

(20-05-2016 22:16)simoncn Wrote:  I think it is quite likely that the sort value conflict messages could be related to the "no such object" problem. If any of the artists in the sort value conflict messages is the same as the artist that is giving you "no such object", then it is almost certain that these are related.

Please zip your log file and attach it to a post here. This will give me a more complete picture of what is happening. Many thanks!

The sort value conflict messages are only for 5 artists, and not the ones that I searched for and found the "no such object" problem. The "no such object" problem seems to happen with lots of artists, though I can't tell what distinguishes one where it happens from one where it doesn't.

[simoncn]

(21-05-2016 14:18)adrian Wrote:  The sort value conflict messages are only for 5 artists, and not the ones that I searched for and found the "no such object" problem. The "no such object" problem seems to happen with lots of artists, though I can't tell what distinguishes one where it happens from one where it doesn't.

Thanks for this log. You are correct that the "no such object" problem isn't related to the sort value conflicts. It is related to the Artist.reverseName.index setting in tagOptions. The artists that produce this error are the artists with reversed index names.

The problem is fixed now in update 86. This update also contains a change to the "sort value conflict" message to provide more information about the conflicting sort values.

[adrian]

(21-05-2016 21:44)simoncn Wrote:  Thanks for this log. You are correct that the "no such object" problem isn't related to the sort value conflicts. It is related to the Artist.reverseName.index setting in tagOptions. The artists that produce this error are the artists with reversed index names.

The problem is fixed now in update 86. This update also contains a change to the "sort value conflict" message to provide more information about the conflicting sort values.

I installed the update. The original problem I noted does appear to be fixed. Thanks.

The sort value conflict messages now look like this:

Code:

Warning: sort value conflict for [artistIndex] filter Moshe Feldenkrais; value1=Feldenkrais, Moshe value2=Moshe Feldenkrais
Warning: sort value conflict for [artistIndex] filter Elizabeth Beringer; value1=Beringer, Elizabeth value2=Elizabeth Beringer
Warning: sort value conflict for [artistIndex] filter David Zemach-Bersin; value1=Zemach-Bersin, David value2=David Zemach-Bersin
Warning: sort value conflict for [artistIndex] filter Mark Reese; value1=Reese, Mark value2=Mark Reese

I figured out that the sort value conflicts result from tracks where the artist was reversed "Reese, Mark" and the AlbumArtist was not reversed "Mark Reese". Since I don't usually set the AlbumArtist at all, this slipped by me. The message might be more useful for troubleshooting if it gave the track title, or some other identifying information about which file generated the conflict. I had to hunt through my collection to try to find files that might be generating the problem.

Actually I am a bit puzzled by one thing. I have an album done by two people where each track is a solo and the artists alternate tracks. There are two albumartist tags, "Leri, Dennis" and "Kress, Carol". Then each file is individually artist tagged as either "Leri, Dennis" or "Kress, Carol" as appropriate. MinimServer reports:

Code:

Warning: conflicting ALBUMARTIST values ignored for file feldenkrais/Mid-Summers-Dream-Intensive-1/2.20.D5_04.DL.Hands.and.Feet.mp3
first conflicting value: Kress, Carol
second conflicting value: Leri, Dennis
Warning: conflicting ALBUMARTIST values ignored for file feldenkrais/Mid-Summers-Dream-Intensive-1/2.16.D4_04.CK.Breathing.mp3
first conflicting value: Kress, Carol
second conflicting value: Leri, Dennis
Warning: conflicting ALBUMARTIST values ignored for file feldenkrais/Mid-Summers-Dream-Intensive-1/1.04.D1_04.CK.Easing.the.Neck.mp3
first conflicting value: Kress, Carol
second conflicting value: Leri, Dennis

Is this how it's supposed to work? The behavior from the control point seems reasonable, namely that the artists appear and I can list the tracks associated with each, or I can select the album and see all the tracks. Is there some other way I ought to handle this?

[simoncn]

(21-05-2016 22:42)adrian Wrote:  I installed the update. The original problem I noted does appear to be fixed. Thanks.

I'm pleased to hear this. Thanks for your help with finding and fixing this problem.

Quote:I figured out that the sort value conflicts result from tracks where the artist was reversed "Reese, Mark" and the AlbumArtist was not reversed "Mark Reese". Since I don't usually set the AlbumArtist at all, this slipped by me. The message might be more useful for troubleshooting if it gave the track title, or some other identifying information about which file generated the conflict. I had to hunt through my collection to try to find files that might be generating the problem.

The message could identify the file that generates the conflict message. This might not always be the file that is "wrong" but it should help some of the time.

Quote:Actually I am a bit puzzled by one thing. I have an album done by two people where each track is a solo and the artists alternate tracks. There are two albumartist tags, "Leri, Dennis" and "Kress, Carol". Then each file is individually artist tagged as either "Leri, Dennis" or "Kress, Carol" as appropriate.

MinimServer doesn't allow more than one AlbumArtist tag on the same album. You can have any number of Artist tags. If you need an AlbumArtist tag on this album for some reason, you could use something like "Leri, Dennis and Kress, Carol".

[adrian]

I deleted the AlbumArtist multi-tag and now I don't have any warning messages showing up in the log file after running rescan. (Well, except for something about a bad playlist during...but I'm still trying to find software that will make relative playlists under linux, so probably my play list is broken, since it's full of absolute paths that are wrong for MinimServer.)

[simoncn]

(22-05-2016 17:21)adrian Wrote:  I deleted the AlbumArtist multi-tag and now I don't have any warning messages showing up in the log file after running rescan. (Well, except for something about a bad playlist during...but I'm still trying to find software that will make relative playlists under linux, so probably my play list is broken, since it's full of absolute paths that are wrong for MinimServer.)

MinimServer supports absolute paths. Can you create a symbolic link to make these paths valid?