error playing tracks from searches

[adrian]

(22-05-2016 17:49)simoncn Wrote:  MinimServer supports absolute paths. Can you create a symbolic link to make these paths valid?

Yeah, I could do that. If I can't figure out a way to get relative paths I'll do it. But relative paths seem much more robust in general, since it means the playlist is completely relocatable.

I left a "tail -f minimserver.log" open and I noticed these messages have appeared:

Code:

MinimServer: 0$=Genre$9435 isn't a valid object
MinimServer: 0$=Genre$9435 isn't a valid object
MinimServer: 0$=Genre$9435 isn't a valid object

I have not been able to figure out what operation generated these messages. If I figure it out I'll supply that additional information.

[simoncn]

(22-05-2016 22:53)adrian Wrote:  I left a "tail -f minimserver.log" open and I noticed these messages have appeared:

Code:

MinimServer: 0$=Genre$9435 isn't a valid object
MinimServer: 0$=Genre$9435 isn't a valid object
MinimServer: 0$=Genre$9435 isn't a valid object

I have not been able to figure out what operation generated these messages. If I figure it out I'll supply that additional information.

Thanks! You can timestamp log messages by setting the .logPrefix property. If you set this to 'time', messages will be prefixed with a timestamp. The 'dateTime' setting includes a datestamp as well. This might help you to recall what you were doing when the messages were written to the log.

[simoncn]

Code:

MinimServer: 0$=Genre$9435 isn't a valid object

Messages like this are normally caused by the control point having out-of-date cached information after you have made changes to the MinimServer library. What control point were you using?

[adrian]

(23-05-2016 08:47)simoncn Wrote:  

Code:

MinimServer: 0$=Genre$9435 isn't a valid object

Messages like this are normally caused by the control point having out-of-date cached information after you have made changes to the MinimServer library. What control point were you using?

I actually ran through everything I could remember doing, so I don't think having time stamps would have helped in this case.

I did some tests with 8player on the iPad, and we also use the Olive ONE. Right now I have set up the ONE to use a uPNP cache, which is a ridiculous kludge that doesn't even seem to do what it is supposed to. And I have to explicitly rebuild the cache when I update the library. I haven't done this, so probably that explains the messages.

[simoncn]

(21-05-2016 22:42)adrian Wrote:  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.

In MinimServer update 87, the "sort value conflict" message now shows the track titles for the files that are producing the conflict.

[adrian]

After updating to 87 I discovered (sometime later) that minimserver wasn't running. I invoked minimwatch and saw an error:

Code:

MinimWatch 0.8.1, Copyright (c) 2012, 2013 Simon Nash. All rights reserved.
Enter command (? for help), or null to exit:
Selected media server: MinimServer[echidna]
MinimServer[echidna]: exception while processing action request: java.lang.ClassCastException: com.minimserver.Server$CompleteAlbum cannot be cast to com.minimserver.Server$AlbumSet
MinimServer[echidna] error: now stopped, use 'relaunch' or 'close'

[simoncn]

(25-05-2016 22:07)adrian Wrote:  After updating to 87 I discovered (sometime later) that minimserver wasn't running. I invoked minimwatch and saw an error:

Code:

MinimWatch 0.8.1, Copyright (c) 2012, 2013 Simon Nash. All rights reserved.
Enter command (? for help), or null to exit:
Selected media server: MinimServer[echidna]
MinimServer[echidna]: exception while processing action request: java.lang.ClassCastException: com.minimserver.Server$CompleteAlbum cannot be cast to com.minimserver.Server$AlbumSet
MinimServer[echidna] error: now stopped, use 'relaunch' or 'close'

Is there a crash dump file in the 'data' directory? If so, please attach it to a post here.

MinimWatch 0.8.1 is no longer supported and you are strongly recommended to install the 0.8.4 version. This is not related to the ClassCastException error.

[adrian]

(25-05-2016 22:16)simoncn Wrote:  

