Hmm... I wonder whether it's related to using Qobuz. I saw the delays with Qobuz, too.
Just looked at this a bit closer: API calls to search for tracks would take an average 5 seconds to return from Qobuz. Now that's super slow. And then there's quite some processing, which would hurt your low-power device much more than my mac. Eg. I'm pre-caching track information in the disk cache. This took about 600ms on my SSD based MacBook Pro for nine searches. I'd imagine this could take a while on your little box.
I'll look into optimizing this pre-caching, as we usually wouldn't need the track info for all search results, but only the ones we're actually using (which might be about 1% of those found in this case...).
-- Michael _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
