215
if you could standardise a file format for a specific task what would you pick and why (lemmy.ml)
submitted 3 years ago* (last edited 3 years ago) by to c/linux@lemmy.ml
286 comments fedilink hide all child comments
 

if you could pick a standard format for a purpose what would it be and why?

e.g. flac for lossless audio because...

(yes you can add new categories)

summary:

  1. photos .jxl
  2. open domain image data .exr
  3. videos .av1
  4. lossless audio .flac
  5. lossy audio .opus
  6. subtitles srt/ass
  7. fonts .otf
  8. container mkv (doesnt contain .jxl)
  9. plain text utf-8 (many also say markup but disagree on the implementation)
  10. documents .odt
  11. archive files (this one is causing a bloodbath so i picked randomly) .tar.zst
  12. configuration files toml
  13. typesetting typst
  14. interchange format .ora
  15. models .gltf / .glb
  16. daw session files .dawproject
  17. otdr measurement results .xml
you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 3 years ago (2 children)

Unpopular opinion but webp isn't bad it just needs wider support, but maybe I'm unaware of its actual shortcomings in which case please educate.

Also I wonder if it's possible to have a single image format for all those uses but also RAW?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 3 years ago* (1 child)

    Here's a little article which highlights jxl well. https://chipsandcheese.com/2021/02/28/modern-data-compression-in-2021-part-2-the-battle-to-dethrone-jpeg-with-jpeg-xl-avif-and-webp/

    I do not think it's mentioned there, but I think webp and also it's indirect successor avif afaik, both lack progressive loading which is not optimal for website loading. It's has incremental loading which I think is akin the the old dial up time of loading top to bottom row for row. They proclaim progressive decoding is costly on memory and cpu, but progressive gives the best user experience imo.

    Lastly a fringe issue, re-encooding multiple times. The good old reason why jpgs turn into trash over time because people encode instead of save images. Or because sites re-encode when uploading. Jxl wins here. It also is very easy to see why jpg turns into what it does rather quickly.

    https://www.reddit.com/r/AV1/comments/ju18pz/generation_loss_comparing_jpeg_webp_jxl_and_avif/

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years ago

    I also like the idea of incremental loading, even if it's not that relevant anymore. Also, I don't think your example of generation loss is enough as it's just one image, I would like to see multiple randomly picked images passed through the same process but if the results are the same as here or barely anymore loss than the best option for any given image I do think that's a good result to aim for.

  • permalink
  • fedilink
  • source
  • parent