[Bug] cover/artwork

[Whiskey]

Well compress images is time consuming and the unwritten rule is still don't compress images unless you don't have to, i actually once looked in to if it was possibly to do it automatic whit powershell but i never made that script done.

I think i come that far so i could put out the image from the files "i have all my artworks embedded in etch file" and after that i think i turned in to some problems and never looked in to it closer.

[simoncn]

As you say, compressing images is time-consuming. A single browse request from the control point can cause 50 or 100 images to be sent by the server. The time laken to downsize all these images would severely impact the responsiveness of MinimServer.

Another issue is the quality of the downsized image. The Java runtime has code to downsize images but the quality of the downsized image is poor. Various workarounds have been suggested for this but none of them matches the quality of the original.

An offiline image converter can produce high-quality downsized images. As this conversion is not done in real time, it doesn't impact the responsiveness of browsing using MinimServer.

For these reasons, it is unlikely that MinimServer will add support for on-the-fly image downsizing.

[Whiskey]

Time-consuming for Java you mean, how could that be would it not compress it one by one on request "what that i mean when the track is used" and not do everyone at once at it sounds on you but you the Java expert and know this better for sure

Okay so it is a poor quality sure but is that really a valid reason to ignore it? I have hard to see that it can't be seen on the display that actually shows the image i mean its really small display and have really hard to think that anyone would notice it.

[simoncn]

Browsing through a list of albums causes MinimServer to send the cover picture for each album. A control point typically requests 50 or 100 albums at a time, then renders the pictures for all these albums. All this happens before the user selects an album for playing. So MinimServer could be compressing 50 or 100 images for a single browsing action (not just one image when playing a track).

When the user selects an album for playing, most control points show a large image on the Now Playing screen. Poor quality compression of this image would be unacceptable to the user.

When the user sends an image to the control point, it doesn't know whether it will only be used for a thumbnail while browsing or also used as a large mage while playing the album. A compression scheme suitable for the former would not be suitable for the latter.

[Whiskey]

Thanks for explain that, why could not be optional to use thumbnail as the artwork that is used by the streamer if its already created?

To be honest i think that would be good, if it looks good on the phone it would look good on the streamer as the screen is really small.

[simoncn]

The server sends a single image to the control point for all purposes.

For your streamer and control point, it sounds like using a thumbnail image for "now playing" artwork would be OK, unless your control point app shows "now playing" artwork as a larger image.

For other control points, using a thumbnail image for "now playing" artwork is definitely not OK. MinimServer has to cater for all control points and streamers, not just your setup.

[Peter StreamMagic]

(07-03-2020 20:24)Whiskey Wrote:  

(07-03-2020 17:51)simoncn Wrote:  Browsing through a list of albums causes MinimServer to send the cover picture for each album. A control point typically requests 50 or 100 albums at a time, then renders the pictures for all these albums. All this happens before the user selects an album for playing. So MinimServer could be compressing 50 or 100 images for a single browsing action (not just one image when playing a track).

When the user selects an album for playing, most control points show a large image on the Now Playing screen. Poor quality compression of this image would be unacceptable to the user.

When the user sends an image to the control point, it doesn't know whether it will only be used for a thumbnail while browsing or also used as a large mage while playing the album. A compression scheme suitable for the former would not be suitable for the latter.

Thanks for explain that, why could not be optional to use thumbnail as the artwork that is used by the streamer if its already created?

To be honest i think that would be good, if it looks good on the phone it would look good on the streamer as the screen is really small.

Which controlpoint are you using?

[Whiskey]

I am not sure what you people mean whit control point, is it the middle between the streamer and the server?

Then it would be "HiFi-Cast" is an android application

And the streamer is as i already told an "Cambridge Audio 851n"

[Peter StreamMagic]

(07-03-2020 23:33)Whiskey Wrote:  

(07-03-2020 22:58)Peter StreamMagic Wrote:  

(07-03-2020 20:24)Whiskey Wrote:  

(07-03-2020 17:51)simoncn Wrote:  Browsing through a list of albums causes MinimServer to send the cover picture for each album. A control point typically requests 50 or 100 albums at a time, then renders the pictures for all these albums. All this happens before the user selects an album for playing. So MinimServer could be compressing 50 or 100 images for a single browsing action (not just one image when playing a track).

When the user selects an album for playing, most control points show a large image on the Now Playing screen. Poor quality compression of this image would be unacceptable to the user.

When the user sends an image to the control point, it doesn't know whether it will only be used for a thumbnail while browsing or also used as a large mage while playing the album. A compression scheme suitable for the former would not be suitable for the latter.

Thanks for explain that, why could not be optional to use thumbnail as the artwork that is used by the streamer if its already created?

To be honest i think that would be good, if it looks good on the phone it would look good on the streamer as the screen is really small.

Which controlpoint are you using?

I am not sure what you people mean whit control point, is it the middle between the streamer and the server?

Then it would be "HiFi-Cast" is an android application

And the streamer is as i already told an "Cambridge Audio 851n"

Yes thats correct, in this case HiFi-cast on your phone or tablet is the app that "controls" your system.
Do you use both phone and tablet?

[Whiskey]

No i only use my mobile phone as control point