PDA

View Full Version : "EMPTY" when browsing



Rich Freedman
2005-04-04, 11:42
I'll start off by saying that I love my new SB2, and am very grateful to
everyone at slim devices and in the open-source community who has worked so
hard on the SB.
What follows is in the spirit of wanting this product to succeed, and of
wanting to help make it do so.

That said, I think that the server software needs a lot of work.

I agree wholeheartedly with the need for a solid set of basic functionality
vs. lots of new features.
This is my main complaint with most commercial software too - lots of
features, but questionable basic functionality.

I just got my SB2 on Friday (3 days ago), and am running slimserver 6.0. (on
Windows XP)
I have never run any of the earlier versions, so I don't have anything to
compare it to, but I understand that the code is now about 3 years old?
While the server does have lots of features, it seems that it has a
relatively high number of bugs in the basic functionality.
So far, in three days, I've seen:
- Server crashes when attempting to play a specific external stream
(RadioIO Classical)
- Wrong entry displayed in "now playing" while using a playlist (off
by three entries, for entire song)
- A mode where the player becomes inoperative, and the date/time on
the display changes rapidly, until the player is power-cycled.
- The player stops playing at the end of every song, while using a
playlist.

None of these problems, except the first, are consistently reproducable.
All but the first seem to me to be problems with basic functionality -
external streams are nice, but I consider them a 'feature'.

I'm willing to help where I can, though I'm not (yet) intimately familiar
with Perl.
Please forgive me if I am out of line here, but I'd like to suggest that,
once the hubub around the new release settles down, a small core of
developers, whether from SD or the open-source community, take a breather
from both general single-issue bug-fixing and new feature production, and
analyze the existing code base for stability and maintainability issues.
Then these issues could be addressed. Once the base is stable (the music
plays, the music continues to play, and the player shows the song that is
actually playing, for example), then everyone could proceed with bug fixing
additional features and adding new ones.

Again, despite the learning curve, I'm more than willing to help with all of
the above.

P.S. Do I understand from earlier messages on the list that the server code
is single-threaded?
If so, this explains a lot of the behavior that I have seen, and seems like
an obvious place to try to improve performance and scalability.....

--------------------------------------------------
Rich Freedman
Senior Software Engineer
Cross Current Corporation
http://www.crosscurrent.com
--------------------------------------------------


>Date: Mon, 4 Apr 2005 17:17:20 +0100
>From: "Patrick Dixon" <patrick.dixon (AT) at-view (DOT) co.uk>
>Subject: [slim] "EMPTY" when browsing
>To: "Slim Devices Discussion" <discuss (AT) lists (DOT) slimdevices.com>
>
>Jack
>
>I don't doubt that it's a major project to move away from Perl, but IME of
troubleshooting development projects, sometimes you do have to take a step
backwards to go further forwards. (I don't know enough to suggest that
that's the case here, I hasten to add).>
>
>I take your point about the overkill of today's hardware, but that's
exactly what's produced all that large, slow, resource hungry un-managable
code out there isn't it? >Lean & Mean (TM), I say ;-)
>
>The thing is, I'm running a XP on a 2.5G P4 with 256M RAM (not enough I
know), with a test db of less that 400 songs and Slimserver with Softsqueeze
frequently pauses playing if I pull up a page on the web. The HTML
interface and the fishbone skin in particular is really excellent, but the
refresh is painfully slow and bit clunky. My >concern is that if the
average 'joe' tests out slimserver on his windows computer before buying a
Squeezebox, and gets the same results, he probably won't bother - and that
would be a real shame.
>
>To me it just seems a bit counter-productive to be adding new features on
top, if the basic code isn't fast and clean. I can put up with a few bugs,
but the music has to keep playing!
>
>Anyway, I think my SB2 might arrive tomorrow; I'm really looking forward to
it and I know just how hard everyone at slim devices has worked to get it
(and the software to run it) to me. So thanks!

Jack Coates
2005-04-04, 12:28
Rich Freedman wrote:
....
> I'm willing to help where I can, though I'm not (yet) intimately familiar
> with Perl.
> Please forgive me if I am out of line here, but I'd like to suggest that,
> once the hubub around the new release settles down, a small core of
> developers, whether from SD or the open-source community, take a breather
> from both general single-issue bug-fixing and new feature production, and
> analyze the existing code base for stability and maintainability issues.
> Then these issues could be addressed. Once the base is stable (the music
> plays, the music continues to play, and the player shows the song that is
> actually playing, for example), then everyone could proceed with bug fixing
> additional features and adding new ones.
>
> Again, despite the learning curve, I'm more than willing to help with all of
> the above.
>
> P.S. Do I understand from earlier messages on the list that the server code
> is single-threaded?
> If so, this explains a lot of the behavior that I have seen, and seems like
> an obvious place to try to improve performance and scalability.....

Hi,

yes, that's correct.

http://slimdevices.com/dev_resources.html to get started. You'll want a
subversion client: http://subversion.tigris.org/project_packages.html

--
Jack at Monkeynoodle dot Org: It's a Scientific Venture...
Riding the Emergency Third Rail Power Trip since 1996!