Bose speaker (wifi) - packet loss

Support
1

Core Machine

Network Details

Audio Devices

Library Size

Description of Issue

Hi,

I can ping the device; sometimes there is timeout but the packet loss on lets say 1000 packets is ~1-2%

The Roon server log is full of messages as below, any idea what exactly is the problem?

Thanks

06/26 21:55:35 Trace: [bose] [LowQuality 74.2x, 24/44 MP3 => 16/44] [100% buf] [PLAYING @ 79:16] Dido The Day Before We Went To War (Leimantour Edit)
06/26 21:55:35 Trace: [airplay/client] server lost 1 packets starting at seq 64594
06/26 21:55:35 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64594
06/26 21:55:35 Trace: [airplay/client] server lost 1 packets starting at seq 64595
06/26 21:55:35 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64595
06/26 21:55:35 Trace: [airplay/client] server lost 1 packets starting at seq 64594
06/26 21:55:35 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64594
06/26 21:55:35 Trace: [airplay/client] server lost 1 packets starting at seq 64595
06/26 21:55:35 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64595
06/26 21:55:35 Trace: [airplay/client] server lost 1 packets starting at seq 64594
06/26 21:55:35 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64594
06/26 21:55:35 Trace: [airplay/client] server lost 1 packets starting at seq 64595
06/26 21:55:35 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64595
06/26 21:55:35 Trace: [airplay/client] server lost 1 packets starting at seq 64688
06/26 21:55:35 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64688
06/26 21:55:35 Trace: [airplay/client] server lost 1 packets starting at seq 64696
06/26 21:55:35 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64696
06/26 21:55:35 Trace: [mdns/dacp] [airplay/dacp] got command 'getproperty' value=0
06/26 21:55:35 Trace: [airplay] unknown transport control: getproperty
06/26 21:55:36 Trace: [airplay/client] server lost 1 packets starting at seq 64696
06/26 21:55:36 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64696
06/26 21:55:36 Trace: [airplay/client] server lost 1 packets starting at seq 64725
06/26 21:55:36 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64725
06/26 21:55:37 Trace: [mdns/dacp] [airplay/dacp] got command 'getproperty' value=0
06/26 21:55:37 Trace: [airplay] unknown transport control: getproperty
06/26 21:55:37 Trace: [airplay/client] server lost 1 packets starting at seq 64844
06/26 21:55:37 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64844
06/26 21:55:37 Trace: [airplay/client] server lost 1 packets starting at seq 64925
06/26 21:55:37 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64925
06/26 21:55:37 Trace: [airplay/client] server lost 1 packets starting at seq 64926
06/26 21:55:37 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64926
06/26 21:55:38 Trace: [airplay/client] server lost 1 packets starting at seq 64964
06/26 21:55:38 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64964
06/26 21:55:38 Trace: [airplay/client] server lost 1 packets starting at seq 64965
06/26 21:55:38 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64965
06/26 21:55:38 Trace: [airplay/client] server lost 1 packets starting at seq 64976
06/26 21:55:38 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64976
06/26 21:55:38 Trace: [airplay/client] server lost 1 packets starting at seq 64978
06/26 21:55:38 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64978
06/26 21:55:38 Trace: [mdns/dacp] [airplay/dacp] got command 'getproperty' value=0
06/26 21:55:38 Trace: [airplay] unknown transport control: getproperty
06/26 21:55:38 Trace: [airplay/client] server lost 1 packets starting at seq 64990
06/26 21:55:38 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 64990
06/26 21:55:38 Trace: [airplay/client] server lost 1 packets starting at seq 65005
06/26 21:55:38 Trace: [airplay/client] resent packet to 10.0.1.32:1264 with seq 65005
2

Hi,

In order for Roon’s @support team to better assist you, please provide a brief description of your current setup and the nature of the issue using this link as a guide.

Make sure to describe your network configuration/topology, including any networking hardware currently in use, so they have a clear understanding of how your devices are connected.

1 Like
3

@Carl
the setup is nothing special, just Bose Soundlink speaker connected via wifi to the AP - while playing i can see these errors in Roon server log; no idea what the issue is.

4

Hey @John_Smith,

Thanks for letting us know of the error you’ve ran into. We’d love to help!

As @Carl has suggested, providing our team with the details in the template will help us help you best. Also, could you please send us a screenshot of Settings → Audio in Roon? Do your Bose speakers show up there?

Thanks in advance :pray:

5

@carl @beka
its common setup, all the other endpoints works “fine”; the speaker shows up there… the error is getting generated while playback to that Bose speaker.

Core Machine
ubuntu

Network Details
router / ethernet/wifi
Audio Devices
Bose speaker
Library Size
200 albums
Description of Issue
during the playback multiple errors as below are in the roon core log

07/17 10:38:59 Trace: [airplay/client] server lost 1 packets starting at seq 45502
07/17 10:38:59 Trace: [airplay/client] resent packet to 10.0.1.32:1246 with seq 45502
07/17 10:39:00 Trace: [airplay/client] server lost 1 packets starting at seq 45557
07/17 10:39:00 Trace: [airplay/client] resent packet to 10.0.1.32:1246 with seq 45557

the speaker has no connectivity issue > pinging speaker from core directly

64 bytes from 10.0.1.32: icmp_seq=215 ttl=128 time=9.38 ms
64 bytes from 10.0.1.32: icmp_seq=216 ttl=128 time=4.13 ms
64 bytes from 10.0.1.32: icmp_seq=217 ttl=128 time=9.74 ms
64 bytes from 10.0.1.32: icmp_seq=218 ttl=128 time=4.14 ms
64 bytes from 10.0.1.32: icmp_seq=219 ttl=128 time=5.99 ms
64 bytes from 10.0.1.32: icmp_seq=220 ttl=128 time=5.18 ms
64 bytes from 10.0.1.32: icmp_seq=221 ttl=128 time=13.2 ms

— 10.0.1.32 ping statistics —
221 packets transmitted, 219 received, 0% packet loss, time 220399ms
rtt min/avg/max/mdev = 2.723/7.132/25.320/3.582 ms

6

Hey @John_Smith,

Thanks a bunch for the details.

I’ve looped in our technical team so they can take a closer look and make suggestions :nerd_face:

7

This topic was automatically closed after 6 days. New replies are no longer allowed.