|This article is of interest to the following WikiProjects:|
- 1 Comparison to JPEG-LS
- 2 Availability
- 3 Edit
- 4 Disadvantages?
- 5 Test-Image
- 6 JPEG/JPEG 2000 comparision with JPEG images?
- 7 Section on Techical Discussion
- 8 Free software
- 9 Legal Issues
- 10 "JPEG 2000 is included in most Linux distributions."
- 11 machine judgment of quality
- 12 Article cleanup
- 13 What is the perf difference?
- 14 Thumbnails?
- 15 Comparison w/ Mr. Sid?
- 16 Basic (Part1) and Advanced (Part2)
- 17 Acrobat support
- 18 Illegal abbreviations
- 19 Colour Transforms
- 20 Tiling
- 21 Sample image?
- 22 best of jpeg for photo graph
- 23 Jargon
Comparison to JPEG-LS
Seems like there should be a section on this (not just split between Advantages and Disadvantage. It is part of the historical development of JPEG of which J2K is a later format. It should talk about WHY it was proposed after it had developed JPEG-LS, in other words the comparison to original JPEG is somewhat false. Maybe the article also needs a history section (although maybe this should be first added in the article on the Joint Photographic Experts Group). —Preceding unsigned comment added by 126.96.36.199 (talk) 16:30, 10 January 2010 (UTC)
The article states in the references that the final standard is not available freely. I think this might be wrong. As the JPEG consortium is a group of ISO and ITU-T all standards get published on the ITU-T pages as "Technical Recommendations". See T.800 to T.812 for the JPEG 2000 standards. —Preceding unsigned comment added by 188.8.131.52 (talk) 13:39, 20 July 2008 (UTC)
The article mentions that 'editability' is a feature of JPEG 2000, but does not explain. If I knew anything about this, I'd fix it.
Right now the article looks like it was written by some JPEG 2000 promotion group, with the first section being "Superiority of JPEG2000". I chuckled when I saw that. I think this should be renamed "Advantages" and another section with "Disadvantages" created right below. Disadvantages possibly being slower compression/decompression (not so good for digital cameras with limited processing power), patent issus (mentioned at the end of the article), lack of support and very slow adaptation, and that images that are "good enough quality" with no visible artifacts are pretty much same size with JPEG and JPEG2000. At least in my tests JPEG2000 seems to win only with quality that clearly shows some noticeable artifacts; It's just that JPEG then shows more. So it's questionable if the format is all that useful, as images with no visual artifacts are usually desirable (and not that big either). Magnus below at Test-Image-section also said something that confirms my observations: "But I think that JPEG2000 isn't better than JPEG at higger queality, it smooths more de image and deletes some detail that JPEG show it." At some compression ratio for some images, JPEG2000 may indeed look worse for the same file size. Negleting to mention this in the article is just hiding the facts. Also in my experience, lossless JPEG2000 is worse than PNG (compressed with pngcrush) even for photos, not just diagrams as the article suggests.
But I didn't edit the article because my info may be wrong or old. Someone better informed should do it if she seems it as appropriate.
There sure should be a section on disadvantages. I tried out JPEG 2000 a bit. And well, the disadvantages outweigh the advantages. First of all, although it eliminates the "jpeg artifacts", it smooths the image too much. A #8 compression on jpeg 2000 is a much larger files size than a #8 regular jpeg, and if compensated to match file size, the regular jpeg preserves more detail. And anyway, hardly any applications support jpeg 2000, so what's the use? Althepal 03:27, 8 January 2007 (UTC)
- I wonder if it would be okay to insert into the article criticism that isn't backed by any notable publication. I too find J2K disappointing. The only thing it might do better than JPEG is extreme compression (say 1/50), and that's not what most people are after. The only general use for it I can think of is lossless photos compression that compresses better than PNG and is somewhat compatible. But that isn't too promising considering JPEG-LS almost always compresses better and always requires much less horsepower. Maybe the situation could be better with better encoders (and maybe they have improved sincen I last tested)?
So what do you reckon, should this be added in? ehudshapira 06:26, 17 June 2007 (UTC)
User ehudshapira wrote: The only thing it might do better than JPEG is extreme compression (say 1/50).
My reply: If you simply feed an image into JPEG 1991 and JPEG 2000 and do extreme compression on it, JPEG 2000 will definitely come out looking better. However, for extreme compression JPEG 1991 is just about as good as JPEG 2000 if you do things as follows in the 1991 compressor. First the compressor reduces the image size -- by a factor of two for each of horizontal and vertical, for instance. Then the smaller image is compressed in the ordinary JPEG 1991 way. Later, the decompressor decompresses it in the ordinary way, and then the image is zoomed back up by the factor of whatever it was reduced by. The consequence of reducing and re-expanding it is an image that suffers from some blurring artefacts. The re-expansion is done by interpolation. Blurring is not as objectionable to the human eye as the texas chain-saw massacre of blocking and ringing that happens in JPEG 1991 when you do extreme compression on it. What JPEG 2000 produces under extreme compression is a blurry image and it does so by reducing the image's resolution, which is the same thing as reducing the size. The 1991 standard doesn't include the feature of reducing and re-expanding for extreme compression. User sean 184.108.40.206 20:36, 5 July 2007 (UTC)
Perhaps, somebody can work it into the article.220.127.116.11 20:58, 1 January 2006 (UTC)
- It's an interesting test image; it has been saved at 20% quality (6.9kb), and the JPEG2000 image has been saved with the same file size.
- But I think JPEG2000 isn't better than JPEG at higher quality. It smooths more of the image and deletes some detail that JPEG would show.
- I have found another comparison with some levels of compression with the Lura Wave plugin for Irfanview : and these are the results:
- Images in EMBED tag (browsers with a JPEG2000 plugin)
- Images in IMG tag (browsers with naive JPEG2000 support, as Konqueror)
- The frist table are images without colour subsamplig (4:4:4), and the second with a 4:2:2 subsamplig.
- Sorry if my English is very poor.
- --Magnus Colossus 16:08, 16 February 2006 (UTC)
- i demand lena. 18.104.22.168 00:40, 27 July 2006 (UTC)
JPEG/JPEG 2000 comparision with JPEG images?
I don't understand why the test images provided here try to show the differences between JPEG and JPEG 2000 by showing them next to each other on a JPEG image. This is like comparing CD quality sound and HD quality sound by copying both of them on a Audio CD... --Abdull 21:01, 12 June 2006 (UTC)
I just came here to say the same thing. They took a JPEG 2000, turned up the loss, and then to show it to people on Wikipedia, they re-compressed it as a JPEG? If the final JPEG as saved at really high quality settings, then it's not as bad as the recording example given above, but it is still NOT VALID. It can NOT be a fair comparsson of the artifacts of JPEG-2000 vs JPEG when they're both a JPEG! It needs to be something lossless. I assume PNG is the most widely supported by web browsers?
Is it possible, that the images of the JPEG/JPEG 2000 comparison have been mixed up? It's obvious, that the doggie's picture called "JPEG" looks way sharper and shows much more detail than the JPEG 2000 picture. I don't really know JPEG 2000 from own experiences, but wasn't it intended to be superior compared to JPEG? Regards, Elmario —Preceding unsigned comment added by 22.214.171.124 (talk) 04:41, 9 August 2009 (UTC)
- They haven't been mixed up: if you zoom into the JPEG one, you will see JPEG artifacts (8x8 blocks), but if you zoom into the JPEG 2000 one, you will see that it looks completely different. It's not surprising that the JPEG one looks sharper, since bluriness is a JPEG 2000 artifact. --Zundark (talk) 08:52, 9 August 2009 (UTC)
Section on Techical Discussion
I've read the techinal description section, and I think it can be re-written a fair bit. In particular, the description can be organized much better, and the rich feature set offered by J2K can be made more explicit (eg: the progressive nature of the code-stream, compressed domain manipulations, and so on).
I'll probably be able to do this in a little while - but since I'm new to editing Wiki, I thought I'd make a post first and get people's opinions on this before I did anything substantial.
--Brokentooth 22:21, 20 July 2006 (UTC)
I don't know how to use WIKI, but its stated that wavelet compression is more computationally intensive than regular jpeg. This is simply not true, wavelets are FAST/simple TRANSFORMATIONS!! compared to DCT based transforms.
Jpeg2000's ability to store lossless images is an important difference, as well as its support for higher colour bitdepth.
Also its a ability to perform partial/resolution decompression is important. The FBI use a wavelet image format just for this reason, so that finger print databases can be analysed quickly. Ronx —Preceding unsigned comment added by 126.96.36.199 (talk) 04:58, 23 May 2009 (UTC)
Section on Coding in Technical Discussion
The section about layers and packets is confused. Layers are not groups of packets, packets are groups of layers. See "JPEG 2000 Part I Final Committee Draft Version 1.0" (ISO/IEC JTC 1/SC 29/WG 1 N1646R) Page 61, Annex B.8 Packets.
- Regardless, however, of the monetary cost of licensing JPEG2000 patents, it would still be impossible to comply with the Debian Free Software Guidelines (the acid test of software freedom) with freely-licensed patents unless the licenses were redistributable and irrevocable, even if the licensed application is modified. This alone could hamper adoption of JPEG 2000 for web purposes as it would exclude open-source web browsers (most notably Gecko-based browsers) and popular LAMP web applications.
- I know very little about free software licensing in general, but surely it could be implemented in a library with free software compatible license (even tho the license itself obviously wouldn't be a free software license) and therefore included as a non free software portion of a free software application. Non free software proponents may not want to do this, but it sounds to me like this is suggesting it's not possible to have JPEG2000 support in freesoftware which I'm pretty sure isn't true. Besides that can't you write the source code even if you can't distribute the binaries? Isn't this how XviD works? Also, VLC seems to have survived despite including support for the patented XviD...? Not to mention GIF was supported while it was patented. I understand why free software proponents dislike (or hate) patents, but I feel the current wording is misleading as it appears to suggest patents must be a deathnell Nil Einne 15:12, 11 January 2007 (UTC)
Yes, Debian can put software in the non-free section when it doesn't meet the DFSG, and has before.
I wanted to bring this up because doing a patent search on "wavelet transform" and "wavelet image" seems to bring up many patents, possibly around 500 or so. So the statement about the heavily patented area seems to be true on it's face although there's not a study or a white paper to point to. Just a patent search will bring the facts to light.
this phrase: "JPEG 2000 is not widely supported in present software due to the perceived danger of software patents on the mathematics of the compression method, this area of mathematics being heavily patented in general."
is invalid. Do it based on any research?
"perceived danger of software patents " can't be the reason of not widely support. The work processed to clean up JPEG2000 standart from submarine patents is a lot bigger than for example JPEG or GIF. But JPEG and GIF is more sphread now. So this assumption on reason of "not widely supported " must be removed ASAP, it is just lie.
- You can argue about whether there's a "danger of patents" or not, but there is obviously a *perceived* danger. I came here looking for the reasons why W3C rejected jpeg2000. IIRC it was due to perceived patent danger. Anyone got info on this? Gronky (talk) 16:15, 18 February 2009 (UTC)
is there any fact for this "Because of this statement, controversy remains in the software community concerning the legal status of the JPEG2000 standard." ? Looks like it is somebody's opinion. —Preceding unsigned comment added by 188.8.131.52 (talk) 16:23, 5 March 2009 (UTC)
"JPEG 2000 is included in most Linux distributions."
What is this supposed to mean? AnonMoos 03:03, 5 October 2007 (UTC)
- I think it means that most Linux distributions SUPPORT it as a standard. Inclusivedisjunction (talk) 07:01, 19 January 2008 (UTC)
Well, what does that mean, then? Debian Linux has the libopenjpeg2 package, but only eight other packages use it, only two of them are actual applications, and only one of the two (krita) deals with normal bitmapped images. In other words, AFAICT virtually no applications can show or save JPEG 2000 images. /JöG (talk) 21:08, 28 November 2012 (UTC)
- Just a clarification: ImageMagick and GraphicsMagick are able to display and save JPEG 2000 files. Ubuntu can show JPEG 2000 in the thumbnails and is able to open them. --Cantalamessa (talk) 14:32, 29 November 2012 (UTC)
machine judgment of quality
- Images machine-judged to be of equivalent quality for both compression schemes often look better to humans in JPEG 2000 at low bitrates.
I am removing the above because all it means is "A certain machine test of image quality doesn't work". If humans judge that one image is better quality than another, then a working metric will give them different scores. The whole purpose of such a metric is to predict human judgment of quality. TomViza 19:48, 4 November 2007 (UTC)
The tone, partiality, article structure, and difficult readability all need to be addressed. The article is not only extremely technical it is addressing the perceived advantages of JPEG2000. Non-technical users will not understand this article even at the introduction. It needs the more technical bits moved to another section and a gentle introduction, history, and body copy must be written. --KJRehberg (talk) 05:07, 17 January 2008 (UTC)
What is the perf difference?
The article makes it sound like the encoding and decoding performance is significant, but I see no hard numbers. I looked for them on the web, and couldn't find any either. If someone has some speed and/or memory numbers, it would be nice to add, because this article has the important numbers in many other places. KeithCu (talk) 10:17, 15 March 2008 (UTC)
It seems a bit silly to me to feature thumbnails of comparisons, since at low resolution all three versions are indistinguishable. Of course they can click on the images for a larger image, but it's preferable to be able to see the artifacts alongside the explanatory text. I'd suggest creating an actual thumbnail-sized demonstration image, and making the image somewhat bigger (e.g. 300px wide). Dcoetzee 06:15, 6 August 2008 (UTC)
Comparison w/ Mr. Sid?
As I understand it, Mr. Sid (.SID from Lizard Tech) is still the industry standard for compressing geospatial imagery but I see no mention of this format. JPeg 2000 is the new kid on the block. —Preceding unsigned comment added by 184.108.40.206 (talk) 21:37, 10 October 2008 (UTC)
Basic (Part1) and Advanced (Part2)
Applications are compared regarding their support for Part1 and Part2. Perhaps the table JPEG 2000 image coding system - Parts could be more verbose on what the Parts are about? "Extensions, (.jpx, .jpf)" is not sufficient IMHO.--220.127.116.11 (talk) 18:07, 11 March 2010 (UTC)
Having searched on the web for converters from JP2 to JPG (or anything else) and found many that are quite pricey, I've since found that Acrobat version 8 can read jp2, and this is worth noting in the table. MS Office 2007 doesn't appear to support jp2 import. 18.104.22.168 (talk) 11:00, 21 April 2010 (UTC)firstname.lastname@example.org
The submitted picture labels file size in "KiB". Abbreviation standards are quite clear (see http://en.wikipedia.org/wiki/SI for example). The only acceptable abbreviation for kilobytes is kB. Postlewaight (talk) 18:20, 6 October 2010 (UTC)
In this section is the wording:
- "This step is called multiple component transformation in the JPEG 2000 language since its usage is not restricted to the RGB color model."
Typically chrominance subsampling is applied in YCbCr images because the Cb and Cr (i.e. Chrominance) are separate. I think the correct wording should be "... since its usage is not restricted to the YCbCr color model". Although it is in the standard, I don't really see how you would get benefit from applying it to RGB space. If someone more familiar with JPEG 2000 could explain, it would improve the article. — Preceding unsigned comment added by 22.214.171.124 (talk) 15:00, 2 January 2012 (UTC)
In the Tiling section it says:
- "The disadvantage of this approach is that the quality of the picture decreases due to a lower peak signal-to-noise ratio."
PSNR is a measurement of the quality therefore this statement is saying "It's bad because the results are not good". I would expect tiling to be a trade off between 1. dividing the image into more manageable chunks and 2. introducing more chunks adds overhead in the case of a fixed bit rate budget. — Preceding unsigned comment added by 126.96.36.199 (talk) 15:04, 2 January 2012 (UTC)
Shouldn't wikipedia actually provide a .jp2 image for people to view (even if most browsers would still show the "broken image" symbol)? There doesn't actually seem to be a Jpeg-2000 format file anywhere in the article or the links! — Preceding unsigned comment added by 188.8.131.52 (talk) 00:13, 28 April 2012 (UTC)
- It couldn't be hosted at the moment, it is an unsupported file type. A repository of weird media formats for quick tests would be nice. Check out Mplayer, I vaguely recall that they have lots of test files. –184.108.40.206 (talk) 22:31, 21 January 2014 (UTC)
best of jpeg for photo graph
I have a PSD file that is full quality but when I try to save it as a JPG file, the quality is a little bit less. What I want to ask you is..... how do I to save the image in JPG or JPEG or jpeg2000 format preserving the quality of the image? what format is best of foto print quality ?
pls help me — Preceding unsigned comment added by 220.127.116.11 (talk) 16:11, 9 April 2013 (UTC)
- ".jpg" and ".jpeg" are just filename extensions, they both are used for JPEG, which is always lossy. JPEG 2000 is not JPEG; JPEG 2000 can be lossy or lossless. If you want to preserve the quality completely, you need a lossless format. A free lossless compression format viewable in web browsers is PNG. If you want to save image in an open format, but preserve data like layers (though not viewable in a web browser), try OpenRaster. --AVRS (talk) 16:55, 9 April 2013 (UTC)
This article uses jargon for which there is no Wikipedia entry, like "codestream" for example. A search for "codestream" on the wikipedia landed me back on this article. This is not what Wikipedia articles are supposed to be like, in my opinion. Feraudyh (talk) 17:04, 7 November 2013 (UTC)
- I moved the explanation to the lead section (second paragraph.) Apparently contributors here don't agree on a spelling (codestream vs. code stream vs. code-stream). I added Video compression picture types to See also, found in a search for "code stream". –18.104.22.168 (talk) 22:22, 21 January 2014 (UTC)