Developer forum

Hi Vincent,

I confirm the bug. I register it to fix asap: 82895

Sorry for inconvenience.

Best regards,
Vladimir

Thanks!

Hi Vincent,

The problem has been solved in Dynamicweb.Imaging 5.3.0
You can either update the Dynamicweb.Imaging package through nuget package manager or wait for the next 9.8 release which should contain Dynamicweb.Imaging 5.3.0

Best regards,
Morten

Hi Morten,

9.9 has been released, and we're running on it, but I still see quality being deteriorated.

http://companyfits.cloud.dynamicweb-cms.com/Files/Images/Naamloos-2.jpg

vs

http://companyfits.cloud.dynamicweb-cms.com/Admin/Public/GetImage.ashx?Width=1920&Height=845&Crop=5&BackgroundColor=&DoNotUpscale=True&FillCanvas=False&Image=/Files/Images/Naamloos-2.jpg&AlternativeImage=/Images/missing_image.jpg

Hi Ambert

The image is scaled and compressed. So it will look differently. The point is to make the image smaller so the site gets faster.

By default jpeg are compressed at 75% - by using &Compression=95 you can increase compression and make the image better quality.

You can also change to webp format and use &quality to control it:

The config below makes your image 11kb instead of the original 40kb - 75% smaller in size - and of course that will cause a bit of quality. But you can then increase &quality=85

http://companyfits.cloud.dynamicweb-cms.com/Admin/Public/GetImage.ashx?Width=1920&Height=845&BackgroundColor=&DoNotUpscale=True&FillCanvas=False&Image=/Files/Images/Naamloos-2.jpg&AlternativeImage=/Images/missing_image.jpg&format=webp&quality=65

If you need your images in the exact same quality, you should not resize and compress them.

Also you need to flush your image cache (I did that for you on the above solution). It is deep in the release notes :-):

"

• Change image resizing to use interpolation and antialias
  Settings
  Added interpolation to drawing of images and antialias for rendering to improve the resized result for scaling large images to relatively small versions. Remember to flush image cache after upgrade. Empty cache in Files/cache.net/images."

Hi Nicolai,

thanks for the reply, i didnt even know it was a configuration option ;-)

I saw the documentation page about the image handler, but thats only to test images (developer -> image Handler).

If this is the correct config: 

Then its already set at 90, i've changed this to 100 and cleared the images cache, but the result seems to remain the same. 

Our client is persistent on uploading images in the correct format, so how could we disable the compression?

Just do not use getimage at all - use the file path directly - requires a change in the template. Compression=100 is a bad option.

The setting you have found is not used by getimage, but by the filemanagers autoresize feature.

Getimage is documented here: https://doc.dynamicweb.com/documentation-9/platform/platform-tools/getimage-image-handler

Hi Nicolai,

wish I could find a reference to it somewhere on this portal.. ;-)

When checking the Rapido partial 'standardparagraphone, it doesnt use GetImage, but only GetFile. I looked a bit around and found the Components/General/Image.cshtml that the @Render outputs. Here the actual code for the image is being generated. In the code I see a 'settings.DisableImageEnine'.

Couldnt I just disable that just as easy, or will other things 'break'.
I actually only want to disable the compression options for the paragraphelements.
Or I should modify each 'paragraph' cshtml to generate the IMG tag manually instead of using @Render?