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
Platform(s) (compiler version, operating system version, CPU) on which the bug was observed:
Linux Ubuntu
libjpeg-turbo release(s), commit(s), or branch(es) in which the bug was observed (always test the tip of the main branch or the latest stable pre-release to verify that the bug hasn't already been fixed):
Duplicate of #402. Not a bug. This is simply that, historically, libjpeg and its derivatives never supported lossless JPEG. I am in the process of implementing that support under contract.
8-bit, 12-bit, and 16-bit lossless JPEG is fully implemented in both the libjpeg and TurboJPEG APIs in the dev branch, and the beta release containing the feature will land early next week.
Have you searched the existing issues (both open and closed) in the libjpeg-turbo issue tracker to ensure that this bug report is not a duplicate?
Yes
Does this bug report describe one of the two known and unsolvable issues with the JPEG format?
No
Clear and concise description of the bug:
Getting error when decoding dicom jpg with transfer syntax 1.2.840.10008.1.2.4.70
Unsupported JPEG process: SOF type 0xc3
Steps to reproduce the bug (using only libjpeg-turbo):
This works:
This does not:
OSError: Unsupported JPEG process: SOF type 0xc3
Image(s) needed in order to reproduce the bug (if applicable):
https://github.com/blazespinnaker/klibs/blob/main/1_2_840_10008_1_2_4_70.jpg
Expected behavior:
Expected turbojpeg to decode the file
Observed behavior:
Error
Platform(s) (compiler version, operating system version, CPU) on which the bug was observed:
Linux Ubuntu
libjpeg-turbo release(s), commit(s), or branch(es) in which the bug was observed (always test the tip of the main branch or the latest stable pre-release to verify that the bug hasn't already been fixed):
Using this library https://github.com/lilohuang/PyTurboJPEG
If the bug is a regression, the specific commit that introduced the regression (use
git bisect
to determine this):I don't think it's a regresssion
Additional information:
The text was updated successfully, but these errors were encountered: