Frequent Playback Interruptions via AirPlay (ref#EFCFFE)

What’s happening?

· Playback stopping

Describe the issue

Playback stopping frequently over AirPlay

Describe your network setup

New fibre-optic connection (150 Mbps) to existing hardware: Draytek Vigor 2762 Router (DHCP, with static IP addresses for audio eqpt) with Amplifi HD (in Bridge mode) for Wifi. Netgear unmanaged 8-port switch. IGMP & multicast etc both disabled.

Might be worth trying things with these enabled. Mainly multicast.

Hi, OP here with further details:

We got Fibre last week, but with SOHO grade hardware already in place and in use with prior copper connection, it was simply a case of swapping the cables out, so we had no need for the ISP (EE UK aka BT) router. Updated login credentials & DNS to 8.8.8.8 was about all I had to do.

Running Roon on a SSD NUC, usually very stable. Wired connection to router, or switch, as desired. A similar post suggested switch actually preferable to router…? Linn Majik also wired connection, NO ISSUES.

Tidal for streaming.

Ping to endpoint:

— 192.168.1.16 ping statistics —
141 packets transmitted, 141 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.718/2.722/8.859/1.284 ms

The 3 AirPlay endpoints however, are frequently stopping at the start of a new track. The new track is cued, but does not play. This happens whether in Shuffle or Album play mode. It may happen straight after the first track, or after several. It does not appear to happen when playing local files.

Any ideas? Thanks in advance :wink:

Thanks for the swift response Menzies, I’ll try enabling multicast. I remember disabling it a good few years ago, as recommended in a Linn support doc…

Hello @Hifipilot
A possibly redundant question, did you restart your entire network after swapping the cables out?
Which means turning off modem, wifi router, switch, streamer, NUC server, all audio endpoints →
and unplug from power for a few minutes.
Then turn everything back on one after the other, as soon as the modem and WiFi router are back.
Dont forget to turn off and restart all remotes.
Good luck.

Hi Axel, I forgot to add that. EVERYTHING has been restarted multiple times! Will try Menzies multicast suggestion at lunchtime, partner is WFH and we can’t have any outages before then.

The only other thing I omitted, we now have an IPv6 WAN connection with the fibre. I’ve left the connection type at PPP in the absence of any info to tell me otherwise…

Well after enabling IGMP (which seems to handle the multicasting on the Draytek) I’ve had several hours of problem-free shuffling, so thanks very much Menzies!

2 Likes

This could be the cause.

Did you enter the DNS server for IPv6 in hexadecimal format:
2001:4860:4860::8888
2001:4860:4860::8844

Just in case Menzies multicast suggestion doesn’t help.

1 Like

That’s nice to hear :slight_smile:

1 Like

:crossed_fingers:

I hope things continue playing well for you

Hi @Hifipilot,

Please let us know if this remains stable.

For context, multicast allows Airplay devices to query and announce one another across the network. It’s best to keep this setting toggled on in a networked Roon environment.

Hi Connor,

After extensive tweaking, the root cause was actually failing network hardware, specifically the Amplifi HD. I swapped it out for the new ISP router (with Wifi 6) and scanning both setups with Wifi Sweetspots (iOS) revealed throughput had more than doubled, from 300 Mbps to 700 Mbps. Roon’s been happily shuffling tracks to 3 endpoints simultaneously for several hours without skipping a beat, and Remote performance seems snappier too.

Comparing logs pre/pro there are now far fewer lost packets. Previously, they were not infrequent.

The Amplifi has always run hot, so it can be forgiven for starting to show its age after 6 long years of continuous service. It still works, and self-tests OK, but the casing has deteriorated into a sticky mess, and if even a stock ISP router can now outperform it, then it was ripe for retirement…

Hi @Hifipilot,

Thank you for the update. Please create a new topic thread should any instability return and we’ll happily assist.

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.