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
I noticed that the JPEG downsampling option is currently set to Downsample::BothDirections => SkJpegEncoder_Downsample::k420 by default, as shown here.
In certain use cases, this default setting can cause exported JPEG images to appear "blurry." For high-quality exports, I currently work around this by exporting images as PNG first, then converting them to JPEG with 4:4:4 subsampling using a separate library. However, this is a multi-step process that adds complexity and extra resource usage.
Feature Proposal:
It would be highly beneficial to allow custom downsampling settings directly within the toBuffer function. This enhancement would provide users with more control over the output quality, enabling the selection of different subsampling options (such as 4:4:4) to avoid potential quality loss.
Thank you for considering this feature!
The text was updated successfully, but these errors were encountered:
antoox-yk
changed the title
jpeg rendering quality
[Feature Request] Jpeg DownSample options
Nov 6, 2024
Hi team,
I noticed that the JPEG downsampling option is currently set to
Downsample::BothDirections => SkJpegEncoder_Downsample::k420
by default, as shown here.In certain use cases, this default setting can cause exported JPEG images to appear "blurry." For high-quality exports, I currently work around this by exporting images as PNG first, then converting them to JPEG with 4:4:4 subsampling using a separate library. However, this is a multi-step process that adds complexity and extra resource usage.
Feature Proposal:
It would be highly beneficial to allow custom downsampling settings directly within the
toBuffer
function. This enhancement would provide users with more control over the output quality, enabling the selection of different subsampling options (such as 4:4:4) to avoid potential quality loss.Thank you for considering this feature!
The text was updated successfully, but these errors were encountered: