First: how many tracks does the SmartMix Qobuz Algorithm request in one batch? GoogleMusic does 5 and can be set to 10 according to what I found. Can this be easily changed for Qobuz too?
It requests 200 items.
Second: how about that "retry" option? TEN throws out a batch of suggestions, so, could the Plugin be instructed to try a different starting track if the first one doesn't return any matches? This might
Automatic re-try can be from useless to dangerous. If it doesn't find a match on first attempt, then it's unlikely you'll ever get a decent mix. There is kind of a re-try feature when you are running into the "don't stop the music" mode. It would first try when there are three tracks left (I think). If that fails, it will again try when there are only two, then one left. This also makes sure we don't hammer the backend.
Which gets us to the "dangerous" part: my dev key is limit to 200 requests per minute (iirc). This number is shared across _all_ users of SmartMix. And there are thousands of installations out there. It's unlikely they are all being used at the same time. Therefore we've been happy campers, even with that rather small number of requests available. But I've added quite some logic to make sure we don't use excessive requests. Re-try would easily cause issues in this regard: if you happen to try to start a mix with an impossible recipe, when should it stop trying? Should it run five consecutive attempts before giving up? Imagine ten users doing the same (which is a very small percentage of all SmartMix users!). These users could easily break functionality for the other users by consuming all requests available.
-- Michael _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
