party-sicko

you are viewing a single comment's thread
view the rest of the comments
[–] 21 points 2 weeks ago (11 children)

Good lord just look at that compression i-cant signature, everybody


Remember to enable JPEG-XL support in your browser, even on your phone!

  • source
  • parent
  • hideshow 11 child comments
  • [–] 6 points 2 weeks ago (10 children)
  • [–] 10 points 2 weeks ago (3 children)

    Ask jpegxl.info, AVIF performs better in some ultra-low-filesize/bitrate scenarions but JPEGXL is better in most other areas and supports progressive loading which is useful for internet purposes. Plus you can losslessly transcode old JPEGs.

    Personally I want to use lossy compression when I want to avoid a 35mb PNG, and AVIF just did not do as well as JXL with bringing the various massive PNGs down to size.


    Remember to enable JPEG-XL support in your browser, even on your phone!

  • source
  • parent
  • hideshow 3 child comments
  • [–] 3 points 2 weeks ago* (last edited 2 weeks ago) (5 children)

    honestly i'm really skeptical of all these video compression algorithms trying to be image compression algorithms. maybe i shouldn't be talking because mao quote but the image algorithm designers never had the advantage of deltas between frames. i assume there's some patent thing stopping apple from using jpeg-xl instead of heif (which is avif but for hevc instead of av1) but since i can't find any benchmarks i'm just speculating there. but it's all speculation since i don't really understand compression all that well.

    EDIT: found a paper by google suggesting heif and jpeg-xl have similar perception scores with jpeg-xl giving a slightly lower size. however, dark spots may have slightly worse perception with jpeg-xl.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 2 points 2 weeks ago (4 children)

    Kinda makes sense that storing image would be a subset of storing videos.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 2 weeks ago (3 children)

    it makes sense yeah but most of the space savings is from keeping one frame and then saving the next several frames as a series of just deltas. plus there's stuff you notice when it's moving but not so much when it's still. between that and the jpeg-xl benchmarks i'm comfortable speculating that there's probably maybe something to the idea of having separate lossy image and video codecs.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 2 weeks ago* (2 children)

    You are still storing a key frame every couple of seconds or so

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 weeks ago (1 child)

    you're right but even then i kinda think there are different things to optimize for. i found a benchmark i edited into my original post but honestly who the hell knows

  • source
  • parent
  • hideshow 1 child comment