- 715bb41 Port the more accurate (and slightly faster) floating point IDCT implementation from jpeg-8a and later. New research revealed that the SSE/SSE2 floating point IDCT implementation was actually more accurate than the jpeg-6b implementation, not less, which is why its mathematical results have always differed from those of the jpeg-6b implementation. This patch brings the accuracy of the C code in line with that of the SSE/SSE2 code. by DRC · 10 years ago
- a758460 Provide a more thorough description of the trade-offs between the various DCT/IDCT algorithms, based on new resarch by DRC · 10 years ago
- 8940e6c Provide a more thorough description of the trade-offs between the various DCT/IDCT algorithms, based on new resarch by DRC · 10 years ago
- 832b1fc Remove the sections about replacing libjpeg at run time and compile time. These were written before O/S distributions started shipping libjpeg-turbo, and they are either pedantic or no longer relevant. Also remove any text that assumes the use of our official project binaries. Notes specific to the official binaries have been moved into the project wiki. by DRC · 10 years ago
- 0f7ff71 Wordsmith the project description by DRC · 12 years ago
- 5039d73 Eliminated the awkward and confusing "TurboJPEG/OSS" designation, since there are no other active implementations of the TurboJPEG API anymore; don't refer to the libjpeg API library as "libjpeg-turbo" anymore, since that can be confusing; ARM v7s build instructions by DRC · 12 years ago
- dc4645d Since Windows doesn't use lazy loading, clarify that a Windows application that uses jpeg_mem_dest() or jpeg_mem_src() must use the DLL containing those functions at run time. Other wordsmithing by DRC · 12 years ago
- ab70623 Implement in-memory source/destination managers even when not emulating the libjpeg v8 API/ABI by DRC · 12 years ago
- b87136c Include justification for not supporting SmartScale, DCT scaling, and the libjpeg v9 ABI by DRC · 12 years ago
- eff4f95 Subtle point, but the libjpeg v7+ API is not backward incompatible. That is, programs that were built against jpeg-6b can still build against jpeg-7+ with no issues. It's only the ABI that is backward incompatible, so the primary justification for implementing the emulation feature was to provide run-time (ABI) compatibility. by DRC · 12 years ago
- 5815699 In all fairness, breaking backward ABI compatibility was necessary in jpeg-7 and jpeg-8 due to the fact that the caller allocates the struct. by DRC · 12 years ago
- dad4d2e by DRC · 12 years ago
- d5e964c Wordsmithing; Remove mention of TurboJPEG/IPP-- it is no longer a relevant comparison, since the version of IPP on which TurboJPEG/IPP was based is now quite old, and TurboJPEG/IPP is no longer distributed or supported by The VirtualGL Project; Include information about mathematical incompatibilities with jpeg-8 by DRC · 12 years ago
- 2870131 Spacing tweak by DRC · 12 years ago
- ac51438 Indicate our support for some of the jpeg-8d features, as well as arithmetic coding by DRC · 12 years ago
- 00b327b Wordsmithing and grammar by DRC · 13 years ago
- 11a122b Wordsmithing and grammar by DRC · 13 years ago
- 6916f87 Several clarifications regarding v7/v8 API/ABI support by DRC · 13 years ago
- bdbcd14 Several clarifications regarding v7/v8 API/ABI support by DRC · 13 years ago
- 33eca7e Document the new scaling factors by DRC · 13 years ago
- 2c62da3 Subtle point, but TurboJPEG is the API and TurboJPEG/OSS is the library implementing that API. by DRC · 13 years ago
- b76c840 Add program that demonstrates how to check for the existence of the colorspace extensions by DRC · 13 years ago
- 67ce3b2 Added new alpha channel colorspace constants/pixel formats, so applications can specify that they need the unused byte in a 4-component RGB output buffer set to 0xFF when decompressing. by DRC · 13 years ago
- 80803ae "which"="that" by DRC · 13 years ago
- 9c4590e by DRC · 13 years ago
- b5624ee Remove any references to the wxWindows Library License and VirtualGL copyrights by DRC · 13 years ago
- 65e0cd3 Update license text to reflect the newly-relicensed jchuff.c by DRC · 13 years ago
- 1f8b601 by DRC · 13 years ago
- 0d2d965 Wordsmithed the project description by DRC · 14 years ago
- ab4db65 Various documentation tweaks by DRC · 14 years ago
- f0a5ba7 "integer forward DCT", not "forward integer DCT" by DRC · 14 years ago
- 7c1df0a Performance pitfalls by DRC · 14 years ago
- e372004 Added configure options to disable arithmetic encoding/decoding by DRC · 14 years ago
- 646e5a8 RGBA=RGBX, etc. by DRC · 14 years ago
- 5559c90 Additional information/corrections involving libjpeg v7/v8b emulation by DRC · 14 years ago
- 77e3964 Document the libjpeg v7/v8 extensions by DRC · 14 years ago
- ae7fe0b Clarify licensing by DRC · 14 years ago
- ff95aa6 by DRC · 14 years ago
- 3dc1bc2 Create separate packages for Win64 binaries by DRC · 14 years ago
- 1e6b5b4 Clarify license description by DRC · 14 years ago
- 0248dd9 Clarify the DLL hell problem by DRC · 15 years ago
- 7e0b499 Install jpeg62.dll in SDK directory, not Windows system directory. Also, check whether SDK is already installed prior to re-installing by DRC · 15 years ago
- 0a1f68e Visual C++ libraries can't be made to work with MinGW because of the dependency on msvcr90.dll, so build a separate installer for MinGW libraries by DRC · 15 years ago
- 68fef83 Split build instructions into a new file and add SDK usage notes to README-turbo.txt by DRC · 15 years ago
- 4614871 Instructions for Tiger-compatible build on Leopard/Snow Leopard by DRC · 15 years ago
- 4d5fc18 Reflect the fact that CFLAGS=CXXFLAGS=-O3 by default by DRC · 15 years ago
- ce1546e License info + updated performance claims by DRC · 15 years ago
- bd17e2a Instructions for cross compiling MinGW libs on Cygwin by DRC · 15 years ago
- 101f09a Build instructions by DRC · 15 years ago