Closed swissspidy closed 7 months ago
Going with this for now:
I thought about that, but need to think more about how to not make that confusing.
I suppose we could start with a quality setting per format. Not sure if other stuff is even supported.
That would match existing behavior in core, where the default quality setting for jpeg and webp was different (82 vs 86)
I thought about that, but need to think more about how to not make that confusing.
Seems fair to me though maybe an advanced tab for this purpose of fine tuning might appeal cool
I suppose we could start with a quality setting per format. Not sure if other stuff is even supported.
I remember correctly WordPress doesn't support progressive jpeg (even if I think it's a shame https://www.smashingmagazine.com/2018/02/progressive-image-loading-user-perceived-performance/).
If you could make a table "format in" "format out" (select) and quality (range slider) would be more than excellent
enabled | extension (in) | desidered out | quality |
---|---|---|---|
X | jpeg/jpg | mozjpeg | -----*- 82% |
x | png | webp | -----*- 86% |
webp | |||
avif | ---*--- 50% |
(....)
I remember correctly WordPress doesn't support progressive jpeg
vips / mozjpeg does, so that's nice :)
If you could make a table "format in" "format out" (select) and quality (range slider) would be more than excellent
Yeah that's what I was getting at with the table in the issue the description, and it would definitely provide most flexibility, but also make things more complex. But as you say, maybe an advanced tab for this would be best.
Reopening for looking into advanced configuration
Maybe a dropdown per file type to have a mapping?
Preferred image format (used for things like poster images etc.):
Choose preferred behavior:
.jpeg
.jpeg
.png
.webp
.avif
.gif
.heic
Note: ffmpeg also has libwebp, but seems pointless as there is already wasm-vips. So maybe remove that again?
Note: both jsquash and wasm-vips use mozjpeg, so can remove the former
Note: vips also supports jpeg xl