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
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.
The text was updated successfully, but these errors were encountered:
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.The text was updated successfully, but these errors were encountered: