Re: [slim] Player synchronisation problems with new mesh wifi
That makes sense. So Shairtunes wasn't the culprit but the victim, and I drew the wrong conclusion from the error messages. Whatever's causing this occasional 37s dropout when players are synced and playing is quite a rare phenomenon in my case. I've had my RPi powered down and back up numerous times today, and haven't had one instance of the dropout problem. But there do seem to be one or two other users with the same issue, dating back to 2014. It seems like the RPi might be a common factor. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
What I have observed on my own network is that, from time to time, my wifi system goes "nuts" which causes players to disconnect randomly. As a result, players in sync will stop and restart as soon as a player re-joins, this is the way LMS works. Then, you'll have all these messages from Shairtunes because each instance stops when the player is disconnected and restarts when it comes back. That can be very annoying and I've never been able to figure out why. I had that with 3 different generations of routers and PLC (unfortuntaly I use PLC). Sometime it happens continuously for a day or two and then I don't have anything for 3 month. I've never been able either to correlate it with RF issues and I leave in a non-polluted WiFi zone. LMS 7.7, 7.8 and 7.9 - 5xRadio, 3xBoom, 4xDuet, 1xTouch, 1 SB2. Sonos PLAY:3, PLAY:5, Marantz NR1603, JBL OnBeat, XBoxOne, XBMC, Foobar2000, ShairPortW, JRiver 21, 2xChromecast Audio, Chromecast v1 and v2, , Pi B3, B2, Pi B+, 2xPi A+, Odroid-C1, Odroid-C2, Cubie2, Yamaha WX-010, AppleTV 4, Airport Express, GGMM E5 philippe_44's Profile: http://forums.slimdevices.com/member.php?userid=17261 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > I'm pretty sure I read another thread where people were having similar > dropouts with synced players, and I think it was from some time ago so > unlikely to be on a Pi4. I'll see if I can dig out that thread. What do you know - that old thread has just come to life again: https://forums.slimdevices.com/showthread.php?101372-Skips-while-playing-in-sync It seems like I simply encountered a long-standing issue - nothing to do with my mesh wifi. It's quite possible that where I thought disabling and re-enabling Shairtunes2 solved my problem it might simply have been that that process restarted LMS. Oddly, I don't think I ever actually did that manually. I did reboot pCP, but maybe that's not enough - maybe LMS needs to be restarted after everything's up and running. If it happens again that'll be a simple thing to test. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > Sorry, I don't use any of Phillipe's plugins other than Group Players. > > I assume your problem is with a Pi4? Only reports of the 37 second sync > problem are from those using a Pi4? > > I no longer use my Pi4, because of the heat related problems, I've gone > back to a Pi3B+, no problems with syncing. Oh well. I'm pretty sure I read another thread where people were having similar dropouts with synced players, and I think it was from some time ago so unlikely to be on a Pi4. I'll see if I can dig out that thread. The temperatures on my Pi4 now seem to be fully under control, and I do like the (subtle) speed bump. I should also add that Airplay and Bluetooth sync seem much better since I moved to pCP6 beta and RPi4. It could have been something specific about my previous pCP4/RPi3B+ setup, but I found that I had to regularly tweak the sync delay settings, especially for Bluetooth. That's no longer the case with my Pi4. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > Just a thought - are you running the 'ShairTunes2 (fork)'? My mesh wifi > has been running flawlessly for the last couple of weeks, but last night > I had a recurrence of the 37-second dropouts. Rebooting pCP didn't fix > it, nor breaking the synchronisation then re-synching, nor restarting > every wifi AP. I hadn't changed anything in the wifi setup, but I'd > been changing a few things in LMS, and on one occasion pCP booted > without being able to start LMS or Squeezelite because I'd removed a > mounted disk. > > I now suspect that the Shairport-helper *might* be the cause of the 37 > second dropouts. I noticed that the dropouts coincided with > shairport-related messages in the log file (which I stupidly didn't > keep), so I disabled Shairport and the dropouts went away. Then I > reloaded Shairport, and still no dropouts. > > If it ever happens again I will try the 'Re-Publish' or 'Wipe' options > for the helper. Is it possible that the Shairport helper information > can get corrupted under certain circumstances, and that this corrupted > information somehow survives a reboot? This could explain why the only > way I could recover previously was to re-image my SD card. Sorry, I don't use any of Phillipe's plugins other than Group Players. I assume your problem is with a Pi4? Only reports of the 37 second sync problem are from those using a Pi4? I no longer use my Pi4, because of the heat related problems, I've gone back to a Pi3B+, no problems with syncing. *Server - LMS 7.9.2 *Pi3B+/pCP 5.0.1 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > A little more on this. > > The Boom plays fine on it's own. > > Without using phillipe44's "group players", no matter what combination > of player's I sync the skip problem is there. > > Cured by simply restarting LMS on the Pi4 from the piCorePlayer LMS > page. Just a thought - are you running the 'ShairTunes2 (fork)'? My mesh wifi has been running flawlessly for the last couple of weeks, but last night I had a recurrence of the 37-second dropouts. Rebooting pCP didn't fix it, nor breaking the synchronisation then re-synching, nor restarting every wifi AP. I hadn't changed anything in the wifi setup, but I'd been changing a few things in LMS, and on one occasion pCP booted without being able to start LMS or Squeezelite because I'd removed a mounted disk. I now suspect that the Shairport-helper *might* be the cause of the 37 second dropouts. I noticed that the dropouts coincided with shairport-related messages in the log file (which I stupidly didn't keep), so I disabled Shairport and the dropouts went away. Then I reloaded Shairport, and still no dropouts. If it ever happens again I will try the 'Re-Publish' or 'Wipe' options for the helper. Is it possible that the Shairport helper information can get corrupted under certain circumstances, and that this corrupted information somehow survives a reboot? This could explain why the only way I could recover previously was to re-image my SD card. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > > The Boom plays fine on it's own. > > Without using phillipe44's "group players", no matter what combination > of player's I sync the skip problem is there. That's the same symptoms I had. And the dropout interval seems common too. kidstypike wrote: > Cured by simply restarting LMS on the Pi4 from the piCorePlayer LMS > page. Didn't work for me - no amount of restarts/reboots made any difference. Bizarrely, changing the SSID of my new wifi fixed it for me. I never did look into the logs, so any further clues as to the cause are now long gone. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > Let me stress, I've never had this problem before with Pi3's, this only > started happening using a Pi4 as server. > > To answer your questions - No, not Mesh, a decent TP-Link router. > Everything wired except the Boom (signal strength 81%). A little more on this. The Boom plays fine on it's own. Without using phillipe44's "group players", no matter what combination of player's I sync the skip problem is there. Cured by simply restarting LMS on the Pi4 from the piCorePlayer LMS page. *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > Apologies if I've missed this in an earlier post of yours, but how are > your server and Boom connected - wired or wireless? Is yours a mesh > wifi system? > > Although I haven't had a recurrence of my dropout problem, I have had > one or two issues getting devices to connect to my mesh wifi for the > first time. My Jogglers in particular caused me some heartache - I > couldn't even get them to connect after reloading the disk image. In > each case, however, the connection problems have gone away after > rebooting the wifi APs. Worth a try. Let me stress, I've never had this problem before with Pi3's, this only started happening using a Pi4 as server. To answer your questions - No, not Mesh, a decent TP-Link router. Everything wired except the Boom (signal strength 81%). *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > Dropouts are back, and I've timed them, 36 seconds between dropouts! > :confused: > Apologies if I've missed this in an earlier post of yours, but how are your server and Boom connected - wired or wireless? Is yours a mesh wifi system? Although I haven't had a recurrence of my dropout problem, I have had one or two issues getting devices to connect to my mesh wifi for the first time. My Jogglers in particular caused me some heartache - I couldn't even get them to connect after reloading the disk image. In each case, however, the connection problems have gone away after rebooting the wifi APs. Worth a try. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > I reinstated the Pi4 to see if I could repeat the dropout when synced > problem, but it's been perfect, on track 117 no problems. Dropouts are back, and I've timed them, 36 seconds between dropouts! :confused: Server/LMS Pi4 (4GB) Players are a Boom and a RPi3B+/HiFiBerry DAC+/squeezelite using phillipe44's group players. Wait a minute, behaviour has changed, the track I'm playing plays until it gets to 2:16 then jumps back to 1:16, it's done this 5 times now. Skip forward to next track, skips at 00:36, 01:12, 01:48, 02:24. Skip forward to next track, skips at 00:36, 01:12, 01:48, 02:24. :( *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Hooray! Thanks all. Code: tc@musicbox4:~$ sudo ./vl805 VL805 FW version: 000137a8 tc@musicbox4:~$ :) *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > It's a bit annoying that I've had to disable the 802.11r 'fast roaming' > to allow the wireless Boom to connect. I may have misunderstood how 802.11r works. I'm still getting to grips with all the settings, but even without that option enabled my phone seems to switch over to the nearest AP just as quickly. So I've disabled that option again, for maximum compatibility with older wifi kit, such as Booms. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > > > The zip file disappears on reboot is that right? > Yep - files in the /home/tc/ folder will only survive a reboot if they are backed up first - either use the 'backup' button on the 'Main' page before rebooting, or 'pcp br' - (b)ackup then (r)eboot - as Ronnie suggested. 'pCP Command Line Interface' (https://www.picoreplayer.org/pcp_cli.shtml) chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Well I just did this on a pCp on rpi4B (4gb). here is a screen shot 27710 I just checked and the files are still there Code: tc@piCorePlayer:/home$ ls tc/ vl805_fw_013701.bin vl805_update_0137a8.zip vl805vl805_fw_0137a8.bin tc@piCorePlayer:/home$ sudo ./vl805 VL805 FW version: 000137a8 tc@piCorePlayer:/home$ I used Code: pcp br instead of Code: sudo reboot +---+ |Filename: usbfirmwarepCP.png | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=27710| +---+ Man in a van's Profile: http://forums.slimdevices.com/member.php?userid=43627 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Man in a van wrote: > Yep I got that on the Raspbian desktop OS, both before and after running > the update :rolleyes: > > > > > > Code: > > pi@khadastoneboard:~ $ cd Downloads > pi@khadastoneboard:~/Downloads $ ls > vl805_update_0137a8.zip > pi@khadastoneboard:~/Downloads $ unzip vl805_update_0137a8.zip > Archive: vl805_update_0137a8.zip > inflating: vl805 > inflating: vl805_fw_013701.bin > inflating: vl805_fw_0137a8.bin > pi@khadastoneboard:~/Downloads $ chmod a+x vl805 > pi@khadastoneboard:~/Downloads $ sudo ./vl805 -w vl805_fw_0137a8.bin > VL805 FW version: 00013701 > VL805 EEPROM successfully reprogrammed - please reboot to activate > > > > The link to the download is not really user friendly, I tried to use > > wget > https://drive.google.com/file/d/1PXwrnhAXKB1hb5J6_EfPy5zLQkqnbGba/view?usp=sharing > > and that did not work. > > I then went to the link via my Windows browser (firefox) and tried to > copy the download from the page by right clicking the download arrow, > but that did not work. > > So I used VNC to connect to the pi and download the link via Chromium > and then opened a terminal to complete the process :rolleyes: > > ronnie Hi Ronnie I had a 2nd attempt at this, and get as shown in screenshot below, so I assume the update was successful? The zip file disappears on reboot is that right? 27709 +---+ |Filename: attempt2.jpg | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=27709| +---+ *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > Hmm... getting "command not found", what does that mean? > > 27708 Yep I got that on the Raspbian desktop OS, both before and after running the update :rolleyes: Code: pi@khadastoneboard:~ $ cd Downloads pi@khadastoneboard:~/Downloads $ ls vl805_update_0137a8.zip pi@khadastoneboard:~/Downloads $ unzip vl805_update_0137a8.zip Archive: vl805_update_0137a8.zip inflating: vl805 inflating: vl805_fw_013701.bin inflating: vl805_fw_0137a8.bin pi@khadastoneboard:~/Downloads $ chmod a+x vl805 pi@khadastoneboard:~/Downloads $ sudo ./vl805 -w vl805_fw_0137a8.bin VL805 FW version: 00013701 VL805 EEPROM successfully reprogrammed - please reboot to activate The link to the download is not really user friendly, I tried to use wget https://drive.google.com/file/d/1PXwrnhAXKB1hb5J6_EfPy5zLQkqnbGba/view?usp=sharing and that did not work. I then went to the link via my Windows browser (firefox) and tried to copy the download from the page by right clicking the download arrow, but that did not work. So I used VNC to connect to the pi and download the link via Chromium and then opened a terminal to complete the process :rolleyes: ronnie Man in a van's Profile: http://forums.slimdevices.com/member.php?userid=43627 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > Hmm... getting "command not found", what does that mean? > > 27708 I'd guess the file is not executable. Try: Code: chmod +x vl805 cpd73's Profile: http://forums.slimdevices.com/member.php?userid=66686 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
cpd73 wrote: > I'd guess the file is not executable. Try: > > Code: > > > chmod +x vl805 > > > Thanks, but seeing "no such file or directory". *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > > Code: > > sudo ./vl805 > > > > The original instructions are 'here' > (https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=243500&p=1490467#p1490467). Hmm... getting "command not found", what does that mean? 27708 +---+ |Filename: notfound.jpg | |Download: http://forums.slimdevices.com/attachment.php?attachmentid=27708| +---+ *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > > > Where/how would I check the pi's current firmware? > Code: sudo ./vl805 The original instructions are 'here' (https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=243500&p=1490467#p1490467). chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > I'm not familiar with the Windows tools*, but you should use WinSCP to > put the zip file in your home directory (/home/tc/), then use Putty to > SSH into the Pi and issue the following commands from your home > directory (which is where Putty should put you after logging in): > > Code: > > unzip vl805_update_0137a8.zip > chmod a+x vl805 > sudo ./vl805 -w vl805_fw_0137a8.bin > sudo reboot > > > > * I use a Macbook - the tools that work for me are: > - FileZilla for moving files back and forth to the Pi. You can get > FileZilla for Windows. You could use this instead of WinSCP. > - A terminal prompt to open an SSH session. Thanks chill, I think that's got it! Was averaging 60/61 all morning just sitting on my desk no case and doing nothing, now averaging 59/60, a slight improvement. Where/how would I check the pi's current firmware? Thanks again. *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > I have the update .zip > I have WinSCP > I have Putty. > > Where on the pi do I put the zip file, and how? > > Any help with this? > > Thanks I'm not familiar with the Windows tools*, but you should use WinSCP to put the zip file in your home directory (/home/tc/), then use Putty to SSH into the Pi and issue the following commands from your home directory (which is where Putty should put you after logging in): Code: unzip vl805_update_0137a8.zip chmod a+x vl805 sudo ./vl805 -w vl805_fw_0137a8.bin sudo reboot * I use a Macbook - the tools that work for me are: - FileZilla for moving files back and forth to the Pi. You can get FileZilla for Windows. You could use this instead of WinSCP. - A terminal prompt to open an SSH session. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > I'd install the firmware update if I knew how. :( I have the update .zip I have WinSCP I have Putty. Where on the pi do I put the zip file, and how? Any help with this? Thanks *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > I might switch that Boom over to wired so that I can make the most of > that feature. Did that, enabled 'fast roaming'. Seems useful - I can see the wifi signal strength indicator on my phone jump back up quite quickly as I walk away from one AP and towards another. Fortunately the SBR wifi doesn't seem to be affected by having fast roaming enabled, so it's only that Boom that needed to be wired, and since it's right next to a Gigabit switch that was easy to do. Probably should have done it earlier. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
paul- wrote: > Wow, that's weird. At least for pCP there should be no memory of the > actual AP it was connected to other than the SSID. But perhaps some > other device was polluting the network. Yes, I hadn't got around to restarting all the other devices that were connected to the old AP, so maybe one of those was blasting something nasty onto the airwaves. Still don't understand why the glitches persisted when I reinstated the Airport instead of the mesh, nor why the glitches didn't happen in the last minute or so of a track, even though they came every 37s during the song. I'm not going to lose sleep over it though - everything's been running fine since the change of SSID. It's a bit annoying that I've had to disable the 802.11r 'fast roaming' to allow the wireless Boom to connect. I might switch that Boom over to wired so that I can make the most of that feature. Typical isn't it - I buy a super-duper new wifi system and have to switch at least one device to wired. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
paul- wrote: > Wow, that's weird. At least for pCP there should be no memory of the > actual AP it was connected to other than the SSID. But perhaps some > other device was polluting the network. > > And Kidstypike, did you install the new firmware from RPI? It really > dropped the temp of my system. > > https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=243500&p=1490467#p1490467 > > I see they have a new bootloader too: > https://www.raspberrypi.org/forums/viewtopic.php?f=117&t=246027 > > If all else fails, maybe you need one of these..lol > https://www.seeedstudio.com/ICE-Tower-CPU-Cooling-Fan-for-Raspberry-pi-Support-Pi-4-p-4097.html I reinstated the Pi4 to see if I could repeat the dropout when synced problem, but it's been perfect, on track 117 no problems. I'd install the firmware update if I knew how. :( *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Wow, that's weird. At least for pCP there should be no memory of the actual AP it was connected to other than the SSID. But perhaps some other device was polluting the network. And Kidstypike, did you install the new firmware from RPI? It really dropped the temp of my system. https://www.raspberrypi.org/forums/viewtopic.php?f=28&t=243500&p=1490467#p1490467 I see they have a new bootloader too: https://www.raspberrypi.org/forums/viewtopic.php?f=117&t=246027 piCorePlayer a small player for the Raspberry Pi in RAM. Homepage: https://www.picoreplayer.org Please 'donate' (https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=U7JHY5WYHCNRU&lc=GB¤cy_code=USD&bn=PP%2dDonationsBF%3abtn_donateCC_LG%2egif%3aNonHosted) if you like the piCorePlayer paul-'s Profile: http://forums.slimdevices.com/member.php?userid=58858 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Well that's a relief - first thing I tried! I changed the SSID of the new mesh wifi, made a new wpa_supplicant.conf for pCP, and reconnected. The USB DAC now runs in perfect sync with the powerline (wired) Boom without glitches. I also connected the wireless Boom to the new SSID and that also runs in perfect sync with the other two players without glitches. If only I'd come up with a new SSID yesterday when I first installed the things I could have saved a lot of effort. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
w3wilkes wrote: > Dumb question... With the mesh network have you tried restoring the SD > card image like you did when you went back to the Airport Extreme? I haven't done that. I reasoned that that would just put me back to the same place that I started. My backed-up image contains all the information about my original wifi hardware, so just works as soon as I power it up, provided I'm using the Airport Extreme. At that point, if I switch the Airport Extreme for the mesh AP, that's where I was when I first noticed the problem. If I re-image again while the new mesh AP is running, the image would still know all about the Airport. A fresh pCP image might be worth trying though - one that doesn't know anything about my Airport. I can see an evening of testing coming up. It's always the same - any new piece of network kit *always* ends up in at least one evening, and often two, of pulling my hair out before peace and tranquility eventually return. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
bpa wrote: > By glitch I assume a short gap of silence but no audio missed. Exactly - both synced players stop for about half a second, then resume with no missed audio. Thanks for the tips on logging - I'll see what the logs tell me. bpa wrote: > I think having same name might cause problem as some network > characteristic may only be detected/saved when first validated. That's an easy thing to correct and test. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Dumb question... With the mesh network have you tried restoring the SD card image like you did when you went back to the Airport Extreme? Main system - Rock Solid with LMS 7.9.1 Official on WHS 2011 - 2 Duets and Squeeseslave Cabin system - Rock solid with LMS 7.9.1 Official on Win10 Pro - 1 RPi 3 Model B/Hifiberry DAC+ Pro/PiCorePlayer and Squeezeslave w3wilkes's Profile: http://forums.slimdevices.com/member.php?userid=22973 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > disabled the 'maintain sync while playing' option they went noticeably > out of sync much faster than every 37 seconds - even after a few seconds > I could hear the difference. By glitch I assume a short gap of silence but no audio missed. This does seems otbe player buffer running out - very unusual unless using Flac or high rate compressed as player normally buffer at least a minute. It is possible using logging to see fullness of the player audio buffer and the decoded output buffer. For a glitch to occur output would have to be empty (also implies audio buffer is also empty). Example of a stream starting and how buffers are filled up - network.protocol.slimproto set to INFO Code: [19-07-17 15:26:58.3468] Slim::Player::Squeezebox::stream_s (928) Using smart transition mode [19-07-17 15:26:58.3474] Slim::Player::Squeezebox::stream_s (988) Starting decoder with format: f flags: 0x0 autostart: 1 buffer threshold: 255 output threshold: 20 samplesize: ? samplerate: ? endian: ? channels: ? [19-07-17 15:26:58.3494] Slim::Networking::Slimproto::_stat_handler (785) 74:da:38:a6:39:77: STAT-STMf: fullness=0, output_fullness=-1, elapsed=0.000 [19-07-17 15:26:58.3495] Slim::Networking::Slimproto::_stat_handler (785) 74:da:38:a6:39:77: STAT-STMf: fullness=0, output_fullness=-1, elapsed=0.000 [19-07-17 15:26:58.3496] Slim::Networking::Slimproto::_stat_handler (785) 74:da:38:a6:39:77: STAT-STMc: fullness=0, output_fullness=-1, elapsed=0.000 [19-07-17 15:26:58.4528] Slim::Networking::Slimproto::_http_response_handler (554) Squeezebox got HTTP response: HTTP/1.1 200 OK Server: Logitech Media Server (7.9.2 - git-4153ef839) Connection: close Content-Type: audio/x-flac [19-07-17 15:26:58.4995] Slim::Networking::Slimproto::_stat_handler (785) 74:da:38:a6:39:77: STAT-STMs: fullness=1376256, output_fullness=1824768, elapsed=0.000 [19-07-17 15:26:58.5001] Slim::Networking::Slimproto::_stat_handler (785) 74:da:38:a6:39:77: STAT-STMt: fullness=1376256, output_fullness=1824768, elapsed=0.000 [19-07-17 15:26:59.5009] Slim::Networking::Slimproto::_stat_handler (785) 74:da:38:a6:39:77: STAT-STMt: fullness=2097151, output_fullness=3262464, elapsed=0.993 [19-07-17 15:27:00.5015] Slim::Networking::Slimproto::_stat_handler (785) 74:da:38:a6:39:77: STAT-STMt: fullness=2097151, output_fullness=3257080, elapsed=1.998 [19-07-17 15:27:01.0008] Slim::Networking::Slimproto::_stat_handler (785) 74:da:38:a6:39:77: STAT-STMt: fullness=2097151, output_fullness=3263224, elapsed=2.496 > I gave my new mesh network the same name as my old wifi network, so > maybe pCP is remembering something about the old network that isn't > suitable for the new one. Perhaps I should just give the new network a > different name. I think having same name might cause problem as some network characteristic may only be detected/saved when first validated. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
bpa wrote: > LMS sends data to player when player says data has dropped below a > certain level - so for a data stream which has same characteristics - > timing would be constant but higher data rate where data is "consumed" > faster then timing will change. To check if it is related to playing > content try repeatedly playing a file with greatly increased data rate > (e.g. 96Khz vs 44.1khz or Flac vs MP3/AAC). 37 secs could be a > reasonable level to request more data as buffer can hold 2-3 minutes of > audio - but best to check by to see if timing varies when playing a > variety of files each on repeat. > IIRC player timing sync is quite frequent (e.g. every few secs) as part > of status messages. You can enable LMS logging for sync (player.sync) > or slimproto (network.protocol.slimproto) to check on LMS/player > message. Thank you. Yes, I was going to investigate the transcoding options. Given how long the Booms continued playing after various LMS shutdowns yesterday, I suspect they're being sent compressed data, so that's certainly something to investigate. And I think you're right about the player sync data - when I disabled the 'maintain sync while playing' option they went noticeably out of sync much faster than every 37 seconds - even after a few seconds I could hear the difference. And given that that option made no difference to the glitches, the 37 seconds seems more likely to be related to buffer refills. But I can't see an obvious reason why they'd suddenly become an issue with the new mesh wifi? If the player signals that it needs a refill, is that message being blocked or delayed somehow? And why would this only affect playback when two players are synced? As well as trying the RPi wired, I'm also thinking I should completely remove and reinstall the wireless parts of pCP. I gave my new mesh network the same name as my old wifi network, so maybe pCP is remembering something about the old network that isn't suitable for the new one. Perhaps I should just give the new network a different name. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > The regular 37s interval must be significant - is this when LMS sends > new data to the player? Is this the frequency of time syncing checks? LMS sends data to player when player says data has dropped below a certain level - so for a data stream which has same characteristics - timing would be constant but higher data rate where data is "consumed" faster then timing will change. To check if it is related to playing content try repeatedly playing a file with greatly increased data rate (e.g. 96Khz vs 44.1khz or Flac vs MP3/AAC). 37 secs could be a reasonable level to request more data as buffer can hold 2-3 minutes of audio - but best to check by to see if timing varies when playing a variety of files each on repeat. IIRC player timing sync is quite frequent (e.g. every few secs) as part of status messages. You can enable LMS logging for sync (player.sync) or slimproto (network.protocol.slimproto) to check on LMS/player message. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Yes, all my testing so far has been with local content that's stored on an SSD connected to one of the Pi's USB3 ports. I do also share that disk via Samba - I guess I could temporarily disable Samba, just to rule that out. I think my next step will be to run pCP/LMS/Squeezelite on a wired connection, and then try syncing with wired and/or wireless players. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
And your able to play local stored files? I've got similar behavior when lms loses access to music share on server. 1 or 2 single player are ok. More players or syncing the two players causing rebuffering. Solved the share acces and everything is fine again. Btw lms on pi3. Player one boom and one SB2, but problem also with a radio or a pcp player. *SqueezeBoxes:* 1x Transporter (Living room) 1x SB2 (shed), 1x Radio (Kitchen), 1x Boom (Dining room), 1x piCorePlayer (jacuzzi), 1x piCorePlayer (Garden) 1x OSMC + Squeezelite (Movie room), 1x Touch (Study 2), few spare unit's *Server:* LMS on Pi3 7.9.1. on PcP 3.21 *Network:* AVM Fritzbox, Netgear Smart Switch 24p, 3x Ubiquity edwin2006's Profile: http://forums.slimdevices.com/member.php?userid=66926 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Glitches still happen even if I turn off the 'Maintain synchronisation while playing' option on both synced players. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
With three players (Squeezelite + 2 Booms) all playing unsynced I don't get any glitches. If I sync two of them then I get glitches in the synced pair every 37 seconds, except when the current track finishes and the next one starts. The unsynced third player continues without error. The regular 37s interval must be significant - is this when LMS sends new data to the player? Is this the frequency of time syncing checks? chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
bpa wrote: > Do you get glitches when there there is only one node of the mesh > working (i.e. no real mesh just like Airport ) ? that will show if it > is a fundamental incompatibility. Yes - even with just a single node, set up in Access Point mode, I get glitches when syncing players. Pretty sure it was fine with just a single unsynced player. I might try running all three players unsynced, just to isolate the problem. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > That's worth a try. The 4B works perfectly with the Airport Extreme, so > I'd be surprised if that's the problem, but maybe there's in > incompatibility between the 4B wifi and the mesh. > > What puzzles me is how attaching the 4B to the new mesh AP somehow > corrupts LMS so that the glitches continue once the Airport is swapped > back in. There must be a file or a cache that gets updated with the > mesh information (which is why I wondered about packet latency). > Obviously clearing that cache or deleting that file would be quicker > than re-imaging the SD card from a backup, but re-imaging has worked > both times. Do you get glitches when there there is only one node of the mesh working (i.e. no real mesh just like Airport ) ? that will show if it is a fundamental incompatibility. bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Greg Erskine wrote: > Probably a virus. lol ...pre-installed by TP-Link and masquerading as something else, like 'HomeCare'. Maybe TP-Link are a subsidiary of Huawei, and the glitches are when it reports back to base chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
Probably a virus. lol Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
kidstypike wrote: > > Try using a Pi3/LMS with your Mesh, see if you still get glitches? > That's worth a try. The 4B works perfectly with the Airport Extreme, so I'd be surprised if that's the problem, but maybe there's in incompatibility between the 4B wifi and the mesh. What puzzles me is how attaching the 4B to the new mesh AP somehow corrupts LMS so that the glitches continue once the Airport is swapped back in. There must be a file or a cache that gets updated with the mesh information (which is why I wondered about packet latency). Obviously clearing that cache or deleting that file would be quicker than re-imaging the SD card from a backup, but re-imaging has worked both times. chill's Profile: http://forums.slimdevices.com/member.php?userid=10839 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss
Re: [slim] Player synchronisation problems with new mesh wifi
chill wrote: > I had a rush of blood to the head and bought a new mesh wifi 3-pack > during 'Prime Day' (TP-Link Deco M5). Easy enough to set up, and the > wifi signal is a little bit stronger than with my old Apple Airport > Extreme. > > I run LMS on a Raspberry Pi 4 running pCP. I run it wireless - yes, I > know that's not advised but it has a strong signal and it's been totally > reliable to date with the Airport Extreme. It connected ok to the new > wifi and was happily playing through the attached USB DAC. But when I > added in a couple of synced Booms I started to get dropouts - more like > momentary pauses in fact. One Boom is on a powerline adapter, and the > other is next to the new wifi AP with 100% signal strength. I tried > turning off the Booms in turn, and concluded that having either one > synced with the USB DAC caused these glitches. > > After tinkering around for an hour or two I decided to give up and put > the old reliable Airport Extreme back, and here's the odd thing. The > glitches then continued, even though the new mesh AP was powered down. > The only way I could get the system working properly was to restore the > pCP SD card from last night's back up. > > To see whether I was imagining things I repeated the process: > - working fine with Airport Extreme > - swapped to mesh AP -> glitches > - swapped back to Airport Extreme -> still glitches > - restored SD card from previous image -> glitches gone. > > It seems to be related to synchronising players. My suspicion is it has > something to do with network latency, and perhaps the faulty or > unreliable latency information from the mesh AP setup is being > remembered even when the Airport Extreme is swapped back in. > > Can anyone comment on how network latency is measured and implemented? > Can I tweak any settings to solve this? > > My absolute priority is a reliable glitch-free LMS setup, so if I can't > get round this PDQ then I'm going to send the mesh kit back, since it > appears to be incompatible with LMS at some level. I had to turn off > one of the more useful features anyway (802.11r, which allows for fast > handover of mobile devices between APs) because the Booms wouldn't > connect with it enabled. > > Has anyone else experienced (and solved) this? Just a thought, a couple of days ago I was getting momentary dropouts as you describe, when I was syncing my study player (see sig) and a Boom, whilst using a Pi4-4GB as LMS server. I have never had this problem before when using any other flavour of RPi. I am now back using a Pi3B+ for server and the 2 players sync without dropouts. Try using a Pi3/LMS with your Mesh, see if you still get glitches? The Pi4 is now in my spare Pi box, it was getting up to 80°C. *Server - LMS 7.9.2 *Pi4B/pCP 6.0.0 18K library, playlists & LMS cache on SSD (ntfs) *Study -* Pi3B+/pCP 5.0.0/pi screen/HiFiBerry DAC+/jivelite, *Lounge* - Pi2/pCP 5.0.0 > HiFiBerry DIGI+ > AudioEngine DAC1 > AVI DM5 *Dining Room* - Squeezebox Boom *Garage* - Pi3B/Pi screen/HiFiBerry DAC+/pCP 5.0.0 > Edifier R980T *Spares* - 2xTouch, 1xSB3, 1xRadio, 6xRPi kidstypike's Profile: http://forums.slimdevices.com/member.php?userid=10436 View this thread: http://forums.slimdevices.com/showthread.php?t=110765 ___ discuss mailing list discuss@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/discuss