Bug 10751 - Detailed setting for pre caching of artwork
: Detailed setting for pre caching of artwork
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Artwork
: unspecified
: All All
: -- enhancement with 2 votes (vote)
: Future
Assigned To: Andy Grundman
:
Depends on: 9919
Blocks:
  Show dependency treegraph
 
Reported: 2009-01-19 04:04 UTC by Anders Markstrom
Modified: 2016-11-27 20:47 UTC (History)
7 users (show)

See Also:
Category: Feature


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anders Markstrom 2009-01-19 04:04:19 UTC
Today Squeezecenter is pre caching the following artwork "100x100_p", "50x50_o"
and "56x56_p". 

It would be useful with a detailed setting where you can specify heigh, width and resizeMode that you would like to add to the pre caching.

To lower level of knowledge needed to make the settings they could also be selectable by skin, plugin, device, application, etc so that a selection of "iPeng" would add "75x75_p" and "Controller" add "56x56_p" to the pre cache.
Comment 1 Michael Herger 2009-08-19 00:02:13 UTC
Anders - could you please comment on https://bugs-archive.lyrion.org/show_bug.cgi?id=9757#c19 It should cover what you're asking for.
Comment 2 Michael Herger 2009-08-20 02:51:56 UTC
Moving some of bug 9757 over here:

After some discussion with Ben we came to the conclusion that a static list of
sizes won't do. A minor change on the SqueezePlay side of things and it's a
waste of resources. We must come up with something more dynamic. Here goes my
suggestion:

Let's introduce a registerartworkparams or similar command which allows to
register artwork size and resizing parameters. Any software requiring artwork
in a given size (Squeezeplay desktop & Controller, iPeng, your greatest and
latest plugin) can tell SC to pre-cache a list of given artwork types:

registerartworkparams jive ['120x120_m','300x140_m.jpg']

I'd add the client type to allow updating this setting. If we had eg. the
following defaults:

{
   web => ['50x50_o.jpg','100x100_o.jpg'],
   jive => ['120x120_m','300x150_m.jpg'],
}

the client could specifically update its own parameters without invalidating
the others, or end up in a ever growing list of formats. The caller just has to
make sure it provides the full list of formats it wants.

The client type isn't used but for this update filtering. Nor is the default
list exhaustive. Any app/plugin could register its own sizes, eg. iPeng. This
would allow to start with a minimum default set, but allow for growth with new
apps as needed.
Comment 3 Michael Herger 2016-11-27 20:47:23 UTC
Implemented in 7.9