Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
×
Graphics Software Microsoft

Microsoft Move to be the End of JPEG? 447

jcatcw writes "Microsoft Corp. will submit a new photo format to an international standards organization. The format, HD Photo (formerly known as Windows Media Photo), can accommodate lossless and lossy compression. Microsoft claims that adjustments can be made to color balance and exposure settings that won't discard or truncate data that occurs with other bit-map formats."
This discussion has been archived. No new comments can be posted.

Microsoft Move to be the End of JPEG?

Comments Filter:
  • Nup, No, Nada. (Score:5, Informative)

    by Whiney Mac Fanboy ( 963289 ) * <whineymacfanboy@gmail.com> on Thursday March 08, 2007 @09:14PM (#18284052) Homepage Journal
    Not going to end jpg - everyone dissatisfied with JPG is already using RAW. Everyone satisified with jpg will stick with jpg.

    This is going to enjoy the same sort of limited uptake as jpeg2000 vs jpg, mp4/wma/ogg vs mp3, png vs gif, etc.

    Few other things to note:

    1) The 'HD' doesn't stand for High Definition, it's just there to get the association with HD TV in consumers minds. *rolls eyes*

    2) This technology is patented to the hilt & the licensing terms for the HD Photo Device Porting Kit 1.0 licensing terms [wikipedia.org] specifically exclude copyleft (GPL style) licenses.
  • by Animaether ( 411575 ) on Thursday March 08, 2007 @09:26PM (#18284164) Journal
    PNG is a replacement for GIF, if anything. JPG files are much smaller than PNG files for typical photographs (though can be smaller for line art and the like), which will always leave JPG as the favorite much like FLAC isn't replacing MP3 anytime soon. The alpha channel in PNG is absolutely a nice perk, but thanks to the dim people at Microsoft never supporting it right until IE7, there wasn't much benefit over using GIF files. (Even though PNG did bi-level transparency just as fine as GIF files - even better, you didn't lose 1 palette entry - but that as an aside.)

    If you want a JPG replacement - a la OGG Vorbis over MP3 - try JPEG2000 or the lurawave stuff based on wavelets.
  • Re:PNG (Score:4, Informative)

    by Tumbleweed ( 3706 ) * on Thursday March 08, 2007 @09:26PM (#18284174)
    PNG was not supposed to replace JPEG; it was supposed to replace GIF. Unfortunately, thanks to massive delays in getting PNG support correctly working in IE, that never happened. Also, some people still insist they need animated GIFs, which PNG doesn't do (see MNG, which is nowhere). It's sad, as for most file sizes of images appropriate for GIF, PNG was way smaller (unless you get way, WAY small, as in under 150bytes or so (not kilobytes, BYTES). Also, Adobe is still unable to provide decent compression on the PNGs its software generates, so to this day, you need compression tools like pngout or pngcrush (pngout usually produces smaller files). Weird that you can still lossly compress a lossy image, but whatever.

    This won't be the end of anything unless it is unemcumbered by patents, and as a previous poster noted, it isn't. So, this is a non-event.

    Perhaps the group that came up with PNG can come up with a patent-free replacement for JPEG?
  • Exactly... (Score:2, Informative)

    by plasmacutter ( 901737 ) on Thursday March 08, 2007 @09:29PM (#18284216)
    this is the same story with windows media..

    the lesson is: the looser the licensing terms (while still maintaining an actual standard), the more widely used it will be.

    this means microsft, sony, and real can keep scrambling to their hearts content, but they wont touch a majority share when they treat formats like this.
  • by MichaelSmith ( 789609 ) on Thursday March 08, 2007 @09:30PM (#18284230) Homepage Journal

    It applies to the code

  • RAW? (Score:4, Informative)

    by Animaether ( 411575 ) on Thursday March 08, 2007 @09:32PM (#18284256) Journal
    "Everyone dissatisfied with JPG is already using RAW"?

    I don't know where you're getting that statement from. Everybody dissatisfied with JPG - which I can only imagine stems from the fact that it is lossy compression - is either using:
    PNG - because it's common, free to use, etc. etc.
    EXR - because it'll allow you to store whatever the hell you want
    GIF - because it's ubiquitious and is free to use nowadays (not that too many people cared a few years ago)

    'RAW' isn't used by anybody. 'RAW' does not exist. 'RAW' is a collective name for a shitload of formats by a smaller shitload of digital camera companies. And it is never "RAW".. it is never raw data.. it's compressed, stored integratedly or separately, encrypted or not (SONY, among other) and contains a bunch of camera data. The closest thing to a "RAW" format is, say, PFM (portable/pixel float map) or any other format that just stores every color(group) as a bunch of bytes in a long chunk with minimal to zero header/footer information whatsoever that you can only open if you know things like bitdepth and dimension. The closest thing to a unified 'RAW' format for cameras is Adobe's DNG (Digital Negative) - and that's finding slow (no?) adoption as it is. And the closest thing to a unified non-'RAW' format for cameras that isn't lossy compressed is TIFF. None of which you can toss on a website and make viewable in any of the major browsers without plugin installation (if even available!)

    That said, I agree with all your other points, especially point 1. Microsoft should be kicked even when down for jumping on the HD bandwagon with a product (or format) that has nothing whatsoever to do with HD.
  • Re:Nup, No, Nada. (Score:5, Informative)

    by dedazo ( 737510 ) on Thursday March 08, 2007 @09:32PM (#18284258) Journal

    everyone dissatisfied with JPG is already using RAW

    Actually, in the context of digital photography (which I assume is what you're talking about here, though JPEG is of course not limited to that) "everyone" uses TIFF. Just try to do freelance for a news agency and watch how quickly they ask you for TIFF files, which only the high-end cameras can generate.

    I suppose some of the smaller shops or newspapers and whatnot do use RAW, but for Reuters et.al if it's not TIFF you're not getting a paycheck. The same goes for the big stock photography companies and so on.

  • Some licenses are best meant to preserve the orginal work of art, not enforce the shared derivitaves thereof.

    Do you believe that your documentswill be subjected to MS's licensing terms when you save them in word? Of course not.

    The GPL does not cover works created using GPLd tools. Learn the difference between code & content.
  • by ceoyoyo ( 59147 ) on Thursday March 08, 2007 @09:39PM (#18284326)
    No. Documents you create with OO.org aren't all GPLed either. The GPL specifically applies to code. You own the copyright to anything you create, even if you use someone else's program to do it. Now, if you use someone else's work and modify it, such as modifying a GPLed program, THEN you have to abide by their copyright wishes.
  • 'HD Photo' blog (Score:2, Informative)

    by Animaether ( 411575 ) on Thursday March 08, 2007 @09:41PM (#18284352) Journal
    For more information on 'HD Photo' (damn I hate that name), check the blog at:
    http://blogs.msdn.com/billcrow/ [msdn.com]

    Hasn't been updated in a good while, but contains plenty of nice information. The various bitdepth storages alone make it an 'interesting' format if nothing else - though I'm sticking with EXR.. just a shame that doesn't offer lossy compression much yet - but then.. that's not its' purpose.
  • by creysoft ( 856713 ) on Thursday March 08, 2007 @09:47PM (#18284414)
    No.
  • Re:Nup, No, Nada. (Score:2, Informative)

    by dfghjk ( 711126 ) on Thursday March 08, 2007 @09:56PM (#18284516)
    It may be trivial as long as you don't care about the quality of the output. If that's the case, one would wonder why you shot RAW in the first place.

    RAW is not an image format. It's a dump of all the sensor data that can be used to create an image. A very substantial amount of processing is required, some of it subjective, to arrive at an image.
  • Re:RAW? (Score:3, Informative)

    by Goaway ( 82658 ) on Thursday March 08, 2007 @10:00PM (#18284544) Homepage
    The raw format of cameras is far more "raw" than PFM or any other RGB format. Camera raw formats save the actual output from the image sensor, before applying the numerous algorithms needed to massage the data into RGB form. The point of camera raw data is not just to avoid compression, it is to do the highly complex processing needed at a later stage, and allow for finer control over the resulting output.
  • Re:better example (Score:3, Informative)

    by arth1 ( 260657 ) on Thursday March 08, 2007 @10:19PM (#18284706) Homepage Journal
    (PNG having taken over for GIF)

    Really? And where exactly did you get that from?

    Well, this very web page you're staring at is a good example.
    I count 21 PNG files and 2 GIF files.
  • by cortana ( 588495 ) <sam@ r o b o t s.org.uk> on Thursday March 08, 2007 @10:27PM (#18284770) Homepage
    It is not faster [ubuntu.com], and in addition, it is much less space-efficient.
  • by SuperBanana ( 662181 ) on Thursday March 08, 2007 @10:33PM (#18284818)

    I don't know where you're getting that statement from. Everybody dissatisfied with JPG - which I can only imagine stems from the fact that it is lossy compression - is either using: (PNG, GIF, EXR.)

    You don't understand what "raw" images are used for. They're used PURELY in the acquisition phase. There isn't a (non-webcam/hideously-dumbed down) camera in the world that records to GIF, I don't know of a single camera on the market that records to PNG, and EXR is a very specialized format used mostly in "film" (ie movie production.) No still digital cameras on the market record to it.

    'RAW' isn't used by anybody. 'RAW' does not exist. 'RAW' is a collective name for a shitload of formats by a smaller shitload of digital camera companies.

    No, it's not. RAW = Canon's "raw" image format. "Raw" image formats are produced by many higher-end digital cameras. I'm sorry you don't understand the distinction between RAW and raw, but it does make it painfully obvious this isn't your area of expertise. It is mine: I've shot RAW images on my Canon dSLR for fun and profit for several years now. I shoot exclusively in RAW format because of the extra bit depth which makes adjustments much more 'transparent' (a level adjustment won't cause as much problems wit 10-12 bit data as it will with 8 bit, and you also have no compression artifacts.) I archive everything in the original Canon RAW format.

    Your characterization that "raw" formats are used by a "shitload of smaller digital camera companies" is also completely wrong. Canon's RAW and Nikons's NEF are by far the largest, most commonly used "raw" formats. Phase1 is probably up there with their digital camera backs. I'm now guessing, but Fuji is probably next (Fuji dSLRs were very popular a few years back, in part because the Fuji SuperCCD was superior to almost everything else on the market at the time), followed by Panasonic/Leica, followed by Pentax.

    Many point-and-shoot consumer cameras these days are incapable of shooting in a RAW mode; it's left to the "prosumer" models by most manufacturers.

    And it is never "RAW".. it is never raw data.. it's compressed, stored integratedly or separately, encrypted or not (SONY, among other) and contains a bunch of camera data.

    It most certainly is raw image sensor data; that's the whole point. "Raw" camera formats all use LOSSLESS compression. Yes, all of them contain incredibly useful EXIF-like data in them. This is not, despite your rant, a negative to anyone I know. Few manufacturers encrypt the data; Nikon encrypts the white balance info on one or two models (which happen to be the several-thousand-dollar professional digital SLR bodies.)

    In most cameras (certainly the Canons and Nikons), it is, in fact, "raw"; it represents the closest you can get to the original sensor data, with little or no processing (on Canon cameras, I believe they don't even do thermal noise subtraction prior to writing the RAW file; the file even contains the "dead" area of the sensor used for such compensation), and anywhere from 10 to 12 bits per channel precision. No white balance, brightness/contrast, gamma, or sharpening adjustments are applied before the data is recorded.

  • Re:jpeg replacements (Score:3, Informative)

    by gutnor ( 872759 ) on Thursday March 08, 2007 @10:42PM (#18284872)
    JP2000 was not lossless. It was just giving beter quality than JPEG at the same size ( think MPEG2 -> H.264 ).
    However JPEG 2000 is a pain to compress and render and is not a 'free format'. (also try to encode/render JPEG2000 images: unless you have a new Intel QuadCore you will feel the suffering of your machine. )

    With this HD Format, Microsoft says their algorithm comes close to JPEG2000 quality/size but with a very simple algo.
    Also Microsoft is making a lot of effort to standardise their stuff ( they tried first to license it for free, now they go to a standardisation process ). They also have the support of Adobe, which is not a bad thing when talking about image format.

    A strong point for HD-Format is that it covers the quality and feature range from JPEG-2000 to TIFF-Losless. So camera manufacturer could benefit from unified chipset that works from pocket camera to SLR. Or a flexible SLR chipset that cover the whole range of quality the user wishes.

    But anyway, good source of information as usual: http://en.wikipedia.org/wiki/Comparison_of_graphic s_file_formats [wikipedia.org]

  • by Lord Satri ( 609291 ) <alexandreleroux@gm a i l .com> on Thursday March 08, 2007 @11:01PM (#18285052) Homepage Journal
    I agree. In geospatial technologies (e.g. satellite imagery, aerial photography, GIS, topography, etc.) the GeoTIFF format [wikipedia.org] is commonly used for georeferenced raster data. Additionally, the BigTIFF format proposal [awaresystems.be] comes to the rescue to circumvent TIFF's 4 gigs maximum size.
  • by fabs64 ( 657132 ) <beaufabry+slashdot,org&gmail,com> on Thursday March 08, 2007 @11:03PM (#18285066)
    Basically it seems you've got 'patents' and 'copyright' confused.. not surprising really, it's a morass.
    The GPL is just copyright, it applies to the specific thing you created, if you were to come up with some amazing new compression algorithm and release the code under the GPL, without patenting it, that algorithm could be re-implemented with different code by anyone and they would not have to release their code under the GPL.
    The reason for a program like Bison having the output GPL'd, is that Bison actually creates lots of the output using its own code, ie, the Bison output HAS GPL code in it. Fortunately there's the exception which makes this a non-issue.
  • by rbanffy ( 584143 ) on Thursday March 08, 2007 @11:07PM (#18285096) Homepage Journal
    bzip2 is much more resource-intensive than gzip.

    In 2001 I considered using bzlib to compress some data files in the Brazilian electronic voting system and, since we had to support older, 386-class hardware with little memory, we went the gzip route.

    Later some Windows fanboy decided they should use .zip instead of .tgz for the files and someone else recoded that piece.

    Consider we are not talking only desktop PCs, but low-end embedded and photographic equipment.
  • by harmonica ( 29841 ) on Friday March 09, 2007 @12:22AM (#18285572)
    In theory, yes. There is a byte compression type in the PNG headers.

    The PNG people (some of them?) don't want to use this, though, for maximum compatibility of readers and files. I don't have a source handy, so take this with a big grain of salt.
  • by cooldev ( 204270 ) on Friday March 09, 2007 @12:25AM (#18285590)

    Before slamming the format, please read more about it. Regardless of what you think about Microsoft, I think it has great potential. Some highlights:

    • High dynamic range
    • Embedded ICC color profile
    • Lossy and lossless compression
    • Ability to decode part of the image without decoding the whole thing (see below)
    • Ability to crop, downsample (i.e. thumbnails), and rotate without decoding the whole image
    • Very efficient encoding and decoding, useful not only on the desktop, but also specifically designed for fast encoding and decoding on devices like digital cameras
    • High quality and small file size. (Around half the file size as JPEG (or) twice the quality. Claimed to be similar to JPEG 2000 without the additional performance and memory impact.)
    • TIFF-like container
    • The licence for the format *is* supposedly compatible with the GPL; only the source code for the reference implementation is not.

    Also, take a look at http://labs.live.com/photosynth [live.com] and http://blogs.msdn.com/billcrow [msdn.com]. To quote one thing from his blog:

    Because this is a compressed domain operation, the server never had to decode or re-encode the compressed data to create this low resolution "thumbnail" of the larger, high resolution image. The only work involved was to copy a portion of the compressed data and wrap it up in a container to make a new HD Photo file. This very small HD Photo file is sent across the network connection, and then decoded by the HD Photo codec on the client to provide the low resolution view required for the particular display.

    When zooming in to the fine details of a high resolution image, the HD Photo codec is able to very quickly extract an arbitrary rectangular region by accessing only the image tiles that overlap that region. Like the mipmaps described above, this is accomplished by simply extracting a small portion of the compressed data and building a new (and very small) HD Photo file to be sent across the network. The client receives and decodes this small file, combining it with the other segments required to display the required view.

    IMHO this seems like a well-balanced format that has most of the advantages of a cornucopia of different formats (JPEG, JPEG 2000, RAW, TIFF) without the corresponding disadvantages. If it's not successful, I at least hope something equivalent is!

  • by udippel ( 562132 ) on Friday March 09, 2007 @02:42AM (#18286276)
    Call me a licencing nazi, but OO.org is not GPL-ed.

    Just FYI: It uses The Lesser GPL (LGPL); so that derivative work could restrict some users' freedom.
    For the rest, your answer is fine. The suspicion of creative work automatically licenced under the code of the software is simply preposterous.
    [Waiting for Microsoft to invent this new twist: A copy of your MS-Office documents are auto-sent-to Redmond and from then onwards, you will have to pay for the use of your own documents. Sorry, even for the fair use of your own documents.]
  • Wrong. (Score:5, Informative)

    by linuxmop ( 37039 ) on Friday March 09, 2007 @04:23AM (#18286656)

    "PNG restarts the compression on each row"

    That is absolutely not true, and would be madness if it were. From the specification [w3.org], section 4.5.5:

    The sequence of filtered scanlines in the pass or passes of the PNG image is compressed (see figure 4.10) by one of the defined compression methods. The concatenated filtered scanlines form the input to the compression stage. The output from the compression stage is a single compressed datastream.

    The rest of your post is suspect now, of course.
  • by mgiuca ( 1040724 ) on Friday March 09, 2007 @06:44AM (#18287152)

    It applies to the code
    But patents extend to user data. HD Photo is heavily patented. The wiki says basically, "it's patented, but MS promises not to sue anybody who uses it but doesn't put it under the GPL."

    itsatrap.
  • by Salsaman ( 141471 ) on Friday March 09, 2007 @08:21AM (#18287462) Homepage
    I'm not aware of the details on this issue,

    Obviously

    but based on some web searches it sounds like it was fairly quickly resolved in a way that enabled GPL implementations

    Wrong ! See: http://en.wikipedia.org/wiki/HD_Photo#Licensing [wikipedia.org]

  • by cooldev ( 204270 ) on Friday March 09, 2007 @08:39AM (#18287550)
    If you look at the history people have been changing Licensing section of the Wikipedia article as we speak, but it still sounds to me like what I said is true: GPL software can use the format, but it would be have to be implemented based on the spec and not the reference implementation. I guess we will have to wait and see if it's officially added to the "Open Specification Promise".
  • by An dochasac ( 591582 ) on Friday March 09, 2007 @11:14AM (#18288780)

    'RAW' isn't used by anybody. 'RAW' does not exist. 'RAW' is a collective name for a shitload of formats by a smaller shitload of digital camera companies.

    No, it's not. RAW = Canon's "raw" image format. "Raw" image formats are produced by many higher-end digital cameras. I'm sorry you don't understand the distinction between RAW and raw, but it does make it painfully obvious this isn't your area of expertise. It is mine: I've shot RAW images on my Canon dSLR for fun and profit for several years now. I shoot exclusively in RAW format because of the extra bit depth which makes adjustments much more 'transparent' (a level adjustment won't cause as much problems wit 10-12 bit data as it will with 8 bit, and you also have no compression artifacts.) I archive everything in the original Canon RAW format.

    Since you claim expertise in this area and make some arguments that are, on the surface, convincing I feel it is important to point out mistakes in your arguments. Mistakes that even a relatively raw beginner such as myself are aware of. It appears that you have a very high level understanding of RAW, but to extend this into an understanding of the internals is a dangerous thing to do on Slashdot. First of all, since you speak of Canon, Nikon, Fuji, Pentax 'raw', I think you do understand that each of these formats are unique. The original poster is correct that some manufacturers (e.g. Sony) actually encrypt some of the data in their RAW format so that (for instance) the white balance can only be extracted using proprietary software. It may not be "a Sh!7l0ad of smaller manufacturers" from your point of view, but since I've seen relatively inexpensive Sony, Canon, Pentax and (the dearly departed) Minolta cameras spit out what their marketing material claims is "raw". The bottom line is that RAW is like tiff, only worse in that the data, data representation (byte order...), encoder and container may change from manufacturer to manufacturer. The only thing Canon RAW and Sony RAW are certain to have in common is that their marketing material, instruction book and camera's menu uses the three letters 'R', 'A', and 'W' to represent the name of the format (or in some cases 'r', 'a', 'w'. For a close look at the internals of many raw formats, I suggest you look at the source code to Dcraw. A few other mistakes, even really cheap webcams don't encode to gif (I don't know where that comment came from but they don't, the closed driver software takes the "raw" CMOS/CCD data and encodes it to GIF without letting the user see the raw data. If you're into astrophotography or have used a webcam on an opensource operating system, you'll understand more. Also, the raw file may be the closest consumers can come to the CCD's internal format, but by no means does is it identical to the RAW CCD data as it comes out of the CCD's analog light buckets (or CMOS gates) into the A/D. [cybercom.net]

"Life begins when you can spend your spare time programming instead of watching television." -- Cal Keegan

Working...