Type in your question below and we'll check to see what answers we can find...
Loading article...
Submitting...
If you couldn't find any answers in the previous step then we need to post your question in the community and wait for someone to respond. You'll be notified when that happens.
Simply add some detail to your question and refine the title if needed, choose the relevant category, then post.
Before we can post your question we need you to quickly make an account (or sign in if you already have one).
Don't worry - it's quick and painless! Just click below, and once you're logged in we'll bring you right back here and post your question. We'll remember what you've already typed in so you won't have to do it again.
I am trying to play Spotify throough my wifi amplifier - Pioneer VSX 924. It has always been fine but has stopped working this morning (last used a few days ago and was fine).
The diplay shows that the track is going to the receiver (ooutput on tv and display window on the receiver.
I have reinstalled the application on my phone and also tried using a laptop.
It seems it may be something to do with the amp using the spotify link - it works perfectly via plastation as a connect to the receivier. Just dooes not work with the application which is a lot better.
Any ideas?
Solved! Go to Solution.
In the last week my Pioneer VSX-1130K spotify connect has not been working properly either. I am getting audio, but it skips out every 10-20seconds. It used to work pretty well up until recently.
When I use Spotify+Airplay to the same receiver, no gaps whatsoever. I have the receiver connected via ethernet to a powerline adapter that gets atleast 20mbs with no detectable packet loss. (Im on gigabit internet at the router)
One more thing.. Make sure you completely unplug and replug in the receiver (not just power off). This often helps with Pioneer receivers, but it isnt helping with the skipping Im seeing recently.
I think there may be an issue with the east coast US spotify servers in Ashburn. I see 10-20% packet loss for pings to servers like ash2-accesspoint-a112.ash2.spotify.com . I'm wondering if this is related to the spotify connect issues.
$ ping ash2-accesspoint-a112.ash2.spotify.com
PING ash2-accesspoint-a112.ash2.spotify.com (23.92.108.235): 56 data bytes
64 bytes from 23.92.108.235: icmp_seq=0 ttl=46 time=15.106 ms
64 bytes from 23.92.108.235: icmp_seq=1 ttl=46 time=11.399 ms
64 bytes from 23.92.108.235: icmp_seq=2 ttl=46 time=11.523 ms
64 bytes from 23.92.108.235: icmp_seq=3 ttl=46 time=12.008 ms
64 bytes from 23.92.108.235: icmp_seq=4 ttl=46 time=14.021 ms
64 bytes from 23.92.108.235: icmp_seq=5 ttl=46 time=12.162 ms
64 bytes from 23.92.108.235: icmp_seq=6 ttl=46 time=11.226 ms
64 bytes from 23.92.108.235: icmp_seq=7 ttl=46 time=11.465 ms
64 bytes from 23.92.108.235: icmp_seq=8 ttl=46 time=11.978 ms
64 bytes from 23.92.108.235: icmp_seq=9 ttl=46 time=11.504 ms
Request timeout for icmp_seq 10
Request timeout for icmp_seq 11
64 bytes from 23.92.108.235: icmp_seq=12 ttl=46 time=11.130 ms
64 bytes from 23.92.108.235: icmp_seq=13 ttl=46 time=12.371 ms
Request timeout for icmp_seq 14
64 bytes from 23.92.108.235: icmp_seq=15 ttl=46 time=10.954 ms
64 bytes from 23.92.108.235: icmp_seq=16 ttl=46 time=13.405 ms
Request timeout for icmp_seq 17
64 bytes from 23.92.108.235: icmp_seq=18 ttl=46 time=12.144 ms
64 bytes from 23.92.108.235: icmp_seq=19 ttl=46 time=12.009 ms
64 bytes from 23.92.108.235: icmp_seq=20 ttl=46 time=11.963 ms
^C
--- ash2-accesspoint-a112.ash2.spotify.com ping statistics ---
21 packets transmitted, 17 packets received, 19.0% packet loss
round-trip min/avg/max/stddev = 10.954/12.139/15.106/1.061 ms
Hey there you, Yeah, you! 😁 Welcome - we're glad you joined the Spotify Community! While you here, let's have a fun game and get…