jpeg-users — Question about JPEG libraries (usage, compilation...)

Re: [Jpeg-users] Jpeg-ls

[Mathieu M. <mat...@gm...>]

I am not sure what you mean. But I simply reused the implementation from CharLS:

http://charls.codeplex.com/

On Sat, Mar 13, 2010 at 9:14 PM, John Hayward
<joh...@us...> wrote:
>
> Message body follows:
>
> Hi - I noticed that you had started jpeg-ls for linux.
> What is the status of that?
>
> johnh...
>
> --
> This message has been sent to you, a registered SourceForge.net user,
> by another site user, through the SourceForge.net site.  This message
> has been delivered to your SourceForge.net mail alias.  You may reply
> to this message using the "Reply" feature of your email client, or
> using the messaging facility of SourceForge.net at:
> https://sourceforge.net/sendmessage.php?touser=2604988
>
>



-- 
Mathieu

Re: [Jpeg-users] problem with pvrg-jpeg

[Mathieu M. <mat...@gm...>]

hi Kurt,

  WARNING: I am not advicing you to use pvrg-jpeg by any mean. You
should keep in mind that the lossless encoder of PVRG is sk*ew up (I
really mean it). The only reason why I worked on this package was to
be able to handle PVRG' compressed file. The only way I found out was
to decompress them with pvrg and then recompress them with
IJG+lossless patch. See GDCM (http://gdcm.sf.net) for the complete
solution.

  Anyway the command line you are looking for is:

$  convert test.pgm test.gray
$  pvrg-jpeg -iw 1024 -ih 64 test.gray -s out.jpg

Assuming that your test.pgm would start with something like:

P5
1024 64
255
...

I have not tested with RGB, but it should work. convert is from the
imagemagick package.

HTH

On Fri, Feb 19, 2010 at 11:52 AM, Kurt Horvath <ku...@ko...> wrote:
> Hallo!
>
> I want to use pvrg-jpeg on debian to compress lossless medical data but it
> seems I have got an input problem. My original source is .bmp (bitmap
> 8-bit). But I also did try to convert to pgm as mentioned in the manual
>
>
>
> I was thinking about following command:
>
>
>
>  pvrg-jpeg –iw 320 –ih 240 –hf 2 –k 21.pgm –s myfle1.llj
>
>
>
> can u give me a hint where my mistake is? (error is 2092: Invalid input
> detected)
>
>
>
> (P.S.: I really need lossless jpeg because I am doing compression of several
> standards)
>
>
>
> Regards,
>
>
>
> Kurt Horvath



-- 
Mathieu

[Jpeg-users] libjpeg7 is out

[Mathieu M. <mat...@gm...>]

FYI,

libjpeg7 is now part of debian

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535350

http://www.ijg.org/

-- 
Mathieu

Re: [Jpeg-users] gallery2 outstanding security bugs -- Abondoned by Berninger?

[Mathieu M. <mat...@gm...>]

'lo there.

On Fri, Dec 12, 2008 at 4:49 PM, Tom Lane <tg...@re...> wrote:
> Bob Friesenhahn <bfr...@si...> writes:
>> On Fri, 12 Dec 2008, Jon Ciesla wrote:
>>> CCing them.  libjpeg SourceForge team, what is the current status of
>>> libjpeg development?
>
>> [ There's nothing happening... ]
>
> [ digs in mail logs... ]  Not long ago I got some email from one
> mat...@gm... telling me somebody was trying to ramp
> up libjpeg development again.  I assumed this was referring to the
> sourceforge project, but now I realize it wasn't.  I didn't save
> the email, so all I've got left is the sender address scraped from
> logs ...

Devpt are happening here: http://jpeg.sf.net.
I created this sf.net project back then when looking for info on IJG +
lossless patch. I was afraid info would get lost so I simply gather
all JPEG implementation there (IJG 6b, lossless patch, JPEG-LS, jasper
...). I was only very recently pointed to libjpeg sf.net project
(which was created after mine).

There hasn't been much discussion on the jpeg ML:

http://lists.sourceforge.net/lists/listinfo/jpeg-users

I guess we all have different goals. My sole interest is to support
all kind of JPEG encoding as found in DICOM. My sole interest in
jpeg1x/ijg 6c is that AFAIK it is compatible with the previous
arithmetic encoder but is patent free. I tried working with the
debian-med people to prepare a libjpeg6c debian package ... maybe one
day.

I have even started supporting JPEG-LS within the IJG codec, but my
laptop was stolen around that time, and I never tried again. But it
would be nice if some guru out there had some time to spent on the
venerable IJG codec to support the different JPEG specifications :)

Thanks & Regards
-- 
Mathieu

Re: [Jpeg-users] libjpeg 6c ?

[Guido V. <gu...@jp...>]

paul van den berg wrote:
> 
> Could you summarize for this list what happened?

This is a long story.
The short story is that I'm now realizing the features in a movie
production environment, based on a Motion-JPEG codec.
It turns out that the SmartScale option is the key feature, that's
why the current working name is "SmartScale Motion Picture Codec".
It also turns out that for HD (High Definition) movie processing
it is not sufficient to implement the core functions in C code -
you need to optimize the functions on assembly code basis with
extended media instruction sets (MMX, SSE...) for realtime
application in high definition movie processing.
That's what I'm actually busy with, and that's why I can't tell
you the long story now...

> I would like to see an open future development of IJG-libjpeg.

An open development has not helped in the past - as said the IJG/
libjpeg development was basically an individual effort.
I'm actually quite confident that my current involvement in the
movie coding field will provide a well foundation for coming
further in the right direction.  It considerably extends the
practical experiences, and, hopefully, can generate some fund
for other work...

Regards
Guido

Re: [Jpeg-users] libjpeg 6c ?

[paul v. d. b. <pau...@gm...>]

On Wed, 03 Dec 2008 11:55:41 +0100
Guido Vollbeding <gu...@jp...> wrote:

> paul van den berg schrieb:
> > 
> > Can you give any information on your JPEG-Plus proposal?
> 
> I'm really puzzled now.
> Is this the same "paul van den berg" with whom I had a discussion about this
> subject in 2006 when this document was created?

Yes, I am still the same.

> Also, the "paul van den berg" back then provided a pdf conversion of this document.
> It is all available here:
> 
>   http://jpegclub.org/temp/
>   http://jpegclub.org/temp/ITU-T-JPEG-Plus-Proposal_R3.doc

I am glad that you make this resource available to this list. I privately 
knew that it existed but it is up to you to make it public. Even your own
site does not refer to this document.
_R3 is more recent than the link Mathieu gave.
A Google-search on 'jpeg-plus' also gives this link:
 www.itu.int/md/T05-SG16-060403-D-0287/en
but the document it refers to is not publicly available.
Could you summarize for this list what happened?

> > What group are you organizing?
> > Who is involved? Can we track its progress?

[...]

Thanks for sharing these insights.
I am sure that very substantial parts in IJG-libjpeg are not coded by
Tom Lane. (See your own contributions). 
I would like to see an open future development of IJG-libjpeg.

Regards, Paul

Re: [Jpeg-users] Fwd: 20 Years of JPEG Celebrated With Software Launch

[Guido V. <gu...@jp...>]

Yes, you must know that Thomas Richter is member of this corrupt ISO
committee.
He started to mislead the people and advertise their bogus results in
Usenet,
and for me this was one of the reasons to abandon the fruitless
discussions there.

The ITU people were kind enough to accept my proposal and looking for
cooperation, but there was no funding either, so it couldn't take off.

Regards
Guido

[Jpeg-users] Fwd: 20 Years of JPEG Celebrated With Software Launch

[mathieu <mat...@gm...>]

Just FYIing to myself...


---------- Forwarded message ----------
From: Guido Vollbeding <gu...@jp...>
Date: Jun 8 2006, 11:15 am
Subject: 20 Years of JPEG Celebrated With Software Launch
To: comp.compression


Thomas Richter wrote:

> That means, I still cannot use Q15 for proprietry products

You can use Q15 as part of that ITU Recommendation for any kind of
products
you want!  That is noted onhttp://ftp3.itu.ch/jpeg1x/.

> Though it would still not be JPEG, it's a different standard - to be
> precise an ITU-recommendation - based on JPEG resp. the identical
> ITU-recommendation. That doesn't mean much, of course, it's just a
> different number and a different organization.

It is the *real* JPEG organization, based on the *real* JPEG standard!
It is the *ISO* part of JPEG which went wrong and got corrupted and
created
a totally different animal "JPEG-2000" which has nothing to do with
the
original JPEG standard!
J2K is a totally different technique, they just were clever enough to
apply the name "JPEG" to it because JPEG was so successful.  They
could do
this because at that time (in the mid and late ninetees) the original
JPEG
inventors had largely left the JPEG committee to do other things, and
there
was a "vacuum" to fill.  So basically JPEG-2000 is a hoax.

> Beating JPEG is actually easy. The standard is a bit old, and an overall
> renovation would be suitable.

Wrong!  There were several attempts in the past to beat JPEG, and they
all
have failed, and they *must* fail, because none of the challengers
have
understood the basic JPEG (DCT) fundamentals.

> Back in the old days, a couple of
> compromises had to be made to make it suitable for the hardware back
> then. The question really is, why drilling up an old working horse that
> does the job fine by introducing marginal improvements that generate
> bitstreams that are not backwards-compatible if instead we can throw it
> away and start from scratch.

Thomas, sorry, but here you show your complete ignorance!
The opposite of what you say is true:  The original JPEG DCT approach
is
the *only* appropriate solution for image coding!  Of course you can't
recognize this because you have not understood or ignore the basic DCT
fundamentals.
You will never achieve any advance without basic understanding of DCT
fundamentals, and that's why all those attempts must fail.
And of course WE WILL be backwards-compatible:  our new decoders will
seamlessly read "old" JPEG files without any problem, the encoders can
optionally output old streams, or you can transcode between different
flavors.
Backwards-compatibility is exactly what YOU broke with your JPEG-2000
thing!

> I haven't compared the Q15 implementation with the QM implementation, so
> I cannot present numbers right now. Given that both are approximately
> comparable, the mentioned improvement isn't able to match with even
> existing standards today, as measurements on QM show. So the question
> really is, why do that? However, I'm with the ITU in the sense that I
> see no point in *not* defining a standard, so let's see how it goes.

Thomas, it is said in the message:  This is only the *first* phase
result,
and "Experts from SG 16 say to stay tuned for further developments."!

These "further developments" will be more important than that first
result!
You can find something about this in my contributed proposal, latest
Revision 3:

 http://jpegclub.org/temp/

  direct:http://jpegclub.org/temp/ITU-T-JPEG-Plus-Proposal_R3.doc

But of course if you read this, and if you would understand it, then
you
could not continue to propagate your misleading statements.
So better keep on ignoring it if you want to maintain your opinion.

> I also haven't compared with the new Microsoft code yet, I just don't
> have it.

I have it!
But I can't tell about the details here because I had to sign kind of
non-disclosure agreements.

> A new round of comparisons would really be suitable and I would
> be curious to see the results with Microsoft's code. One thing for sure,
> the 50% higher compression than JPEG as advertised by M$ is definitely
> marketing hype. I would belive it's better than JPEG-1 (no blocking),
> maybe it's better than JPEG2000, it would require testing to make
> statements. Statements like "They cannot!" *at this time* come
> definitely too early and are as much marketing hype as the hot air from
> Redmond.

JPEG-2000 is obsolete and will lose even more ground (if it ever had
any)
after this WM Photo attempt, because WMP is more related to
traditional
JPEG technology than JPEG-2000/Wavelets.
The developers of this WM Photo are, similar to JPEG-2000 proponents
and
other folks, not aware of the basic DCT properties for image coding.
Therefore they *cannot* beat our actual JPEG-Plus approach!
The original JPEG-1 was only an initial approach.  They found the
right
technique (DCT), rather by accident so to say, but they had no basic
understanding of DCT fundamentals, and thus couldn't exploit all of
its
potential.
That is exactly what we do now with our JPEG-Plus approach:
For the first time present an appropriate exploitation of basic DCT
properties and thus approach its full potential!
And I can assure you that our results are superior to anything what
you have seen so far.  As said:  Stay tuned...

Regards
Guido Vollbeding
Organizer Independent JPEG Group

Re: [Jpeg-users] libjpeg 6c ?

[Guido V. <gu...@jp...>]

paul van den berg schrieb:
> 
> Can you give any information on your JPEG-Plus proposal?

I'm really puzzled now.
Is this the same "paul van den berg" with whom I had a discussion about this
subject in 2006 when this document was created?
Also, the "paul van den berg" back then provided a pdf conversion of this document.
It is all available here:

  http://jpegclub.org/temp/
  http://jpegclub.org/temp/ITU-T-JPEG-Plus-Proposal_R3.doc

There have been more things happening in the meantime and other documents
being written (which are not publicly available) with more descriptions
and more discoveries described, but this one is still valid.

> What group are you organizing?
> Who is involved? Can we track its progress?

It is the entity which I took over from the previous IJG organizer Tom Lane.
The "group" was nothing more than a mailing list, and unfortunately it went
defunct some time back.  Then I tried to recover the list by taking it over
to my own site, but it turned out that the effort wasn't worth it because
there were no more substantial contributions.
And I think the group was not very helpful even before that happened - the
IJG libjpeg effort was basically the whole work of Tom Lane himself, and
now it is basically the whole work of myself.  There is no noticeable
support from anywhere, that's why Tom Lane couldn't continue the work.
I took it over because I made fundamental discoveries and contributions,
and nobody else was present to do that.
The missing support problem is still the same, but what can I do?
Either I do it, or nobody else will do it, and DCT-based JPEG, which is
the only proper base for image coding application, would die.

Yes, there are always many people demanding support, updates, and asking
questions, and I do my best to answer the questions and hint to solutions,
but there is no one who would provide any fund for doing this work.
There are many funds available, but, as said, they are actually all invested
in bogus developments.  This has to be understood.  And as long as this
situation continues, there can be no proper progress.

What I'm actually doing is to establish an enterprise for realizing the
discovered features in the movie coding domain!  There are much more
opportunities available in the movie coding.  The still image domain
is actually in complete darkness - all research, development, and
industry is corrupted in this area.
I have now found some kind of support for introducing the features for
movie coding applications, and if this goes well, I will also be able
to push the still image develeopment in the right direction.

Regards
Guido Vollbeding
Organizer Independent JPEG Group

Re: [Jpeg-users] libjpeg 6c ?

[Mathieu M. <mat...@gm...>]

On Wed, Dec 3, 2008 at 10:57 AM, paul van den berg
<pau...@gm...> wrote:
> On Wed, 03 Dec 2008 00:38:47 +0100
> Guido Vollbeding <gu...@jp...> wrote:
>
>> ...  This is one of the features possible with the
>> new direct DCT scaling functions as described on my site and in
>> my JPEG-Plus proposal ...
>
> Can you give any information on your JPEG-Plus proposal?
>

After a quick google search:

http://jpegclub.org/temp/ITU-T-JPEG-Plus-Proposal.doc

2cts
-- 
Mathieu

Re: [Jpeg-users] libjpeg 6c ?

[paul v. d. b. <pau...@gm...>]

On Wed, 03 Dec 2008 00:38:47 +0100
Guido Vollbeding <gu...@jp...> wrote:

> ...  This is one of the features possible with the
> new direct DCT scaling functions as described on my site and in
> my JPEG-Plus proposal ...

Can you give any information on your JPEG-Plus proposal?

> Regards
> Guido Vollbeding
> Organizer Independent JPEG Group

What group are you organizing? 
Who is involved? Can we track its progress?

Regards, Paul

Re: [Jpeg-users] libjpeg 6c ?

[Guido V. <gu...@jp...>]

Hi Mathieu

The most important aspect of that v7 update will be to introduce
new features in the core of the JPEG system, and that core is the
DCT!  This has to be understood first:  The primary aspect is to
utilize the fundamental DCT properties to a more appropriate
degree than has been done before in image coding in general,
and everything else is secondary!

You must understand that all established image compression research
and development is actually going in wrong directions, and the
reason for this situation is that the DCT and its fundamental
properties are not understood properly.  There is a common lack
of understanding the basic image coding principles - I have until
today not come across a single person who would understand the
essence of the DCT for image coding!  And I can tell you that I
have met and communicated with lots of so-called "experts" in this
field - including the original JPEG and MPEG authors!  And no one
of them has understood the DCT and its potential!  So that is the
primary and essential goal to achieve.
Without proper understanding and utilizing the DCT there can be
no real progress in image coding - all other attempts which we see
today are mistakes and will fail, due to misunderstanding of and
deviating from the true DCT.
JPEG as we know it today uses only a tiny subset of the full DCT
potential, and v7 starts to extend the features to a more
appropriate degree.  (It lays foundation for other important
features to come later...)

> By the way do you consider merging the lossless patch from Ken
> Murchison in v7 at all ?

You mean the lossless mode of the original JPEG spec?
There is a reason that it has not found noticeable application
in practice.  It is not seamlessly integrated with the usual
DCT processing mode.  With proper understanding of the DCT you
can provide a lossless mode which is seamlessly integrated with
the DCT mode.  This is one of the features possible with the
new direct DCT scaling functions as described on my site and in
my JPEG-Plus proposal, which is actually ignored at the official
committees because they are invested in bogus developments.

Regards
Guido Vollbeding
Organizer Independent JPEG Group

Re: [Jpeg-users] libjpeg 6c ?

[Mathieu M. <mat...@gm...>]

On Tue, Dec 2, 2008 at 11:41 PM, Guido Vollbeding <gu...@jp...> wrote:
> By the way, you may consider this one of the reasons why I
> will not provide any official v6 update anymore.
> The next release will be v7, because there are fundamental
> enhancements in this version.

ok.
By the way do you consider merging the lossless patch from Ken
Murchison in v7 at all ? I have tried, but I really lack an in depth
understanding of IJG (and jpeg spec) to be able to finish the work.

Thank you.
-- 
Mathieu

Re: [Jpeg-users] libjpeg 6c ?

[Guido V. <gu...@jp...>]

By the way, you may consider this one of the reasons why I
will not provide any official v6 update anymore.
The next release will be v7, because there are fundamental
enhancements in this version.

Regards
Guido Vollbeding
Organizer Independent JPEG Group

Re: [Jpeg-users] libjpeg 6c ?

[Mathieu M. <mat...@gm...>]

On Tue, Dec 2, 2008 at 10:20 PM, Guido Vollbeding <gu...@jp...> wrote:
> paul van den berg wrote:
>>
>> But if you run 'make -i test' on the 6c source with testimages
>> from ijg-source you get:
>
> But why would you run the test of 6c with testimages from 6b?
> One of the improvements of this 6c package is that it has got
> its own corrected testimages!  The testimages from 6b cannot
> work with 6c/7, because I have introduced a more correct method
> for the internal color subsampling processing.  The method used
> in 6b is inferior and has serious shortcomings.  6c/7 solves
> these problems by using the same new direct DCT scaling
> functions for the color subsampling as for the image rescaling.
> The compressed testimages had to be adapted (recreated with new
> method) for the new version.  There is nothing wrong with this,
> it's actually a feature, not a bug!

I updated the wiki. Thank you Guido.

http://apps.sourceforge.net/mediawiki/jpeg/index.php?title=Jpeg-6c&curid=9&diff=40&oldid=39&rcid=45


-- 
Mathieu

Re: [Jpeg-users] libjpeg 6c ?

[Guido V. <gu...@jp...>]

paul van den berg wrote:
> 
> But if you run 'make -i test' on the 6c source with testimages
> from ijg-source you get:

But why would you run the test of 6c with testimages from 6b?
One of the improvements of this 6c package is that it has got
its own corrected testimages!  The testimages from 6b cannot
work with 6c/7, because I have introduced a more correct method
for the internal color subsampling processing.  The method used
in 6b is inferior and has serious shortcomings.  6c/7 solves
these problems by using the same new direct DCT scaling
functions for the color subsampling as for the image rescaling.
The compressed testimages had to be adapted (recreated with new
method) for the new version.  There is nothing wrong with this,
it's actually a feature, not a bug!

Regards
Guido Vollbeding
Organizer Independent JPEG Group

Re: [Jpeg-users] libjpeg 6c ?

[Mathieu M. <mat...@gm...>]

On Tue, Dec 2, 2008 at 8:50 PM, paul van den berg <pau...@gm...> wrote:
> On Wed, 26 Nov 2008 21:05:33 +0100
> Bill Allombert <Bil...@ma...> wrote:
>
>> Is it an official libjpeg release ?
>> Should I upgrade the Debian package to it ?
>> What are the changes ?
>
> I have followed http://jpegclub.org/libjpeg-6c.tar.gz for some time.
> It is a moving target. I have at least 4 different versions, 2 from 2006
> and 2 from 2008.
>
> The most important changes from the original ijg-release are:
>
> cjpeg -h adds:
>  -scale M/N     Scale image by fraction M/N, eg, 1/2
>
> djpeg -h adds:
>  -scale M/N     Scale output image by fraction M/N, eg, 1/8
>
> jpegtran -h adds:
>  -crop WxH+X+Y  Crop to a rectangular subarea
> [ this is already included in debian, gentoo, suse ..? ]
>
> But if you run 'make -i test' on the 6c source with testimages
> from ijg-source you get:
>
> ./djpeg -dct int -ppm -outfile testout.ppm  ./testorig.jpg
> ./djpeg -dct int -bmp -colors 256 -outfile testout.bmp  ./testorig.jpg
> ./cjpeg -dct int -outfile testout.jpg  ./testimg.ppm
> ./djpeg -dct int -ppm -outfile testoutp.ppm ./testprog.jpg
> ./cjpeg -dct int -progressive -opt -outfile testoutp.jpg ./testimg.ppm
> ./jpegtran -outfile testoutt.jpg ./testprog.jpg
> cmp ./testimg.ppm testout.ppm
> ./testimg.ppm testout.ppm differ: byte 37, line 4
> make: [test] Error 1 (ignored)
> cmp ./testimg.bmp testout.bmp
> ./testimg.bmp testout.bmp differ: byte 59, line 1
> make: [test] Error 1 (ignored)
> cmp ./testimg.jpg testout.jpg
> ./testimg.jpg testout.jpg differ: byte 1395, line 7
> make: [test] Error 1 (ignored)
> cmp ./testimg.ppm testoutp.ppm
> ./testimg.ppm testoutp.ppm differ: byte 37, line 4
> make: [test] Error 1 (ignored)
> cmp ./testimgp.jpg testoutp.jpg
> ./testimgp.jpg testoutp.jpg differ: byte 1582, line 8
> make: [test] Error 1 (ignored)
> cmp ./testorig.jpg testoutt.jpg
>

That's pure gold ! :)

Thanks I added that info to jpeg's wiki:

http://apps.sourceforge.net/mediawiki/jpeg/index.php?title=Jpeg-6c

Thanks


-- 
Mathieu

Re: [Jpeg-users] libjpeg 6c ?

[paul v. d. b. <pau...@gm...>]

On Wed, 26 Nov 2008 21:05:33 +0100
Bill Allombert <Bil...@ma...> wrote:

> Is it an official libjpeg release ? 
> Should I upgrade the Debian package to it ?
> What are the changes ?
 
I have followed http://jpegclub.org/libjpeg-6c.tar.gz for some time.
It is a moving target. I have at least 4 different versions, 2 from 2006
and 2 from 2008. 

The most important changes from the original ijg-release are:

cjpeg -h adds:
  -scale M/N     Scale image by fraction M/N, eg, 1/2

djpeg -h adds:
  -scale M/N     Scale output image by fraction M/N, eg, 1/8

jpegtran -h adds:
  -crop WxH+X+Y  Crop to a rectangular subarea 
[ this is already included in debian, gentoo, suse ..? ]

But if you run 'make -i test' on the 6c source with testimages 
from ijg-source you get:

./djpeg -dct int -ppm -outfile testout.ppm  ./testorig.jpg
./djpeg -dct int -bmp -colors 256 -outfile testout.bmp  ./testorig.jpg
./cjpeg -dct int -outfile testout.jpg  ./testimg.ppm
./djpeg -dct int -ppm -outfile testoutp.ppm ./testprog.jpg
./cjpeg -dct int -progressive -opt -outfile testoutp.jpg ./testimg.ppm
./jpegtran -outfile testoutt.jpg ./testprog.jpg
cmp ./testimg.ppm testout.ppm
./testimg.ppm testout.ppm differ: byte 37, line 4
make: [test] Error 1 (ignored)
cmp ./testimg.bmp testout.bmp
./testimg.bmp testout.bmp differ: byte 59, line 1
make: [test] Error 1 (ignored)
cmp ./testimg.jpg testout.jpg
./testimg.jpg testout.jpg differ: byte 1395, line 7
make: [test] Error 1 (ignored)
cmp ./testimg.ppm testoutp.ppm
./testimg.ppm testoutp.ppm differ: byte 37, line 4
make: [test] Error 1 (ignored)
cmp ./testimgp.jpg testoutp.jpg
./testimgp.jpg testoutp.jpg differ: byte 1582, line 8
make: [test] Error 1 (ignored)
cmp ./testorig.jpg testoutt.jpg


Regards, Paul

Re: [Jpeg-users] Wiki activated

[Mathieu M. <mat...@gm...>]

Simply drop me an email (private email is fine) if you want write
access to the wiki. You are required to have a sf.net account (sorry).

Thanks !

On Tue, Dec 2, 2008 at 11:12 AM, Mathieu Malaterre
<mat...@gm...> wrote:
> I have activated the wiki for jpeg sf.net project:
>
> * http://apps.sourceforge.net/mediawiki/jpeg/index.php?title=Main_Page
>
> --
> Mathieu
>



-- 
Mathieu

[Jpeg-users] Wiki activated

[Mathieu M. <mat...@gm...>]

I have activated the wiki for jpeg sf.net project:

* http://apps.sourceforge.net/mediawiki/jpeg/index.php?title=Main_Page

-- 
Mathieu

[Jpeg-users] Fwd: libjpeg 6c ?

[Mathieu M. <mat...@gm...>]

Fwding as Guido is not member of jpeg-users


---------- Forwarded message ----------
From: Guido Vollbeding <gu...@jp...>
Date: Sun, Nov 30, 2008 at 10:04 PM
Subject: Re: [Jpeg-users] libjpeg 6c ?
To: Mathieu Malaterre <mat...@gm...>
Cc: Bill Allombert <Bil...@ma...>,
jpe...@li...


Hello all

Mathieu Malaterre wrote:
>
> Cool ! Thanks for the info.
> No roadmap, no timeline ?

I have a roadmap, but no timeline.

> Is libjpeg6c stable ?

It appears to be stable, as far as I can tell.
But I'm actually not in the condition to conduct the
necessary tests for all the platforms, and some minor things
are still missing (particularly updated documentation),
so that's why it is not a release, although the major
new features for the upcoming v7 update are already
contained in this package.

> Where does the development take place ?

The development is actually exclusively in my hands.

Best regards
Guido Vollbeding
Organizer Independent JPEG Group



-- 
Mathieu

Re: [Jpeg-users] setting up lossless jpeg

[Mathieu M. <mat...@gm...>]

Hi Jim,

On Mon, Dec 1, 2008 at 11:05 PM, Jim Moody
<bb...@us...> wrote:
> Hello, I have been using the IJG library for a few years,
> but now need lossless decompression for some DICOM data I
> received. I saw your comments on fixunix.com regarding JPEG
> Lossless decompression, and I'm a bit confused on what to
> download from source forge. The thread mentions that a
> "famous patch" is available from the sourceforge jpeg
> project site, but is it a separate item or is has it already
> been applied to some version (6c perhaps?)?  Can you point
> me to the specific package or packages I need to download in
> order to have a library that support lossless jpeg
> (de)compression?

In short:
You need the following patch: ljpeg-patch.v6b.tar.gz  (ftp.oceana.com
section in sf.net download). This file was downloaded from official
oceana ftp site at a time where it was still available.

OR you can download a prepatch version + cmake as:
ljpeg-62.1.0.tar.bz2   (section ljpeg in sf.net download).

libjpeg6c is a release prepared by Guido which has some upcoming
features, but does not include the lossless patch.

As a side note there are still a couple of place where the lossless
patch is not working, so I would suggest you have a look at what is
being done in GDCM or DCMTK. ref:

http://apps.sourceforge.net/mediawiki/gdcm/index.php?title=GDCM_Release_2.0

I need to merge local gdcm patch back into the jpeg sf.net release.


> Is there some document that explains the differences between
> the various packages you have here? (what is the difference
> between what oceana.com has and jpegclub, and ijg.org?)

Not that I know of.
IJG: official 6b version (lossy only)
jpegclub: 6c version from guido (lossy only)
oceana: 6b + lossless patch (lossy+lossless).

If you are to process lossless jpeg, do not forget to compile the
12bits/16bits version of IJG. See what is being done in the cmake
version to avoid duplicating source code.

2cts
-- 
Mathieu

Re: [Jpeg-users] libjpeg 6c ?

[Mathieu M. <mat...@gm...>]

On Sun, Nov 30, 2008 at 7:50 PM, Bill Allombert
<Bil...@ma...> wrote:
> On Wed, Nov 26, 2008 at 09:05:33PM +0100, Bill Allombert wrote:
>> Hello Guido,
>>
>> It has been brought to my attention: your post from 2006
>> http://groups.google.com/group/comp.compression/msg/77d99c47ec1736da?hl=en&
>> and the file http://jpegclub.org/libjpeg-6c.tar.gz
>>
>> Is it an official libjpeg release ?
>
> Guido answered that this is not an official release, and that I should
> wait for v7.

Cool ! Thanks for the info.
No roadmap, no timeline ? Is libjpeg6c stable ?
Where does the development take place ?

Thanks,
-- 
Mathieu

Re: [Jpeg-users] libjpeg 6c ?

[Bill A. <Bil...@ma...>]

On Wed, Nov 26, 2008 at 09:05:33PM +0100, Bill Allombert wrote:
> Hello Guido,
> 
> It has been brought to my attention: your post from 2006
> http://groups.google.com/group/comp.compression/msg/77d99c47ec1736da?hl=en&
> and the file http://jpegclub.org/libjpeg-6c.tar.gz
> 
> Is it an official libjpeg release ? 

Guido answered that this is not an official release, and that I should
wait for v7.

Cheers,
Bill.

[Jpeg-users] libjpeg 6c ?

[Bill A. <Bil...@ma...>]

Hello Guido,

It has been brought to my attention: your post from 2006
http://groups.google.com/group/comp.compression/msg/77d99c47ec1736da?hl=en&
and the file http://jpegclub.org/libjpeg-6c.tar.gz

Is it an official libjpeg release ? 
Should I upgrade the Debian package to it ?
What are the changes ?

Cheers,
Bill.