Become a fan of Slashdot on Facebook

 



Forgot your password?
typodupeerror
×
AI

JPEG Committee is Banking on AI To Build Its Next Image Codec (thenextweb.com) 43

Joint Photographic Experts Group (JPEG), a committee that maintains various JPEG image-related standards, has started exploring a way to involve AI to build a new compression standard. From a report: In a recent meeting held in Sydney, the group released a call for evidence to explore AI-based methods to find a new image compression codec. The program, aptly named JPEG AI, was launched last year; with a special group to study neural-network-based image codecs. Under the program, it aims to find possible solutions towards finding a new standard. To do that, it has partnered with IEEE (Institute of Electrical and Electronics Engineers) to call for papers under the Learning-based Image Coding Challenge. These papers will be presented at the International Conference of Image Processing (ICIP) scheduled to be held at Abu Dhabi in October.
This discussion has been archived. No new comments can be posted.

JPEG Committee is Banking on AI To Build Its Next Image Codec

Comments Filter:
  • Smart (Score:5, Funny)

    by 110010001000 ( 697113 ) on Thursday February 20, 2020 @02:12PM (#59747368) Homepage Journal

    They are running it against images gathered on the Internet. The result is the new codec will be able to compress images of cats and naked women by 99%.

  • While I am all for efficiency and using as little bandwidth as possible. Being the standard home network connections are now measured in gigabits per second or more commonly in megabits per second vs kilobits per second, or bits per second which were common 20/30 years ago. Most speed inefficiencies are not from our image codecs but from people not using the existing ones, Not saving images in the appropriate size, and most commonly hooking over to external (ad servers) which just take so long to respond

    • by un1nsp1red ( 2503532 ) on Thursday February 20, 2020 @02:26PM (#59747410) Homepage
      More people are accessing the internet via phones than computers on a home ISP connection. And many of those people are still paying by the GB of data transferred. More compression, less data sent.
      • by mspring ( 126862 )
        More compression, less data sent, more crap getting added.
      • More people are accessing the internet via phones than computers on a home ISP connection. And many of those people are still paying by the GB of data transferred. More compression, less data sent.

        So maybe we should be looking at a way to "compress" the several megabytes of Javascript pulled down by every page for tracking purposes.

        All I'm insinuating is that in 2005, "the problem" was that image files took up huge amounts of a web page's bandwidth use. Today... it's crap we didn't ask for. Yes, I recognize that improving two things is better than improving one thing. But personally I'd rather pay more monthly to transfer inefficiently compressed content over all the advertisement and metrics-ga

    • by Bengie ( 1121981 )
      It's difficult to solve social issues with technology, but if they can make images 10% smaller, that would not only reduce bandwidth, but storage, caching, and every step from end-to-end.
    • As a hobbyist photographer, formats are just as bad as they were 20 years ago. You have your RAW file from your camera...then DNG, which compresses it slightly and retains nearly all the RAW info...but Adobe's implementation retains all changes, so you get a full size file even after cropping. Plus...it's basically an Adobe-only format...not many other people use it

      So what does one do? Photo tools seem to like TIFF...because apparently disk space means nothing to people....PNG seems good, but no one rea
      • by ceoyoyo ( 59147 )

        What you're asking for is pretty much impossible. RAW files are the most storage efficient because they accurately reflect the actual amount of data acquired by the camera sensor (and are usually losslessly zipped on top). When you convert a RAW to TIFF it at least triples in size because instead of having to store only one value per pixel like the RAW, now it has to store one each for the R,G and B channels. You can losslessly compress that (TIF usually does) but it's still bigger.

        If you want lossy compres

      • by darkain ( 749283 )

        RAWs straight out of camera are actually already compressed. This is why the file size varies from image to image of the same exact resolution. This is also why file sizes are larger for higher ISO (more grain, less commonality within the pixels). If you want the fastest way to check this, just look at your camera's "remaining photo" counter (whatever it happens to be called), and adjust from ISO 100 to ISO 6400. Without taking a single pic, the "available" storage will appear to drop. This is also why when

        • Not true. There are hundreds of RAW formats and most are not compressed. Many are variations on TIFF type.

          • by darkain ( 749283 )

            "File compression techniques that lose some of the original data are called ‘lossy’. However, ‘lossless’ compression is also available. This is used by Canon digital cameras when the highest resolution image is stored as RAW data."

            Literally Canon's own documentation. And yes, there are other formats out there by other manufacturers, but they're similar nature.

            https://cpn.canon-europe.com/c... [canon-europe.com]

      • by slaker ( 53818 )

        New iPhones and some high end cameras also support a format called HEIC (high efficiency image codec) which I understand involves using x.265 video compression on a single (presumably huge) bitmap.

        This doesn't help RAW or DNG in particular, but I understand it to be a less lossy yet smaller output format when compared to JPEG, albeit at a cost of greatly increasing the CPU/GPU needed to decode it.

        I pulled some HEIC files off a dead iphone a couple weeks ago. I'd never even heard of the format before. It wou

      • I want a lossless archive format that takes less space than my RAW files and that can guarantee that when I find the photo 30 years from now, I won't have trouble opening it. Is that too much to ask?

        • RAW is already compressed, and is pretty much as small as you can make the photo without losing anything.
        • DNG undoes the Bayer filter mosaicing [wikipedia.org], assigning an individual R, G, and B value to each pixel (in the raw data, a block of 4 pixels has one red, one blue, two green). Exactly how you do this demosaicing c
    • A new codec doesn't necessarily need to target better compression or lower file sizes as the ultimate goal. One could just as easily make an argument that because so much of computing has switched to mobile devices that a codec which is computationally less expensive would be a major benefit for battery life.
    • Being the standard home network connections are now measured in gigabits per second or more commonly in megabits per second

      There are still tons of real-world cases to be found using cellular data, where you are hard pressed to get even 1MB/s. Compression still matters very much.

    • YES, bandwidth still matters.

      NO, we don't need yet-another-codec. We already have FLIF [flif.info] (Free Lossless Image Format) for BOTH lossless and lossy [flif.info] encoding.

  • by xack ( 5304745 ) on Thursday February 20, 2020 @02:23PM (#59747402)
    Most new image and media formats are an excuse to keep patented technology in use as the old formats patents expire. Plus we have enough image formats and it always is a struggle to get web browsers to support new ones especially Safari and Internet Explorer. Transparent PNGs were a decade long nightmare and WebP is even worse.
    • by AvitarX ( 172628 )

      I've still seen more webp images than jpeg 2000, and it's far newer.

      • Looks like webp has better support; that likely has a lot to do with it.

        webp [caniuse.com]: works in everything except IE and Safari.

        jpeg 2000 [caniuse.com]: only works in Safari.

        • by AvitarX ( 172628 )

          I'd bet the most common use of jpeg2000 is in PDF files, but Acrobat 5 is still a pretty common target compatibility and doesn't support it, and even the Adobe presets for newer versions still default to regular jpeg.

          Acrobat 6+ support jpeg2000, so that's a lot of instances of software.

          • by dwywit ( 1109409 )

            The most common use of JPEG2000 is digital cinema. Every frame in a Digital Cinema Package (DCP) is JPEG2000, and it's heavily compressed.

            Commercial editing software outputs direct to JPEG2000 and thence to DCP, but I did it once on Debian using ffmpeg and a toolset called OpenDCP.

            The original MP4 was exported to a directory of frames in lossless TIFF - each frame ~2 - 4 MB, then those were converted to JPEG2000, where each frame was about 1/10 the size of the TIFF. And no compression artifacts even when sh

            • That makes a lot of sense.

              Since it allows for frame exact splicing and frame by frame editing with minimal loss.

              Also, since the format can be lossless, one could presumably do the editing lossless if needed.
              • by dwywit ( 1109409 )

                It's possible, but it's more common to do much of the editing on a low-res proxy. That way you can use commodity PCs for a lot of the editing, and only bring in the heavy-hitters when needed, e.g. compositing high-def CGI into the "live" footage. I had to edit a low-def copy of my first short film, because the footage from the camera was 1280x720, and my computer at the time couldn't handle that. Edit the proxy at leisure, then apply the editing cuts & transitions to the high-def footage for final outpu

      • I don't recall ever seeing a webp image and I have a habit of viewing the image properties.
        • by AvitarX ( 172628 )

          I had two yesterday here (https://en.todocoleccion.net/postcards-religious-in-memoriam-cards/bonita-estampa-religiosa-antigua-sanctus-rochus~x41275298)

          PDF supports jpeg2000, but I don't think it's very often used.

          • by dj245 ( 732906 )

            I had two yesterday here (https://en.todocoleccion.net/postcards-religious-in-memoriam-cards/bonita-estampa-religiosa-antigua-sanctus-rochus~x41275298)

            PDF supports jpeg2000, but I don't think it's very often used.

            The main image on that page looks like a jpg to me.

            • by AvitarX ( 172628 )

              So it does.

              right click save as gets a webp though

              • by AvitarX ( 172628 )
                Actually, I take that back, it looks like it serves browser dependant.

                <picture>
                <!--[if IE 9]><video style="display: none"><![endif]-->
                <source type="image/webp" srcset="https://cloud10.todocoleccion.online/postales-religiosas-recordatorios/tc/2014/01/28/00/41275298.webp">
                <!--[if IE 9]></video><![endif]-->
                <img src="https://cloud10.todocoleccion.online/postales-religiosas-recordatorios/tc/2014/01/28/00/41275298.jpg" alt="Postales: BONITA ESTAMPA RELIGIOSA ANTI
          • by tlhIngan ( 30335 )

            PDF supports jpeg2000, but I don't think it's very often used.

            JPEG2000 is used when you need lossless encoding. It's used by some scanning machines that can directly send you an email with the scanned document as an image. The document is either in PDF or JPEG2000 format.

      • by Kjella ( 173770 )

        I've still seen more webp images than jpeg 2000, and it's far newer.

        If I recall correctly there was a lot of fear that wavelet compression was covered by patents and nobody big wanted to take point on it. Whereas webp is just the single image version of webm, which Google is using extensively for YouTube. So it should be very safe from an IP rights perspective.

  • ohhhh, this will end in tears:

    Count the dots.
    - Dots?
    The dots! Look, look.
    "Every single detail is", dot-dot-dot, "perfect".
    Okay? There are three dots in that ellipsis, which is the correct number of dots.
    However, in the message that I sent her, there are four dots, which is incorrect.
    Thus, not perfect.
    It was a joke.
    - Was it?

  • The best text compression algorithms use dictionaries common to both the encode and decode ends, I guess this is the image-based equivalent. Need the AI to do the searching for optional representations within the scope of the dictionary.

  • Blockchain (Score:4, Funny)

    by CubicleZombie ( 2590497 ) on Thursday February 20, 2020 @02:51PM (#59747496)

    They should definitely use blockchain in the new format. AI just isn't enough.

  • ...so we're gonna use a universal function and gradually alter its weights until we think it does what we want.

    Because Oooohh, "AI"!

    This is literally the same as if some company in the 50s had gone "Try our new WonderJelly! Just as tasty as the old one. But now with more *atom*!"

    I guess they haven't heard of EXTRA BIG ASS FRIES yet ...

  • Ahem, it's "sex" not "gender"; the latter applies to words, not objects.

    https://tech.slashdot.org/stor... [slashdot.org] seems to indicate we're moving in the wrong direction.

  • I get security updates for various image programs / libraries all the time.
    How is anyone gonna check AI-written code for vulnerabilities?
    Will there even BE human comprehensible source code produced?

    I suppose an AI-BlackHat might work, but that would inevitably escape into the wild.
  • Didn't Richard do this already with Gilfoyle's AI?

Work without a vision is slavery, Vision without work is a pipe dream, But vision with work is the hope of the world.

Working...