▲ 104 ▼ Just saw $6 per gallon at the chevron on my way to work. (hexbear.net) submitted 2 weeks ago* by Johnny_Arson@hexbear.net to c/chapotraphouse@hexbear.net 76 comments fedilink hide all child comments
[–] chgxvjh@hexbear.net 6 points 2 weeks ago (10 children) Isn't AVIF better? permalink fedilink source parent hideshow 10 child comments replies: [–] ashinadash@hexbear.net 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! permalink fedilink source parent hideshow 3 child comments replies: [–] segfault11@hexbear.net 24 points 2 weeks ago (2 children) permalink fedilink source parent hideshow 2 child comments replies: [–] ashinadash@hexbear.net 10 points 2 weeks ago* (1 child) Y'all best get informed ⓘ Remember to enable JPEG-XL support in your browser, even on your phone! permalink fedilink source parent hideshow 1 child comment replies: [–] Johnny_Arson@hexbear.net [S] 3 points 2 weeks ago ashinadash: I sell PNG and PNG accessories. permalink fedilink source parent [–] into_highest_invite@lemmygrad.ml 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. permalink fedilink source parent hideshow 5 child comments replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago (4 children) Kinda makes sense that storing image would be a subset of storing videos. permalink fedilink source parent hideshow 4 child comments replies: [–] into_highest_invite@lemmygrad.ml 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. permalink fedilink source parent hideshow 3 child comments replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* (2 children) You are still storing a key frame every couple of seconds or so permalink fedilink source parent hideshow 2 child comments replies: [–] into_highest_invite@lemmygrad.ml 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 permalink fedilink source parent hideshow 1 child comment replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* To me it's honestly a lot of And the results in data compression aren't different enough to use anything with less wide software support. permalink fedilink source parent
[–] ashinadash@hexbear.net 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! permalink fedilink source parent hideshow 3 child comments replies: [–] segfault11@hexbear.net 24 points 2 weeks ago (2 children) permalink fedilink source parent hideshow 2 child comments replies: [–] ashinadash@hexbear.net 10 points 2 weeks ago* (1 child) Y'all best get informed ⓘ Remember to enable JPEG-XL support in your browser, even on your phone! permalink fedilink source parent hideshow 1 child comment replies: [–] Johnny_Arson@hexbear.net [S] 3 points 2 weeks ago ashinadash: I sell PNG and PNG accessories. permalink fedilink source parent
[–] segfault11@hexbear.net 24 points 2 weeks ago (2 children) permalink fedilink source parent hideshow 2 child comments replies: [–] ashinadash@hexbear.net 10 points 2 weeks ago* (1 child) Y'all best get informed ⓘ Remember to enable JPEG-XL support in your browser, even on your phone! permalink fedilink source parent hideshow 1 child comment replies: [–] Johnny_Arson@hexbear.net [S] 3 points 2 weeks ago ashinadash: I sell PNG and PNG accessories. permalink fedilink source parent
[–] ashinadash@hexbear.net 10 points 2 weeks ago* (1 child) Y'all best get informed ⓘ Remember to enable JPEG-XL support in your browser, even on your phone! permalink fedilink source parent hideshow 1 child comment replies: [–] Johnny_Arson@hexbear.net [S] 3 points 2 weeks ago ashinadash: I sell PNG and PNG accessories. permalink fedilink source parent
[–] Johnny_Arson@hexbear.net [S] 3 points 2 weeks ago ashinadash: I sell PNG and PNG accessories. permalink fedilink source parent
[–] into_highest_invite@lemmygrad.ml 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. permalink fedilink source parent hideshow 5 child comments replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago (4 children) Kinda makes sense that storing image would be a subset of storing videos. permalink fedilink source parent hideshow 4 child comments replies: [–] into_highest_invite@lemmygrad.ml 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. permalink fedilink source parent hideshow 3 child comments replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* (2 children) You are still storing a key frame every couple of seconds or so permalink fedilink source parent hideshow 2 child comments replies: [–] into_highest_invite@lemmygrad.ml 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 permalink fedilink source parent hideshow 1 child comment replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* To me it's honestly a lot of And the results in data compression aren't different enough to use anything with less wide software support. permalink fedilink source parent
[–] chgxvjh@hexbear.net 2 points 2 weeks ago (4 children) Kinda makes sense that storing image would be a subset of storing videos. permalink fedilink source parent hideshow 4 child comments replies: [–] into_highest_invite@lemmygrad.ml 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. permalink fedilink source parent hideshow 3 child comments replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* (2 children) You are still storing a key frame every couple of seconds or so permalink fedilink source parent hideshow 2 child comments replies: [–] into_highest_invite@lemmygrad.ml 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 permalink fedilink source parent hideshow 1 child comment replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* To me it's honestly a lot of And the results in data compression aren't different enough to use anything with less wide software support. permalink fedilink source parent
[–] into_highest_invite@lemmygrad.ml 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. permalink fedilink source parent hideshow 3 child comments replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* (2 children) You are still storing a key frame every couple of seconds or so permalink fedilink source parent hideshow 2 child comments replies: [–] into_highest_invite@lemmygrad.ml 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 permalink fedilink source parent hideshow 1 child comment replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* To me it's honestly a lot of And the results in data compression aren't different enough to use anything with less wide software support. permalink fedilink source parent
[–] chgxvjh@hexbear.net 2 points 2 weeks ago* (2 children) You are still storing a key frame every couple of seconds or so permalink fedilink source parent hideshow 2 child comments replies: [–] into_highest_invite@lemmygrad.ml 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 permalink fedilink source parent hideshow 1 child comment replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* To me it's honestly a lot of And the results in data compression aren't different enough to use anything with less wide software support. permalink fedilink source parent
[–] into_highest_invite@lemmygrad.ml 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 permalink fedilink source parent hideshow 1 child comment replies: [–] chgxvjh@hexbear.net 2 points 2 weeks ago* To me it's honestly a lot of And the results in data compression aren't different enough to use anything with less wide software support. permalink fedilink source parent
[–] chgxvjh@hexbear.net 2 points 2 weeks ago* To me it's honestly a lot of And the results in data compression aren't different enough to use anything with less wide software support. permalink fedilink source parent