kc3-lang/libjpeg-turbo/doc
Branch :
Log
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
 |
6d9f1f81 | 2024-09-01 14:04:20 | Merge branch 'main' into dev | |
|
797c6ccd | 2024-09-01 11:23:31 | Doc: Further clarify MCU definition | |
|
64567381 | 2024-08-31 17:31:02 | Merge branch 'main' into dev | |
|
8d76e4e5 | 2024-08-31 15:33:55 | Doc: "EXIF" = "Exif" | |
|
9983840e | 2024-08-31 12:41:13 | TJ/xform: Check crop region against dest. image Lossless cropping is performed after other lossless transform operations, so the cropping region must be specified relative to the destination image dimensions and level of chrominance subsampling, not the source image dimensions and level of chrominance subsampling. More specifically, if the lossless transform operation swaps the X and Y axes, or if the image is converted to grayscale, then that changes the cropping region requirements. | |
|
8456d2b9 | 2024-08-30 10:50:13 | Doc: "MCU block" = "iMCU" or "MCU" The JPEG-1 spec never uses the term "MCU block". That term is rarely used in other literature to describe the equivalent of an MCU in an interleaved JPEG image, but the libjpeg documentation uses "iMCU" to describe the same thing. "iMCU" is a better term, since the equivalent of an interleaved MCU can contain multiple DCT blocks (or samples in lossless mode) that are only grouped together if the image is interleaved. In the case of restart markers, "MCU block" was used in the libjpeg documentation instead of "MCU", but "MCU" is more accurate and less confusing. (The restart interval is literally in MCUs, where one MCU is one data unit in a non-interleaved JPEG image and multiple data units in a multi-component interleaved JPEG image.) In the case of 9b704f96b2dccc54363ad7a2fe8e378fc1a2893b, the issue was actually with progressive JPEG images exactly two DCT blocks wide, not two MCU blocks wide. This commit also defines "MCU" and "MCU row" in the description of the various restart marker options/parameters. Although an MCU row is technically always a row of samples in lossless mode, "sample row" was confusing, since it is used in other places to describe a row of samples for a single component (whereas an MCU row in a typical lossless JPEG image consists of a row of interleaved samples for all components.) | |
|
fd9b21b6 | 2024-08-28 18:58:21 | Merge branch 'main' into dev | |
|
5cf79606 | 2024-08-28 18:36:37 | Undocument TJ*PARAM_RESTARTBLOCKS for lossless TJ*PARAM_RESTARTBLOCKS technically works with lossless compression, but it is not useful, since the value must be equal to the number of samples in a row. (In other words, it is no different than TJ*PARAM_RESTARTINROWS, except that it requires the user to do more math.) | |
|
6a9565ce | 2024-08-26 16:45:41 | Merge branch 'main' into dev | |
|
35199878 | 2024-08-26 16:35:30 | TurboJPEG doc: Fix incorrect/confusing parentheses |