Skip to content

Would you consider exposing intermediate decoding data? #232

@pbeart

Description

@pbeart

This is a fantastic library which I particularly appreciate for not taking a 'babying' approach to decoding: I am currently planning on writing a pinned version fork which exposes the decoder, extractor, binarizer etc modules, but I imagine there might be some value in having the metadata this return be exposed in this library? E.g. as well as returning raw data, the decoder could optionally return the pixel data found in the image, and potentially other information like the sequence of blocks found in the image.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions