PDA

View Full Version : 5.2 release candidate w/ firmware v.26 testing summary



Mike Uhrich
2004-06-23, 10:32
I get the same behavior described below with a fresh install not saving
selected music or playlist folders. Also, if I use: Options > Set Music
Library Folder or Options > Set Saved Playlist Folder, it doesn't seem to
save the settings either. I have to go under "Server Settings" to get the
directories to change. I'm using 6/21 nightly.

Originally posted by Michael Bird:
"When doing a clean install of a nightly (that is, I removed the previous
version and deleted the SlimServer directory to do a fresh install), the
installer program does not save the selected music folder and playlist
folder that I specify during installation. I have to go in to server
settings and set these after the install. This has happened with at least
the last month of nightlies, maybe farther back."

Mike Uhrich
425.369.2500
v-muhric (AT) Microsoft (DOT) com

-----Original Message-----
From: discuss-bounces (AT) lists (DOT) slimdevices.com
[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Michael Bird
Sent: Wednesday, June 23, 2004 10:18 AM
To: discuss (AT) lists (DOT) slimdevices.com
Cc: 'Kevin Pearsall'
Subject: [slim] 5.2 release candidate w/ firmware v.26 testing summary


Testing report for 5.2 w/firmware v.26, 6/22 nightly build.

System summary:

Server: Windows Server 2003. The only thing running on it other than the OS
is the SlimServer service.
CPU: 2GHz Intel Celeron.
Memory: 512MB DDR.
System drive: 60GB Maxtor system drive.
Music collection drive: Terabyte raid 5 array with Escalade RAID card and
four Western Digital 250GB drives.
Network: Everything is running wired connections with NetGear
routers/switches.
Slim hardware: 1 Squeezebox and 1 SliMP3
Music collection: Approx 43,000 songs, all are LAME-encoded MP3s.

Here's a summary of my experience with the 6/22 nightly:

Firmware update to Squeezebox: No problems here.

Problem with pausing/unpausing the music: Still having the same problem as
before -- if the Squeezebox is paused for more than 30 seconds or so, when
unpausing it plays what is in the buffer and then stops. Just as a side
note, my SliMP3 does NOT have this problem.

Various performance problems:

When the server first builds the tag database, at the very end of the scan,
it becomes unresponsive for several minutes (seems to vary from about 5 to
20 minutes). I've tried this with the tag db turned on and off, and also
with the "look for artwork" option turned on and off, doesn't seem to make
any difference.

With the tag db caching turned on, about every hour or so of continuous
play, the music stops for about 3-4 seconds, then starts again where it left
off. This does NOT happen with the tag db caching turned off. Very strange.

I have been experiencing both of these problems throughout 5.1.6 and 5.2,
and have reported them previously.

During song title searches, the server almost always becomes unresponsive.
Sometimes it becomes unresponsive during artist and album title searches.
Seems like the database searches should be a lot more efficient, given the
fact that I am running a fairly robust dedicated server. This seems less of
a problem (though it still happens sometimes) with the tag db caching turned
on, but I usually have that turned off because of the above problem.

Nuisance bugs:

When doing a clean install of a nightly (that is, I removed the previous
version and deleted the SlimServer directory to do a fresh install), the
installer program does not save the selected music folder and playlist
folder that I specify during installation. I have to go in to server
settings and set these after the install. This has happened with at least
the last month of nightlies, maybe farther back.

After a clean install, the player settings for the SliMP3 default to a
bitrate limit of 64kbps -- that is, the first item in the dropdown. I
haven't checked the prefs file to see what it shows there, I'm just going by
what the web interface says.

Other problems:

The synchronization between the Squeezebox and the SliMP3 still doesn't work
very well. They often start up a second or more apart. This seemed to be
(mostly) fixed for a while pre-5.1.6, but seems worse now. Would like to see
this working. I only have 1 Squeezebox, so I don't know if that sync works
better.

-Michael Bird

vidurapparao
2004-06-23, 13:46
The Library and Playlist folder information are saved in the file
slimserver.pref (in the server subdirectory of the SlimServer
installation on Windows) - not in the Windows registry. If you do an
uninstall *and* delete the SlimServer directory, you will lose this
information on a fresh install. Installing over an existing version will
preserve the file, as will uninstalling, not deleting SlimServer, and
reinstalling.

--Vidur

Mike Uhrich wrote:

>I get the same behavior described below with a fresh install not saving
>selected music or playlist folders. Also, if I use: Options > Set Music
>Library Folder or Options > Set Saved Playlist Folder, it doesn't seem to
>save the settings either. I have to go under "Server Settings" to get the
>directories to change. I'm using 6/21 nightly.
>
>Originally posted by Michael Bird:
>"When doing a clean install of a nightly (that is, I removed the previous
>version and deleted the SlimServer directory to do a fresh install), the
>installer program does not save the selected music folder and playlist
>folder that I specify during installation. I have to go in to server
>settings and set these after the install. This has happened with at least
>the last month of nightlies, maybe farther back."
>
>Mike Uhrich
>425.369.2500
>v-muhric (AT) Microsoft (DOT) com
>
>-----Original Message-----
>From: discuss-bounces (AT) lists (DOT) slimdevices.com
>[mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Michael Bird
>Sent: Wednesday, June 23, 2004 10:18 AM
>To: discuss (AT) lists (DOT) slimdevices.com
>Cc: 'Kevin Pearsall'
>Subject: [slim] 5.2 release candidate w/ firmware v.26 testing summary
>
>
>Testing report for 5.2 w/firmware v.26, 6/22 nightly build.
>
>System summary:
>
>Server: Windows Server 2003. The only thing running on it other than the OS
>is the SlimServer service.
>CPU: 2GHz Intel Celeron.
>Memory: 512MB DDR.
>System drive: 60GB Maxtor system drive.
>Music collection drive: Terabyte raid 5 array with Escalade RAID card and
>four Western Digital 250GB drives.
>Network: Everything is running wired connections with NetGear
>routers/switches.
>Slim hardware: 1 Squeezebox and 1 SliMP3
>Music collection: Approx 43,000 songs, all are LAME-encoded MP3s.
>
>Here's a summary of my experience with the 6/22 nightly:
>
>Firmware update to Squeezebox: No problems here.
>
>Problem with pausing/unpausing the music: Still having the same problem as
>before -- if the Squeezebox is paused for more than 30 seconds or so, when
>unpausing it plays what is in the buffer and then stops. Just as a side
>note, my SliMP3 does NOT have this problem.
>
>Various performance problems:
>
>When the server first builds the tag database, at the very end of the scan,
>it becomes unresponsive for several minutes (seems to vary from about 5 to
>20 minutes). I've tried this with the tag db turned on and off, and also
>with the "look for artwork" option turned on and off, doesn't seem to make
>any difference.
>
>With the tag db caching turned on, about every hour or so of continuous
>play, the music stops for about 3-4 seconds, then starts again where it left
>off. This does NOT happen with the tag db caching turned off. Very strange.
>
>I have been experiencing both of these problems throughout 5.1.6 and 5.2,
>and have reported them previously.
>
>During song title searches, the server almost always becomes unresponsive.
>Sometimes it becomes unresponsive during artist and album title searches.
>Seems like the database searches should be a lot more efficient, given the
>fact that I am running a fairly robust dedicated server. This seems less of
>a problem (though it still happens sometimes) with the tag db caching turned
>on, but I usually have that turned off because of the above problem.
>
>Nuisance bugs:
>
>When doing a clean install of a nightly (that is, I removed the previous
>version and deleted the SlimServer directory to do a fresh install), the
>installer program does not save the selected music folder and playlist
>folder that I specify during installation. I have to go in to server
>settings and set these after the install. This has happened with at least
>the last month of nightlies, maybe farther back.
>
>After a clean install, the player settings for the SliMP3 default to a
>bitrate limit of 64kbps -- that is, the first item in the dropdown. I
>haven't checked the prefs file to see what it shows there, I'm just going by
>what the web interface says.
>
>Other problems:
>
>The synchronization between the Squeezebox and the SliMP3 still doesn't work
>very well. They often start up a second or more apart. This seemed to be
>(mostly) fixed for a while pre-5.1.6, but seems worse now. Would like to see
>this working. I only have 1 Squeezebox, so I don't know if that sync works
>better.
>
>-Michael Bird
>
>
>
>

vidurapparao
2004-06-23, 15:38
Apologies, I didn't see the bit about you specifying the library path in
the installation process. A question: immediately after installation, do
you run SlimServer as a service (by checking "Start Automatically") or
as an application?

--Vidur

Vidur Apparao wrote:

>
> The Library and Playlist folder information are saved in the file
> slimserver.pref (in the server subdirectory of the SlimServer
> installation on Windows) - not in the Windows registry. If you do an
> uninstall *and* delete the SlimServer directory, you will lose this
> information on a fresh install. Installing over an existing version
> will preserve the file, as will uninstalling, not deleting SlimServer,
> and reinstalling.
>
> --Vidur
>
> Mike Uhrich wrote:
>
>> I get the same behavior described below with a fresh install not saving
>> selected music or playlist folders. Also, if I use: Options > Set Music
>> Library Folder or Options > Set Saved Playlist Folder, it doesn't
>> seem to
>> save the settings either. I have to go under "Server Settings" to
>> get the
>> directories to change. I'm using 6/21 nightly.
>>
>> Originally posted by Michael Bird:
>> "When doing a clean install of a nightly (that is, I removed the
>> previous
>> version and deleted the SlimServer directory to do a fresh install), the
>> installer program does not save the selected music folder and playlist
>> folder that I specify during installation. I have to go in to server
>> settings and set these after the install. This has happened with at
>> least
>> the last month of nightlies, maybe farther back."
>>
>> Mike Uhrich
>> 425.369.2500
>> v-muhric (AT) Microsoft (DOT) com
>>
>> -----Original Message-----
>> From: discuss-bounces (AT) lists (DOT) slimdevices.com
>> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Michael Bird
>> Sent: Wednesday, June 23, 2004 10:18 AM
>> To: discuss (AT) lists (DOT) slimdevices.com
>> Cc: 'Kevin Pearsall'
>> Subject: [slim] 5.2 release candidate w/ firmware v.26 testing summary
>>
>>
>> Testing report for 5.2 w/firmware v.26, 6/22 nightly build.
>>
>> System summary:
>>
>> Server: Windows Server 2003. The only thing running on it other than
>> the OS
>> is the SlimServer service.
>> CPU: 2GHz Intel Celeron.
>> Memory: 512MB DDR.
>> System drive: 60GB Maxtor system drive. Music collection drive:
>> Terabyte raid 5 array with Escalade RAID card and
>> four Western Digital 250GB drives.
>> Network: Everything is running wired connections with NetGear
>> routers/switches.
>> Slim hardware: 1 Squeezebox and 1 SliMP3
>> Music collection: Approx 43,000 songs, all are LAME-encoded MP3s.
>>
>> Here's a summary of my experience with the 6/22 nightly:
>>
>> Firmware update to Squeezebox: No problems here.
>>
>> Problem with pausing/unpausing the music: Still having the same
>> problem as
>> before -- if the Squeezebox is paused for more than 30 seconds or so,
>> when
>> unpausing it plays what is in the buffer and then stops. Just as a side
>> note, my SliMP3 does NOT have this problem.
>>
>> Various performance problems:
>>
>> When the server first builds the tag database, at the very end of the
>> scan,
>> it becomes unresponsive for several minutes (seems to vary from about
>> 5 to
>> 20 minutes). I've tried this with the tag db turned on and off, and also
>> with the "look for artwork" option turned on and off, doesn't seem to
>> make
>> any difference.
>>
>> With the tag db caching turned on, about every hour or so of continuous
>> play, the music stops for about 3-4 seconds, then starts again where
>> it left
>> off. This does NOT happen with the tag db caching turned off. Very
>> strange.
>>
>> I have been experiencing both of these problems throughout 5.1.6 and
>> 5.2,
>> and have reported them previously.
>>
>> During song title searches, the server almost always becomes
>> unresponsive.
>> Sometimes it becomes unresponsive during artist and album title
>> searches.
>> Seems like the database searches should be a lot more efficient,
>> given the
>> fact that I am running a fairly robust dedicated server. This seems
>> less of
>> a problem (though it still happens sometimes) with the tag db caching
>> turned
>> on, but I usually have that turned off because of the above problem.
>>
>> Nuisance bugs:
>>
>> When doing a clean install of a nightly (that is, I removed the previous
>> version and deleted the SlimServer directory to do a fresh install), the
>> installer program does not save the selected music folder and playlist
>> folder that I specify during installation. I have to go in to server
>> settings and set these after the install. This has happened with at
>> least
>> the last month of nightlies, maybe farther back.
>>
>> After a clean install, the player settings for the SliMP3 default to a
>> bitrate limit of 64kbps -- that is, the first item in the dropdown. I
>> haven't checked the prefs file to see what it shows there, I'm just
>> going by
>> what the web interface says.
>>
>> Other problems:
>>
>> The synchronization between the Squeezebox and the SliMP3 still
>> doesn't work
>> very well. They often start up a second or more apart. This seemed to be
>> (mostly) fixed for a while pre-5.1.6, but seems worse now. Would like
>> to see
>> this working. I only have 1 Squeezebox, so I don't know if that sync
>> works
>> better.
>>
>> -Michael Bird
>>
>>
>>
>>

vidurapparao
2004-06-23, 23:37
I checked in fixes for both problems:
1) It turns out that the installer was writing out the initial
slimserver.prefs file *after* starting the windows service. As a result,
the service lost the values set by the installer. I switched the
ordering of events in the installer.
2) The SlimServer application was using old pref names for setting the
music and playlist directories. I changed them to the current ones and
everything's good.

Mike and Michael, could you confirm that these fixes work for you with
the 6/24 nightly? Thanks for pointing these out!

--Vidur

Vidur Apparao wrote:

>
> Apologies, I didn't see the bit about you specifying the library path
> in the installation process. A question: immediately after
> installation, do you run SlimServer as a service (by checking "Start
> Automatically") or as an application?
>
> --Vidur
>
> Vidur Apparao wrote:
>
>>
>> The Library and Playlist folder information are saved in the file
>> slimserver.pref (in the server subdirectory of the SlimServer
>> installation on Windows) - not in the Windows registry. If you do an
>> uninstall *and* delete the SlimServer directory, you will lose this
>> information on a fresh install. Installing over an existing version
>> will preserve the file, as will uninstalling, not deleting
>> SlimServer, and reinstalling.
>>
>> --Vidur
>>
>> Mike Uhrich wrote:
>>
>>> I get the same behavior described below with a fresh install not saving
>>> selected music or playlist folders. Also, if I use: Options > Set
>>> Music
>>> Library Folder or Options > Set Saved Playlist Folder, it doesn't
>>> seem to
>>> save the settings either. I have to go under "Server Settings" to
>>> get the
>>> directories to change. I'm using 6/21 nightly.
>>>
>>> Originally posted by Michael Bird:
>>> "When doing a clean install of a nightly (that is, I removed the
>>> previous
>>> version and deleted the SlimServer directory to do a fresh install),
>>> the
>>> installer program does not save the selected music folder and playlist
>>> folder that I specify during installation. I have to go in to server
>>> settings and set these after the install. This has happened with at
>>> least
>>> the last month of nightlies, maybe farther back."
>>>
>>> Mike Uhrich
>>> 425.369.2500
>>> v-muhric (AT) Microsoft (DOT) com
>>>
>>> -----Original Message-----
>>> From: discuss-bounces (AT) lists (DOT) slimdevices.com
>>> [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Michael
>>> Bird
>>> Sent: Wednesday, June 23, 2004 10:18 AM
>>> To: discuss (AT) lists (DOT) slimdevices.com
>>> Cc: 'Kevin Pearsall'
>>> Subject: [slim] 5.2 release candidate w/ firmware v.26 testing summary
>>>
>>>
>>> Testing report for 5.2 w/firmware v.26, 6/22 nightly build.
>>>
>>> System summary:
>>>
>>> Server: Windows Server 2003. The only thing running on it other than
>>> the OS
>>> is the SlimServer service.
>>> CPU: 2GHz Intel Celeron.
>>> Memory: 512MB DDR.
>>> System drive: 60GB Maxtor system drive. Music collection drive:
>>> Terabyte raid 5 array with Escalade RAID card and
>>> four Western Digital 250GB drives.
>>> Network: Everything is running wired connections with NetGear
>>> routers/switches.
>>> Slim hardware: 1 Squeezebox and 1 SliMP3
>>> Music collection: Approx 43,000 songs, all are LAME-encoded MP3s.
>>>
>>> Here's a summary of my experience with the 6/22 nightly:
>>>
>>> Firmware update to Squeezebox: No problems here.
>>>
>>> Problem with pausing/unpausing the music: Still having the same
>>> problem as
>>> before -- if the Squeezebox is paused for more than 30 seconds or
>>> so, when
>>> unpausing it plays what is in the buffer and then stops. Just as a side
>>> note, my SliMP3 does NOT have this problem.
>>>
>>> Various performance problems:
>>>
>>> When the server first builds the tag database, at the very end of
>>> the scan,
>>> it becomes unresponsive for several minutes (seems to vary from
>>> about 5 to
>>> 20 minutes). I've tried this with the tag db turned on and off, and
>>> also
>>> with the "look for artwork" option turned on and off, doesn't seem
>>> to make
>>> any difference.
>>>
>>> With the tag db caching turned on, about every hour or so of continuous
>>> play, the music stops for about 3-4 seconds, then starts again where
>>> it left
>>> off. This does NOT happen with the tag db caching turned off. Very
>>> strange.
>>>
>>> I have been experiencing both of these problems throughout 5.1.6 and
>>> 5.2,
>>> and have reported them previously.
>>>
>>> During song title searches, the server almost always becomes
>>> unresponsive.
>>> Sometimes it becomes unresponsive during artist and album title
>>> searches.
>>> Seems like the database searches should be a lot more efficient,
>>> given the
>>> fact that I am running a fairly robust dedicated server. This seems
>>> less of
>>> a problem (though it still happens sometimes) with the tag db
>>> caching turned
>>> on, but I usually have that turned off because of the above problem.
>>>
>>> Nuisance bugs:
>>>
>>> When doing a clean install of a nightly (that is, I removed the
>>> previous
>>> version and deleted the SlimServer directory to do a fresh install),
>>> the
>>> installer program does not save the selected music folder and playlist
>>> folder that I specify during installation. I have to go in to server
>>> settings and set these after the install. This has happened with at
>>> least
>>> the last month of nightlies, maybe farther back.
>>>
>>> After a clean install, the player settings for the SliMP3 default to a
>>> bitrate limit of 64kbps -- that is, the first item in the dropdown. I
>>> haven't checked the prefs file to see what it shows there, I'm just
>>> going by
>>> what the web interface says.
>>>
>>> Other problems:
>>>
>>> The synchronization between the Squeezebox and the SliMP3 still
>>> doesn't work
>>> very well. They often start up a second or more apart. This seemed
>>> to be
>>> (mostly) fixed for a while pre-5.1.6, but seems worse now. Would
>>> like to see
>>> this working. I only have 1 Squeezebox, so I don't know if that sync
>>> works
>>> better.
>>>
>>> -Michael Bird
>>>
>>>
>>>
>>>