Given the size of Slim Devices as a company, I feel like they do an adequate level of testing prior to release.  Do you really think many other companies would even bother to support a product as old as the slimp3?

SlimServer is supported for a wide variety of platforms.  It is impossible for them to test all platforms under all configurations.  And even two people with the same platforms and the same set of devices may observe different problems based on different music libraries, or based on what else they have installed on their OS, etc.

The only way to be sure that the new version work on your individual configuration is to try it, and report the problems that you find.  If you are not willing to do this, then you should stay at a level that works for you.  Nobody is forcing you to upgrade -- the devices will continue to operate as before at your previous software level.

In an ideal world SD could catch every bug before it was released.  As it is, they do their best.  For many people on this list, 6.2 works fine, myself included.  This is true even for some who use slimp3, as you have seen in the replies to your post.

So if your goal is to be able to move up to 6.2 and have it work, you need to invest some of your own time.  Otherwise, continue to run your previous level.  I don't see that you have a legitimate beef here.  I can see why you would want to vent, but I hope you can see why venting isn't going to solve the problem you are facing.  Only reporting the bugs that you observe will do that.

On 10/31/05, Bonesteel <[EMAIL PROTECTED] > wrote:

Ben Sandee Wrote:
> On 10/31/05, snarlydwarf <snarlydwarf.1xsghc (AT) no-mx (DOT)
> forums.slimdevices.com>
> wrote:
> >
> >
> > Maybe this is just a WAG...
> >
> > But doesn't the Slimp3 have a virtually-non-existent buffer?
> >
> > And doesn't 6.2 require a full database rebuild when it is first
> > installed?
> >
> > And doesn't that tend to drag down the machine that the server runs
> > on...
> >
> > (See where I'm going?)
> >
> > Is it possible that the "problem" is that the buffer underruns while
> > the database is being rebuilt?
>
>
> Why are you bothering to help him? This guy obviously just wants to
> complain
> and isn't really looking for answers or he would have asked for help
> rather
> than making declarative statements as to how unsatisfactory the new
> software
> is. There are plenty of people using SliMP3's and SlimServer 6.2
> (myself
> included, two SliMP3's); if he has any desire to get this working he
> will be
> more constructive and less inflamatory in the future.
>
> BTW, I suspect that many of the most helpful and knowledgeable people
> with
> respect to SlimServer have actually abandoned the main support forum
> because
> of threads like this. It must be frustrating to volunteer your help
> only get
> constantly see people who can't be bothered to help themselves flame
> the
> product that they've worked so hard on.
>
> Ben
>
> Ben

Well, Ben,

I have had this product since it first came out, and have supported it
since then.

Clearly from my post and others in regard to 6.2 it is not ready for
prime time.  ANY process that consistently takes 65-70% of CPU is not
properly written.

I can start the same exact box running 6.0.2 of Slim Server and it
scans and prepares the library with low CPU impact and minimal start up
time.  On the exact same box 6.2 brings it to it's knees without
actually ever getting to the point where it can be usable.  Even
changes between configuration settings while scanning is going on take
forever, eventually hanging without response.  On 6.0.2 they turn
around in a matter of seconds.

I personally don't feel I should have to spend my time and effort
debugging or tracking down issues with this software when presumably it
is a standard release where at least a basic level of performance should
be supported.  Is it written in the product description for the SLIMP3
that I should be prepared to debug for myself each release of the
SlimServer software?  I think not.

If you look at the other posts here you will see I am not alone with
issues on 6.2.

My guess is that the additional features were added to this release
resulting in the poor performance.

You can complain about my so called "flame" all you wish, but if all
other variables remain the same and 6.0.2 works fine yet 6.2 does not,
there's a problem with the SW.  I don't have the time to waste on these
sorts of beta releases.  I'd rather be listening to music.

Jon


--
Bonesteel
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss

Reply via email to