I tried running it from the SB1 using the remote control under
extras-->network test and got the message "Not supported on this
player" maybe because it is a SB1. I'll try from the computer menu I
guess.
--
icdsgnr
icd
>> Sadly I cannot run the network performance plugin as it is not
>> compatable with the beta version 7.0.
You'll find it in the help window.
___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/discuss
icdsgnr;248692 Wrote:
> Sadly I cannot run the network performance plugin as it is not
> compatable with the beta version 7.0.
I believe it's built into SS/SC and has been for a while now. I don't
have my SC7 fired up right now but I would be surprised if it wasn't
there.
--
Mark Lanctot
---
Just to make you all feel a bit worse.
My library is 25k tracks (all lossless) and I often run wireless for
both hops. I've never had music skipping (well, not for a few years
anyway). A scan take about 1 hour 20 minutes (and this with the
majority of the music held on USB 2 connected disks). Sli
icdsgnr wrote:
> How do I give feedback to the folks updating the software?
In the beta forum
--
Pat Farrell
http://www.pfarrell.com/
___
discuss mailing list
discuss@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/discuss
Ok maybe I was delusional. The problem seems to be unrelated to my
wireless network connection controling the server ... The same problem
occurs when I run the web browser from the server directly. It is
consistant and repeatable. Sadly I cannot run the network performance
plugin as it is not c
whoops, my math was way off. 44.1kHz sample rate * 16 bits * 2 channels
= 1.41Mbit/s. 2 seconds only requires 2.8Mbits of buffer. Your compare
link obviously implies I have ~ 1 sec of buffering for uncompressed
data. SB2 and SB3, having more than 10x that buffering, would not see
this problem.
icdsgnr;248607 Wrote:
> I know nothing about the internals of the SB1, but it would seem that it
> wouldn't take much buffering in the box to avoid minor streaming
> interruptions. For example, 2 seconds worth of 16 bits * 2 channels *
> 1.4Mb/sec would imply a need of only ~ 90Mbits or ~ 11MB o
I actually think it has to do with my crumby linksys router. I forgot
to tell you that I was accessing the server via a laptop with a
wireless connection while the SB1 is hardwired to the router. It seems
that the problem occurs only when the web browser updates with the newly
highlighted song.
slimkid;248502 Wrote:
> Also, firmware version seems low for the server version
Actually it looks like he has an SB1, that's the last firmware
version.
icdsgnr, sounds like maybe your server is choking. How much RAM do you
have, and is there enough free?
You can diagnose whether it's server p
icdsgnr;248472 Wrote:
> I have a similar problem (may be related?) using squeezecenter 7.0.
> Each song in the play list will hiccup (mute) for a 1/2 second about 2
> seconds into the song, precisely when the new song is highlighted(late)
> in the gui.
>
> ...
>
> Player InformationName: Squ
My collection 94,000+ tracks normally requires 3-4 hours in order to
index with MIP & Squeezecenter.
During the scan, I've learned best to just leave the interface alone,
else the lock-ups occur.
SqueezeCenter Version: 7.0 - 15125 - Windows XP - EN - cp1252
Perl Version: 5.8.8 MSWin32-x86-multi-t
I have a similar problem (may be related?) using squeezecenter 7.0.
Each song in the play list will hiccup (mute) for a 1/2 second about 2
seconds into the song, precisely when the new song is highlighted(late)
in the gui. If I play a song from the "left" panel directly, without a
playlist, or i
13 matches
Mail list logo
