@fanciulli, I have uploaded the log:
http://logs.volumio.org/volumio/qfjxtFD.html
I mostly just left Volumio to play a few albums and didn’t monitor it too closely. But I did see it skip songs at least a couple of times. I am interested in knowing your feedback.
Thanks.
Hello @Aylarja,
from an initial analysis of your log i see that from the scheduling on the song to the effective playback you have a constant 6 seconds of delay. Can you exclude any kind of network related delays due to something like a proxy, firewall etc?
@fanciulli, I don’t use a proxy, and the only firewall is the standard one built into my router. I checked its logs and see no evidence of anything being blocked while I’m playing Qobuz from Volumio. For reference, if I play Qobuz directly from the Qobuz app on either my desktop computer or a mobile device, there is no lag whatsoever - one song plays immediately after the previous one ends, and no song-skipping, either.
If there is something else that I might check, please let me know. Thanks.
@fanciulli, do you have any further questions or guidance? Or any other possibilities on the six-second delay? Thanks.
Volumio 2.861
Very often now I’ll start up RPi and Volumio and Qobuz will not be there under Home - just Favourites and Music library showing.
Note, I don’t currently use Spotify.
I check sources - no Qobuz showing.
I check my account login. Yup I’m signed in and it’s showing Virtuoso.
After a fair bit of messing about, I realised;
I have to logout and log back in again.
Volumio will do it’s search circular dots thing and then Qobuz will be accessable.
I’ve had to do this pretty much every time after RPi has been shutdown and powered up the past week!
I always shutdown in Volumio.
Would be great with a fix to this.
Hello @Aylarja,
in the test channel there’s a new version with added telemetry to better check you issue. Could you please update to that version and replicate the issue? Wen done, please send me the log file.
Thank you.
@fanciulli, I updated Volumio to the latest version, and then generated a new log file: http://logs.volumio.org/volumio/gIljY5W.html.
This is probably nothing but normal behavior, although I haven’t noticed it before: when in the DEV console for Volumio, in the section titled “Player State”, there is a value labeled “seek” that is continuously increasing, even when the player isn’t playing. Assuming this is normal, I am curious about its purpose.
Please let me know if you have further questions or observations about my log file. I appreciate your help.
For the record, after updating to 2.873 I’ve not had the missing / won’t load Qobuz problem again🤠
This is after many power ups and use sessions.
Current track playing updates are also much faster👍
Hello @Aylarja,
from the log you sent i see the following:
TESTING REMOTE ENDPOINTS
https://google.com: FAILED
https://www.googleapis.com: FAILED
https://securetoken.googleapis.com: OK
https://myvolumio.firebaseio.com: FAILED
https://functions.volumio.cloud: FAILED
https://oauth-performer.dfs.volumio.org: FAILED
http://cddb.volumio.org: FAILED
https://functions.volumio.cloud: FAILED
http://pushupdates.volumio.org: FAILED
http://plugins.volumio.org: FAILED
https://database.volumio.cloud: FAILED
https://radio-directory.firebaseapp.com: FAILED
Moreover i see that EVERY connection to our cloud requires about 6 seconds. That’s quite strange. Looks like you’re having some network configuration which is not perfect…
Are you using a proxy, VPN or firewall?
This will explain why all network requests take so long, and therefore they make playback fail (prefetch of a song shall last less than 5 seconds, while your calls require 6)
@fanciulli, very interesting. I tried manually clicking on the links above while on the same network as my Volumio player, just to see if my router is blocking them for some reason. I think most of these links expect query data to be passed to them, and so most of them return some type of error message because I am simply attempting to access the domain name without a query string. However, these messages appear to be generated by the remote servers and not my router since they are formatted differently from one another.
After checking my router logs to see if any of these URLs were being blocked, I found nothing. As a test, I whitelisted on my router all of the URLs listed above. Interestingly, the www.googleapis.com URL now passes the test, but none of the others do. Then I disabled my router’s Trend Micro content filtering, and that made no difference either.
I am not very familiar with Linux, but would it be possible to perform tracert with each URL listed above, especially if they are able to query actual data? Although I agree my router would be a likely cause of these failures, I don’t see evidence that it actually is. Is it possible that there is something with the account used to access these resources? For instance, is it my Virtuoso account?
I would appreciate any suggestions on further testing. There is no value in maintaining my Virtuoso account if I am unable to use Volumio with Qobuz. It is essential that I sort this out.
Thanks.
@volumio, I am not using any of these. I agree that these would be likely culprits, but none of them apply.
Thanks, Aylarja
@volumio, I should note that my router acts as a firewall, but I am not using a third-party service, if that is what you mean. My router does use Trend Micro filtering, which would also seem a likely suspect, but it logs nothing of these URLs, and even when I whitelist them or turn of the Trend Micro altogether, it makes no difference.
Hello @Aylarja,
after further research it seems that the issue may be due to a bug in the DNS resolving which in some particular configuration introduces a 5 seconds delay.
If ok for you i would like you to perform the following tasks and report the result.
Please, let me know.
Massimiliano
@fanciulli, apologies for taking so long to respond. I followed your instructions and produced another log file, available here: http://logs.volumio.org/volumio/rldwylN.html. Hopefully this provides more information on the behavior, which is still occurring. I look forward to your feedback. Thanks.
@Aylarja from the logs we can see that your system cannot reach any of the endpoints needed for MyVolumo to work:
TESTING REMOTE ENDPOINTS
https://google.com: FAILED
https://www.googleapis.com: FAILED
https://securetoken.googleapis.com: FAILED
https://myvolumio.firebaseio.com: FAILED
https://functions.volumio.cloud: FAILED
https://oauth-performer.dfs.volumio.org: FAILED
http://cddb.volumio.org: FAILED
https://functions.volumio.cloud: FAILED
http://pushupdates.volumio.org: FAILED
http://plugins.volumio.org: FAILED
https://database.volumio.cloud: FAILED
https://radio-directory.firebaseapp.com: FAILED
Can you exclude your trend micro firewall?
Do you have network blocking of some sort or can you put Volumio under DMZ in your router?
What are your DNS and your gateway settings?
@volumio, I think you helped solve this puzzle. I checked my DNS settings - they were the ones assigned automatically by my Internet service provider, Wave Broadband in California, USA. Their primary DNS server is 76.14.0.8, and their secondary is 208.76.152.1. Although not necessarily a problem, the completely different addresses struck me as odd, and prompted me to dig further to see if that might be the problem.
I switched my settings to Cloudflare’s free DNS servers, and after restarting my Raspberry Pi, once Volumio was back up, I could immediately see the difference in responsiveness: Qobuz options popped on the screen within a second or two, whereas previously I got to watch the progress bar crawl its way across the screen. Artists and albums pop up almost immediately. I created a log file and reviewed it and found that all of the remote endpoints connected successfully. Currently I am testing with some albums to ensure that there is no further song-skipping, but I am pretty confident that will be fine, too. The music starts playing almost immediately, and the gap between songs is practically non-existent, as well. So if other customers of yours are on Wave Broadband and have and similar issues, consider the DNS servers likely suspects.
Thank you for your help, and @fanciulli was very persistent and helpful as well. I’ll post back if I discover some issue that is not resolved, but what I’m seeing so far is night-and-day improvement, so I’m pretty confident things are good now.
Really glad that we helped you finding the core issue 
And even more glad that now you can finally enjoy music with Volumio as it is supposed to.
Your experience motivated us to add few tests to Volumio which hopefully will be beneficial also for other users in your same situation, so it was really worth
Enjoy!