[EMAIL PROTECTED] wrote:
> On Tue, 27 May 2008 18:13:41 CDT, stuart wrote:
>> Hi...
>>
>> I've gotten to a point where I think my private version of mclient is 
>> stable with SqueezeCenter 7.0.x.  Actually I think this combination 
>> works better then any previous mclient / SqueezeCenter(aka SlimServer) 
>> combination.
>>
>> However, I have not made many provisions for earlier versions of SlimServer.
>>
>> I suspect if people are not running 7.0.x they are running 6.5.4 (last 
>> SlimServer release) or 6.3.0 (what Debian is currently offering - wow, 
>> that's old!).
>>
>> So, here's my thinking:  If everyone is running 7.0.x I don't have to 
>> spend time fixing the code to run older versions.  I can go do other 
>> stuff - yea!
>>
>> On the other hand, if there are a lot of 6.5.4 and / or 6.3.0 users out 
>> there, I'll put in some time to at least ensure the mvpmc box does not 
>> reset.
>>
>> So...  what are you running?
>>
>> (Maybe someone knows how to set up a poll somewhere for this sort of 
>> question?)
>>
>> ...thanks
>>
> 
> I am running 6.5.1 under FreeNAS.  What is the motivation to upgrade?
> 
> Jon

Hi Jon...

Ehr, are you running on some light weight embedded processor device like 
a slug?  What is FeeNAS usually run on?

If that's the case, and you are happy with 6.5.1, perhaps it would be 
easier to work on making mclient more universal then it would be to 
upgrade you to 7.0.x.

Isn't 6.5.4 the latest slimserver version?

-----
Anyways, Motivation:

It appears the image manipulation is much improved - probably because of 
the new squeezebox duet from logitech.  Regardless, asking for images of 
a particular size, for instance, is as easy as making up a URL with 
dimensions as part of the file name.  Now the album cover browser 
performs at a much quicker pace loading images of only 100 by 100 pixels 
regardless of the original image size.  Add to that, I'm now caching the 
images to a depth of 100 covers locally.

Also, there is better support for using images of different formats. 
The meta data supplied by SqueezeCenter is correct for different formats 
such an PNG, JPEG and GIF. Locally, I have changed to code which handles 
all three.

This arrangement, however, handles the default "no album cover" image. 
This may not seam to be a problem, but the image covers up screen space 
used for the title of albums that have no image.  SqueezeCenter 7.0.x 
provides a solution by allowing us to indirectly find albums w/no 
covers.  Now we can skip pulling the album covers for such albums. (It 
was serendipities this was not a problem before - since this default 
image was a PNG and we couldn't handle PNGs we didn't display it.)

-----
Other fixes...

It appears (more evident in 7.0.x) that the tag fields in CLI responses 
can come and go depending on the situation and are not necessarily in a 
fixed order.  So the album and title CLI queries have been re-written to 
handle these situations.  The fall out is that mclient can handle the 
"scanning" tag field which pops up during the rescanning of your album 
collection.  Up till now, I believe mclient would reset if used during a 
rescanning session.






-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to