We're hosting multiple sites on our Squiz Matrix system and some of those sites have responsive designs. Part of our responsive implementation includes support for retina-friendly images; desktop users get the same images so to avoid much unnecessary overhead, a lower JPEG compression level (i.e. lower quality, smaller size) is used when generating image varieties (thumbnail, preview, hero image).
The problem with this approach is that compression level seems to be applied globally - any "non-responsive" site that also relies on triggers for generating image varieties inherits the "low" settings and results in visible pixelation/JPEG artifacts.
Is there a way to configure compression settings per trigger, or is there an altogether different approach to be taken?
Thanks, Nic. I wonder what work-around we'll end up with :\
I don't know what your workflow is like, but personally I manually add high-res varieties, and sometimes the low-res thumbnails because I am not satisfied with the compression.
I don't know what your workflow is like, but personally I manually add high-res varieties, and sometimes the low-res thumbnails because I am not satisfied with the compression.
Some EES users who end up uploading such images will not necessarily have the tools or... know-how? to manually create thumbnails ಠ_ಠ
Given the choice, I'd rather automate the process as much as possible than have artisan image compression :) I guess we could always pitch responsifying the legacy sites and use some batch compression in the meantime.