libjpeg-turbo-users Mailing List for libjpeg-turbo (Page 19)
SIMD-accelerated libjpeg-compatible JPEG codec library
Brought to you by:
dcommander
You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
(1) |
Apr
(3) |
May
(1) |
Jun
(4) |
Jul
(2) |
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
(21) |
Jun
(8) |
Jul
(20) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
(4) |
2012 |
Jan
(3) |
Feb
(6) |
Mar
|
Apr
|
May
|
Jun
(12) |
Jul
(1) |
Aug
(8) |
Sep
(4) |
Oct
(9) |
Nov
(2) |
Dec
|
2013 |
Jan
(28) |
Feb
(24) |
Mar
(10) |
Apr
(10) |
May
(2) |
Jun
|
Jul
|
Aug
(12) |
Sep
(14) |
Oct
(15) |
Nov
(5) |
Dec
(2) |
2014 |
Jan
(21) |
Feb
(12) |
Mar
(13) |
Apr
(39) |
May
(3) |
Jun
|
Jul
|
Aug
(8) |
Sep
(5) |
Oct
|
Nov
(5) |
Dec
(8) |
2015 |
Jan
(10) |
Feb
(10) |
Mar
|
Apr
(5) |
May
(8) |
Jun
(23) |
Jul
(1) |
Aug
(8) |
Sep
(1) |
Oct
(1) |
Nov
(4) |
Dec
(4) |
2016 |
Jan
|
Feb
(2) |
Mar
(17) |
Apr
|
May
(1) |
Jun
(1) |
Jul
|
Aug
|
Sep
(1) |
Oct
(1) |
Nov
(2) |
Dec
(1) |
2017 |
Jan
(4) |
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(1) |
Aug
(2) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
From: DRC <dco...@us...> - 2010-09-10 00:56:34
|
https://sourceforge.net/projects/libjpeg-turbo/files/1.0.1/ Significant changes since 1.0.0 =============================== [1] The Huffman decoder will now handle erroneous Huffman codes (for instance, from a corrupt JPEG image.) Previously, these would cause libjpeg-turbo to crash under certain circumstances. [2] Fixed typo in SIMD dispatch routines which was causing 4:2:2 upsampling to be used instead of 4:2:0 when decompressing JPEG images using SSE2 code. [3] configure script will now automatically determine whether the INCOMPLETE_TYPES_BROKEN macro should be defined. |
From: Claus S. <csc...@gm...> - 2010-08-02 19:20:59
|
Thank you! It successfully installed after deleting the file. On Mon, Aug 2, 2010 at 20:21, DRC <dco...@us...> wrote: > It just checks for the existence of c:\windows\system32\turbojpeg.dll > (or c:\windows\syswow64\turbojpeg.dll, if you're installing the 32-bit > SDK on a 64-bit system.) It should install after you delete this file. > > NOTE: turbojpeg.dll is the compatibility wrapper to allow programs that > were built to use TurboJPEG/IPP to use libjpeg-turbo instead. It > installs in the Windows system directory to maintain backward > compatibility with the TurboJPEG/IPP SDK. > > On 8/2/10 8:23 AM, Claus Scheiblauer wrote: > > Hi! > > > > I have a question about the installer for Visual C++. > > > > Once I installed libjpeg-turbo 0.0.93 and deleted it later (I forgot how > > I deleted it...). > > > > Today I downloaded "libjpeg-turbo-1.0.0-vc.exe" and tried to install it, > > but I get an error message saying: "An existing version of the > > libjpeg-turbo SDK for Visual C++ or the TurboJPEG SDK is already > > installed. Please uninstall it first." > > > > I cannot find an entry in the Windows programs data base, so I cannot > > uninstall the previous version of the SDK. > > > > So my question is, which Windows Registry entries the setup program > > checks, that make it think that an older version of the SDK is already > > installed? I could then simply delete these entries. I searched the > > Registry for entries of "libjpeg", but there are none. > > > > I would prefer to install the SDK instead of building it from the > > sources, I like the easy way :) > > > > > > Thank you very much! > > > > C. > > > > -- > > Claus Scheiblauer, mailto:sch...@cg... > > <mailto:sch...@cg...> > > Vienna University of Technology, http://www.cg.tuwien.ac.at/ > > DVR: 0005886 > > > > > > > > > ------------------------------------------------------------------------------ > > The Palm PDK Hot Apps Program offers developers who use the > > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > > of $1 Million in cash or HP Products. Visit us here for more details: > > http://p.sf.net/sfu/dev2dev-palm > > > > > > > > _______________________________________________ > > Libjpeg-turbo-users mailing list > > Lib...@li... > > https://lists.sourceforge.net/lists/listinfo/libjpeg-turbo-users > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > Libjpeg-turbo-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libjpeg-turbo-users > -- Claus Scheiblauer, mailto:sch...@cg... Vienna University of Technology, http://www.cg.tuwien.ac.at/ DVR: 0005886 |
From: DRC <dco...@us...> - 2010-08-02 18:44:55
|
It just checks for the existence of c:\windows\system32\turbojpeg.dll (or c:\windows\syswow64\turbojpeg.dll, if you're installing the 32-bit SDK on a 64-bit system.) It should install after you delete this file. NOTE: turbojpeg.dll is the compatibility wrapper to allow programs that were built to use TurboJPEG/IPP to use libjpeg-turbo instead. It installs in the Windows system directory to maintain backward compatibility with the TurboJPEG/IPP SDK. On 8/2/10 8:23 AM, Claus Scheiblauer wrote: > Hi! > > I have a question about the installer for Visual C++. > > Once I installed libjpeg-turbo 0.0.93 and deleted it later (I forgot how > I deleted it...). > > Today I downloaded "libjpeg-turbo-1.0.0-vc.exe" and tried to install it, > but I get an error message saying: "An existing version of the > libjpeg-turbo SDK for Visual C++ or the TurboJPEG SDK is already > installed. Please uninstall it first." > > I cannot find an entry in the Windows programs data base, so I cannot > uninstall the previous version of the SDK. > > So my question is, which Windows Registry entries the setup program > checks, that make it think that an older version of the SDK is already > installed? I could then simply delete these entries. I searched the > Registry for entries of "libjpeg", but there are none. > > I would prefer to install the SDK instead of building it from the > sources, I like the easy way :) > > > Thank you very much! > > C. > > -- > Claus Scheiblauer, mailto:sch...@cg... > <mailto:sch...@cg...> > Vienna University of Technology, http://www.cg.tuwien.ac.at/ > DVR: 0005886 > > > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > > > > _______________________________________________ > Libjpeg-turbo-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libjpeg-turbo-users |
From: Claus S. <csc...@gm...> - 2010-08-02 13:23:43
|
Hi! I have a question about the installer for Visual C++. Once I installed libjpeg-turbo 0.0.93 and deleted it later (I forgot how I deleted it...). Today I downloaded "libjpeg-turbo-1.0.0-vc.exe" and tried to install it, but I get an error message saying: "An existing version of the libjpeg-turbo SDK for Visual C++ or the TurboJPEG SDK is already installed. Please uninstall it first." I cannot find an entry in the Windows programs data base, so I cannot uninstall the previous version of the SDK. So my question is, which Windows Registry entries the setup program checks, that make it think that an older version of the SDK is already installed? I could then simply delete these entries. I searched the Registry for entries of "libjpeg", but there are none. I would prefer to install the SDK instead of building it from the sources, I like the easy way :) Thank you very much! C. -- Claus Scheiblauer, mailto:sch...@cg... Vienna University of Technology, http://www.cg.tuwien.ac.at/ DVR: 0005886 |
From: DRC <dco...@us...> - 2010-07-08 05:50:16
|
(actually last Friday, but I forgot to send out an e-mail until now.) Source changes since 0.0.93 =========================== [1] 2983700: Further FreeBSD build tweaks (no longer necessary to specify --host when configuring on a 64-bit system) [2] Created sym. links in the Unix/Linux packages so that the TurboJPEG include file can always be found in /opt/libjpeg-turbo/include, the 32-bit static libraries can always be found in /opt/libjpeg-turbo/lib32, and the 64-bit static libraries can always be found in /opt/libjpeg-turbo/lib64. [3] The Unix/Linux distribution packages now include the libjpeg run-time programs (cjpeg, etc.) and man pages. [4] Created a 32-bit supplementary package for amd64 Debian systems which contains just the 32-bit libjpeg-turbo libraries. [5] Moved the libraries from */lib32 to */lib in the i386 Debian package. [6] Include distribution package for Cygwin [7] No longer necessary to specify --without-simd on non-x86 architectures, and unit tests now work on those architectures. Packaging changes since 0.0.93 ============================== [1] The static libraries in the Debian distribution packages are now built with PIC code so that they can be used to build shared libraries. [2] The 64-bit libraries in the Mac package are now backward compatible with OS X 10.4 and 10.5. |
From: DRC <dco...@us...> - 2010-07-02 11:19:11
|
Source changes since 0.0.93 =========================== [1] 2983700: Further FreeBSD build tweaks (no longer necessary to specify --host when configuring on a 64-bit system) [2] Created sym. links in the Unix/Linux packages so that the TurboJPEG include file can always be found in /opt/libjpeg-turbo/include, the 32-bit static libraries can always be found in /opt/libjpeg-turbo/lib32, and the 64-bit static libraries can always be found in /opt/libjpeg-turbo/lib64. [3] The Unix/Linux distribution packages now include the libjpeg run-time programs (cjpeg, etc.) and man pages. [4] Created a 32-bit supplementary package for amd64 Debian systems which contains just the 32-bit libjpeg-turbo libraries. [5] Moved the libraries from */lib32 to */lib in the i386 Debian package. [6] Include distribution package for Cygwin [7] No longer necessary to specify --without-simd on non-x86 architectures, and unit tests now work on those architectures. Build changes since 0.0.93 ========================== [1] Static libraries in the DEB packages are now built with PIC code, so they can be used to build shared libraries. [2] The 64-bit fork of the dynamic libraries and executables in the Mac package will now work on OS X 10.4 and 10.5. |
From: DRC <dr...@vi...> - 2010-06-11 17:21:13
|
Do you have a timeframe for when you think it will be integrated into Fedora? If it's, say, more than a month out, then I probably will want to put out a 0.0.94 release. On 6/11/10 5:25 AM, Adam Tkac wrote: > On Thu, Jun 10, 2010 at 05:15:25PM -0500, DRC wrote: >> Checked in the patch and also fixed the unit tests so that they work on >> non-x86 architectures (as a sanity check, the test files for the >> non-SIMD tests were generated with an unmodified version of jpeg-6b.) >> >> New release candidate tarball is here: >> http://www.virtualgl.org/libjpeg-turbo-1.0.0.tar.gz >> >> I'm in no particular hurry to get 1.0.0 out the door, so please take the >> time to do whatever testing you feel is necessary. I think it would be >> a good idea to wait until it is fully integrated into the Fedora build >> before releasing 1.0.0. > > I think wait till it gets integrated into the Fedora is a good idea, > it will help us to catch major issues. For now we can stuck in RC > stage and release 0.0.9X versions (or release nothing :) ). I will > inform you about any issues. > > Regards, Adam > |
From: Adam T. <at...@re...> - 2010-06-11 10:25:47
|
On Thu, Jun 10, 2010 at 05:15:25PM -0500, DRC wrote: > Checked in the patch and also fixed the unit tests so that they work on > non-x86 architectures (as a sanity check, the test files for the > non-SIMD tests were generated with an unmodified version of jpeg-6b.) > > New release candidate tarball is here: > http://www.virtualgl.org/libjpeg-turbo-1.0.0.tar.gz > > I'm in no particular hurry to get 1.0.0 out the door, so please take the > time to do whatever testing you feel is necessary. I think it would be > a good idea to wait until it is fully integrated into the Fedora build > before releasing 1.0.0. I think wait till it gets integrated into the Fedora is a good idea, it will help us to catch major issues. For now we can stuck in RC stage and release 0.0.9X versions (or release nothing :) ). I will inform you about any issues. Regards, Adam -- Adam Tkac, Red Hat, Inc. |
From: DRC <dr...@vi...> - 2010-06-10 22:15:45
|
Checked in the patch and also fixed the unit tests so that they work on non-x86 architectures (as a sanity check, the test files for the non-SIMD tests were generated with an unmodified version of jpeg-6b.) New release candidate tarball is here: http://www.virtualgl.org/libjpeg-turbo-1.0.0.tar.gz I'm in no particular hurry to get 1.0.0 out the door, so please take the time to do whatever testing you feel is necessary. I think it would be a good idea to wait until it is fully integrated into the Fedora build before releasing 1.0.0. On 6/10/10 5:38 AM, Adam Tkac wrote: > Hello, > > current compilation on non-SIMD architectures (like IBM PowerPC) > requires --without-simd configure parameter. I think we can > automatically fallback to non-SIMD with warning instead of abort > configure process. Proposed patch is attached, what do you think about > it? Is it still enough time to get it into 1.0.0? > > Regards, Adam > > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > > > > _______________________________________________ > Libjpeg-turbo-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libjpeg-turbo-users |
From: Adam T. <at...@re...> - 2010-06-10 10:38:55
|
Hello, current compilation on non-SIMD architectures (like IBM PowerPC) requires --without-simd configure parameter. I think we can automatically fallback to non-SIMD with warning instead of abort configure process. Proposed patch is attached, what do you think about it? Is it still enough time to get it into 1.0.0? Regards, Adam -- Adam Tkac, Red Hat, Inc. |
From: DRC <dco...@us...> - 2010-05-12 06:32:40
|
https://sourceforge.net/projects/libjpeg-turbo/files/0.0.93 Significant changes since 0.0.91 ================================ [1] Fixed x86-64 build on FreeBSD systems [2] Added support for Windows 64-bit systems |
From: Conrad P. <co...@me...> - 2010-04-23 07:11:33
|
On 18 April 2010 02:36, DRC <dco...@us...> wrote: > You may not get the full benefit, but you should still get some benefit. > Every aspect of the baseline JPEG pipeline, including Huffman coding, > has been accelerated in libjpeg-turbo. > > The best thing I can suggest is to try it and see. Hi Darrell, thanks, I'll do some measurements and report back here eventually :) Conrad. > > DRC > > On 4/16/10 9:28 PM, Conrad Parker wrote: >> Hi, >> >> I'm working on a JPEG rescaling tool which can be used as a thumbnailer CGI: >> >> http://www.kfish.org/software/fastphoto/ >> >> it uses libepeg, a wrapper for libjpeg set up to only decode the DCT >> coefficients needed to reconstruct at the required size, and to avoid >> colorspace conversions where possible. I'm wondering if libjpeg-turbo >> would provide a performance improvement in this use-case? >> >> Conrad. >> >> ------------------------------------------------------------------------------ >> Download Intel® Parallel Studio Eval >> Try the new software tools for yourself. Speed compiling, find bugs >> proactively, and fine-tune applications for parallel performance. >> See why Intel Parallel Studio got high marks during beta. >> http://p.sf.net/sfu/intel-sw-dev >> _______________________________________________ >> Libjpeg-turbo-users mailing list >> Lib...@li... >> https://lists.sourceforge.net/lists/listinfo/libjpeg-turbo-users > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Libjpeg-turbo-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libjpeg-turbo-users > > |
From: DRC <dco...@us...> - 2010-04-17 17:36:10
|
You may not get the full benefit, but you should still get some benefit. Every aspect of the baseline JPEG pipeline, including Huffman coding, has been accelerated in libjpeg-turbo. The best thing I can suggest is to try it and see. DRC On 4/16/10 9:28 PM, Conrad Parker wrote: > Hi, > > I'm working on a JPEG rescaling tool which can be used as a thumbnailer CGI: > > http://www.kfish.org/software/fastphoto/ > > it uses libepeg, a wrapper for libjpeg set up to only decode the DCT > coefficients needed to reconstruct at the required size, and to avoid > colorspace conversions where possible. I'm wondering if libjpeg-turbo > would provide a performance improvement in this use-case? > > Conrad. > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Libjpeg-turbo-users mailing list > Lib...@li... > https://lists.sourceforge.net/lists/listinfo/libjpeg-turbo-users |
From: Conrad P. <co...@me...> - 2010-04-17 02:28:26
|
Hi, I'm working on a JPEG rescaling tool which can be used as a thumbnailer CGI: http://www.kfish.org/software/fastphoto/ it uses libepeg, a wrapper for libjpeg set up to only decode the DCT coefficients needed to reconstruct at the required size, and to avoid colorspace conversions where possible. I'm wondering if libjpeg-turbo would provide a performance improvement in this use-case? Conrad. |
From: DRC <dco...@us...> - 2010-03-21 00:43:07
|
Pre-built SDK packages are available for Linux (64-bit and 32-bit RPMs & DEBs and source RPM), Mac OS X (universal Tiger 32-bit and Snow Leopard 64-bit), Windows (32-bit, both Visual C++ and GCC flavors), and Solaris/x86 (32/64-bit Solaris 10 package built with Sun Studio 12.) https://sourceforge.net/projects/libjpeg-turbo/files/0.0.91 Significant changes since 0.0.90 ================================ [1] Added documentation to .deb packages [2] 2968313: Fixed data corruption issues when decompressing large JPEG images and/or using buffered I/O with the libjpeg-turbo decompressor |