We have no reports about it, and here it works just fine. Please contact our customer care and they’ll help you out
Hi I see the error in your log.
Please verify that:
- You do the supersearch after at least 20 seconds after you hear the startup sound
- You have Volumio Premium account
- Your device is enabled in your settings
Let me know
- I waited for a few minutes after reboot to perform the search
- I actually have “Superstar yearly” which cost me €66.99 in May this year. Glad you asked about that. Why does this cost more than the €59.99 Premium plan?
- The device is enabled in settings
Here is the new log file after this time of trying “britpop from the 90s” in Supersearch:
It’s working did a reboot and noticed there was a volumio update so did that too. Thanks.
About my other question for premium, does remote access mean you can access and play your own music library from your phone outside the house, and or offline mode?
I got a DAC connected to rpi4 as the main device? Have been able to get an answer on this.
Thank you! I understand these new features are still in beta, so I’ll just turn it off for now.
Cheers
1 Like
Hi & thx Michelangelo,
I have carried out the 3 steps as proposed.
Then I acitviated the Supersearch and entered “American Folk”. Result was “No item” and it took about 3 minutes until I could browse my local library or to stop the current stream (I have been playing music when I tried it).
Here the link to the log: http://logs.volumio.org/volumio/dVV7k6e.html
Best regards Axel
1 Like
hey @volumio - this was not resolved yet
We are investigating, your case is really not easy since we can’t replicate the issue you have, but we have clues.
We are collecting all your feedbacks and bug reports and working to improve the supersearch feature, our goal is to send an update at the end of the month.
OK, I can wait for that. I know this advanced search will be great once fully baked 
… though what about my question about Superstar vs Premium price I paid? What is the difference? This plan seems not to be available any more, what did I gain by paying more for Superstar? Thanks.
I notice that What Hi-fi has a news article about Volumio and the supersearch function.
Is there any way to tell supersearch to use a particular source plugin, e.g. Tidal vs Spotify ?
Right now, when I use supersearch I only seem to get results from Spotify, no matter where I start the search, so I have to disable the Spotify plugin to get supersearch results from Tidal.
Is there any way to set the desired source, e.g. Spotify, Tidal or Local, or any combo of your sources …?
1 Like
No. It’s a good idea though and has been suggested already. Also to reduce the overhead on searches to just those sources required by the user.
Thanks guys for the suggestions, we are taking them into consideration for tweaking the supersearch 
I performed the update this morning to 3.532 and tested the supersearch and infinity playing, it’s simply amazing. I’ve always been quick and straight in criticism but with a working spotify and this 2 new additions, volumio reach the top that it has slightly left for a while
Of course this is not perfect and I join to some requests from previous posts (more -why not plenty ?- of AI tweaking ability, source choice, pre fill of search area with memory…etc) but the result is already quite good and you meet my expectation in term of music consumption
My first search was “Django Django” and the resulting playlist was so good despite of some repetition
Thx for the work
I played an album from a connected USB drive. Then I clicked infinity playback, but the music stopped after the last track has been played. And in the display it showed me not the titles which it played but which currently where played in Radio Paradise Mellow Mix :-/
How many tracks are available in your local library? Infinity needs at least 1k tracks
FWIW the router is more likely the culprit in these cases.
Interesting, but how to understand, respectively can you explain more about the background?
Und wenn es mit dem Router zusammenhängt, frage ich mich, ob der Router wirklich der Übeltäter ist, oder ob es ein Problem der Implementierung ist, die mit bestimmten Verhaltensweisen von Routern nicht umgehen kann (?)