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
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
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:
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
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,
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
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
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
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
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
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
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
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
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
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
vl805
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
>
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
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
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 -*
chill wrote:
> >
Code:
> > sudo ./vl805
> >
>
> The original instructions are 'here'
> (https://www.raspberrypi.org/forums/viewtopic.php?f=28=243500=1490467#p1490467).
Hmm... getting "command not found", what does that mean?
27708
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=243500=1490467#p1490467).
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):
>
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
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
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.
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
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
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.
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
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
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
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
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
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
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 -
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
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
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:
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
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.
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
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
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
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
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
45 matches
Mail list logo
