Thumbs quality and height seems not to work (?)

[Jobenvil]

System information

• Picapport version: PicApport V8.3.0 (48444 Fotos verfügbar) Headless Version

• Operating system: Ubuntu 19.10 (GNU/Linux 5.3.0-53-generic x86_64)

• Java version: openjdk version "11.0.6" 2020-01-14 | OpenJDK Runtime Environment AdoptOpenJDK (build 11.0.6+10) | Eclipse OpenJ9 VM AdoptOpenJDK (build openj9-0.18.1, JRE 11 Linux amd64-64-Bit Compressed References 20200122_441 (JIT enabled, AOT enabled)

• Proxy server: nginx nginx/1.17.10 and without proxy

• Client: Version 83.0.4103.61 (Offizieller Build) (64-Bit) Bildschirm 1920x1080 dpr=1.0 pysical=1920x1080

• Language: UTF8

After playing around with the following parameters:

foto.thumb.quality=1.0      # but also 0.90

foto.jpg.quality=1.0        # but also 0.90

foto.jpg.scalemethod=ultra  # but also quality

thumbs.mode=2               # but also 1

thumbs.height=300           # but also 180, 200, 300

 

I came up that either I made or configured something wrong or not considered anything but I cannot see a difference in the thumbnail quality & height at all.

Later on, I changed the height of the thumbs incrementaly but still the same "visual" size. I restarted Picapport after every config change. The INFO logs doesn't show anything invalid with the values.

Any hint will be appreciated. 

[Micke Pe]

foto.thumbs.quality and thumbs.height are settings for the crawler who creates the Files.

If you would like to change the visual size, look at client.css.thumb.height instead.

The quality setting should be at least as high as the client setting.

[Jobenvil]

Thanks Mike, but unfortunatedly you are hinst are too smart for me :-)

foto.thumbs.quality and thumbs.height are settings for the crawler who creates the Files.

Clear. But, are not these created files, the showed one in my browser? If not, for what does it make sense to configure them (foto.thumb.quality=1.0, foto.jpg.quality=1.0)on piccaport.properties if this is only for the crawler and not for the client/browser? I don't get the point.

If you would like to change the visual size, look at client.css.thumb.height instead.

You mean that there is the possibility of doing this e.g.:  

client.css.thumb.height=300

on the piccaport.properties file?

The quality setting should be at least as high as the client setting.

How is possible to achieve that? I don't know at which sides I have to configure what? I mean at server side is clear how it is done (foto.jpg.quality=1.0, etc) but at client side (chrome browser)?

My target is to see the foto thumbs with better quality in chrome than default, since I have the power CPU computing and ressources without the necessity to make use of cache.

[Micke Pe]

Your assumptions are totally right :)

The quality setting tells the crawler what thumbnail it has to create. This thumb is shown in your browser but the viewable size ist adjusted by Inline CSS Statements. So you could have a 1000px thumb wich is shown in 100px space in the site (10% zoom/sketch).

Top control the CSS statements set the client.css.thumb.height also in your piccaport.properties .

Maybe it is now clearer why you should Set both options. Imagine a quality setting at 100px and a css setting at 1000px. This would be a large but very ugly thumbnail.

[Micke Pe]

One Thing I missed:

When I wrote about "quality" setting I meant the "thumbs.height" .
The image.quality is also important fir the compression like the "Save As" function in picture programms where you can choose how big the filesize should be (lesser size = lesser colours and lesser resoloution)