Skip to content

Limits of bimg #160

@axyz

Description

@axyz

Currently skrop is strictly coupled with bimg for all the image processing.

While bimg provides a good coverage for the basic operations it is a very limited wrapper on top of all the vips capabilities.

Ideally would be nice to use vips bindings directly. Of course bimg comes out of the box with some nice abstractions and wrappers to overcame the nightmare of all the segmentation faults that we may have using the bindings directly.

One option may be to just copy the part of bimg that we need, or to fork it.

A concrete example of the limits is customizing the jpeg encoding settings.
we cannot pass down the no_subsample option, leading to very poor quality for compressions lower than 85, also we cannot use different quantization tables (mozjpeg one may lead to better quality), and some other advanced settings that could allow us to fine tune the quality and the size of the images

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions