|
#21
|
|||
|
|||
|
Ahh, so you did.
Well, I was still being general
|
|
#22
|
|||
|
|||
|
A larger cache could help in situations where there are infrequent long bursts of noise.
For example, if there is a three second buffer and a five second fierce burst of noise, the audio is at risk. If the buffer was six seconds and happened to be full at the start of the five second burst, the music would survive. The best plan would be to log the cache performance for a large block of users. Based on this survey, one could make an informed decision about the usefulness of a deeper cache. It is a slightly different database, but I believe that SONOS support could survey cache performance from the database of submitted diagnostics. But, one must be careful about any conclusions because this is similar to a survey of patients in a hospital -- it is difficult to make valid inferences about the general population based on a skewed sample. |
|
#23
|
|||
|
|||
|
Quote:
My Sonos hasn't been too bad lately - until today, it's been mostly unusable for any complete song. ![]() I've have the 1001 error which I seem to get everytime I try to add songs to the queue - works second time around though. This can't be a disk spin down issue because it's already playing music at the time Ironically, for the first time ever, I've had the ''network connection speed insufficient to maintain playback'. Then I also had a track stop and was told it wasn't encoded correctly. Never stopped it playing before. It stutters for a bit or just stops and displays the first song in the playlist. Sometimes it thinks it's still playing (time bar still moving) but it's not. It's getting embarrassing now when guests just say 'There it goes again'. Did the usual reboots etc. too. Submitted a couple of diagnostics again (2145703 & 2145751) - will raise an incident against them now. Last edited by sjw; Jul 22nd, 2012 at 01:07 PM. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|