You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When it comes to image quality, i feel a difference between the full resolution image (display through seadragon viwer in deepzoom mode) and the rezised image.
Full resolution is net and clear, resized is a bit fuzzy (especialy when looked on ipad screen)
I checked the interpolation startup variable and having it set on bilinear by my provider improved the resized image quality.
But it seems like since a couple of days the quality deteriorated.
How can i test the startup variables to check if the interpolation is still on ?
The text was updated successfully, but these errors were encountered:
The interpolation startup variable cannot change during runtime, so you will always use bilinear interpolation.
When you say "resized", are you referring to the thumbnail image on the page you link to? It looks fine to me, but if this only occurs on iPads, perhaps it's due to the high resolution display? Your thumbnail is limited to 656px in height, which is not much. The iPad will do it's own resizing in this case. A way around this would be to use the HTML element with multiple image sizes proposed.
Hi !
I am running iiipsrv in version 1.1 to display images on a Versailles web site https://sculptures-jardins.chateauversailles.fr/notice/notice.php?id=575
When it comes to image quality, i feel a difference between the full resolution image (display through seadragon viwer in deepzoom mode) and the rezised image.
Full resolution is net and clear, resized is a bit fuzzy (especialy when looked on ipad screen)
I checked the interpolation startup variable and having it set on bilinear by my provider improved the resized image quality.
But it seems like since a couple of days the quality deteriorated.
How can i test the startup variables to check if the interpolation is still on ?
The text was updated successfully, but these errors were encountered: