hmmm ... found the guilty plugin and it was one of mine, of course :). LMS was constantly asking for metadata of a track that was not and could not be cached. Would you happen to know, when getMetadataFor is called, what is the minimum infoset that will decide LMS to not continue asking for metadata? Is this artist, album, duration, title? Otherwise I'll look at the code
The status query would certainly use that function to get track information. Probably display code?
I usually do cache in getMetadataFor too, in particular when dealing with remote tracks. Would yours have been an expensive call?
If in doubt (and if you don't fear the excessive logging), you could always add a logBacktrace() statement to getMetadataFor() to see where the calls are coming from. I'm not sure whether the callers do implement any kind of caching.
-- Michael _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