(25-05-2016 22:07)adrian Wrote:  After updating to 87 I discovered (sometime later) that minimserver wasn't running. I invoked minimwatch and saw an error:

Code:

MinimWatch 0.8.1, Copyright (c) 2012, 2013 Simon Nash. All rights reserved.
Enter command (? for help), or null to exit:
Selected media server: MinimServer[echidna]
MinimServer[echidna]: exception while processing action request: java.lang.ClassCastException: com.minimserver.Server$CompleteAlbum cannot be cast to com.minimserver.Server$AlbumSet
MinimServer[echidna] error: now stopped, use 'relaunch' or 'close'

Is there a crash dump file in the 'data' directory? If so, please attach it to a post here.

MinimWatch 0.8.1 is no longer supported and you are strongly recommended to install the 0.8.4 version. This is not related to the ClassCastException error.

MinimWatch updated.

I have attached the crash log that I found.

I also noticed that in the regular log the error is preceded by a bunch of messages

Code:

MinimServer: 0$=Genre$5832$=Artist$5959$albums$135 isn't a valid object
MinimServer: 0$=Genre$5832$=Artist$5951$albums$135 isn't a valid object
MinimServer: 0$=Genre$5832$=Artist$5951$albums$135 isn't a valid object
MinimServer: 0$=Genre$8663$=Artist$8758$albums$236 isn't a valid object
MinimServer: 0$=Genre$8663$=Artist$8758$albums$236 isn't a valid object
MinimServer: 0$=Genre$8663$=Artist$8755$albums$236 isn't a valid object
MinimServer: 0$=Genre$8663$=Artist$8755$albums$236 isn't a valid object
MinimServer: 0$=Genre$1044$albums$*a6$s10615.0 isn't a valid object
MinimServer: 0$=Genre$1044$albums$*a6$s10615.0 isn't a valid object
MinimServer: 0$=Genre$1044$albums$84 isn't a valid object
MinimServer: 0$=Genre$1044$albums$84 isn't a valid object

Unfortunately, I don't know if these messages are related. I'm turning on that time stamping feature for the log file now to decrease ambiguity in the future.

I also noticed I got new messages about sort order conflicts that I didn't see before and that relate to old files that I didn't change. Is there something I can do to check my whole database and root out these problems all at once?

[simoncn]

Thanks for the crash dump and the log extract. The ClassCastException and all the log messages look like they they are all caused by the control point's cache being out of date. I will fix the ClassCastException and replace it by an "isn't a valid object" log message. Thanks for letting me know about this problem.

When MinimServer detects a sort value conflict, it disables sort value processing for the value in question. This means that any further sort value conflicts for the same value (e.g., an artist name) won't be detected until the first conflict is fixed. This approach is necessary because MinimServer doesn't know which alternative is the correct sort value until the user has fixed the first conflict.

Also, some sort values are not checked for conflicts until the user browses to a part of the library that requires the conflicting values to be displayed in a sorted list. For example, the Artist index can contain a mixture of Artist tag values and AlbumArtist tag values and there might be a conflict between an Artist value and an AlbumArtist value. This conflict wouldn't cause any problems if the user is using the All Artists and AlbumArtist indexes instead of the Artist index. Because of cases like this, it is difficult for MinimServer to perform all conflict checking as part of the library scan.

[adrian]

I realized last night something that probably explained the "isn't a valid object" messages. As I think I mentioned somewhere, I've enabled a stupid kludge feature on my control point where it makes a cache of the entire database. With this feature on, I have to explicitly tell it to rebuild the cache after I do a rescan. I think it may have been still rebuilding the cache and I did another rescan---I saw this happen in action last night where I was watching the minimserver log and it started spewing "isn't a valid object" messages like crazy. I rebooted my control point and restarted the cache rebuild and the messages quit appearing.

It actually also appears that the "new" sort value conflict was old---I had just overlooked it before in the logs. (It actually had a different origin: the same artist was listed two different ways in an Artist tag on the same album.)