メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

JPEG XL, AVIF, and WebP2!

コメント

4件のコメント

  • Lukas

    I fully support adding next gen delivery formats to C1. However a note on OP's post: I believed WebP2 has been abandoned. Also, for images/photography I don't find AVIF very appealing although support for that would of course be positive.

    JPEG XL is the format I'm really looking forward to, as it is superior to its competition and has the best chance of becoming the new standard. I'm sure the folks at C1 are aware of it and its benefits so I won't go into them here. Personally I think I won't upgrade to a newer version of C1 until JPEG XL export (and of course editing, though I work mostly in RAW) is implemented. Yes, it's a killer feature, so I hope you're already working on it! Adobe and Serif have just updated their software with JPEG XL support so now I'm waiting for C1 to fill in the gap in my workflow.

    2
  • Platon B

    In JPEG, the sky is covered with ugly pixel stripes! This is very harmful to landscape photographers. Here are some examples:

    https://500px.com/photo/1052877550/sky-and-lake-in-the-late-evening-by-platon

    https://500px.com/photo/1056003599/descent-into-the-pond-and-reflection-of-the-city-building-in-the-evening-by-platon

    Very much I ask to add the ability to export to modern formats.

    0
  • FirstName LastName

    Now that Google and Mozilla no longer plan to support JXL, I strongly recommend to focus on AVIF because its support is still getting better. We need a successor for the limited JPEG fast.

    0
  • Lukas

    Mozilla is neutral about it and the user base is demanding JXL quite vocally, so support is bound to come. Sure, support for opening AVIF is nice as those files might show up, but why would photographers want to export in AVIF when it doesn't even support resolutions over 4K without artifacts? AVIF is not widely used either so the two formats are both effectively new kids on the block trying to replace the currents standard format. Affinity has JXL support but not AVIF. Darktable just came out with JXL support.

    If only one the two can be supported in the short term in a raw processor, it should be the one with higher quality (JXL). If someone really needs to send AVIF images, they could export in JXL and use some 3rd party app to convert it to AVIF. Going the other way around would mean a poorer quality image to begin with.

    Yes, the web browser situation looks weird right now, but in the authoring realm JXL is the one gaining support. I wouldn't deliver a high quality photo of mine in AVIF. So it seems like first come the pro software and the browsers evidently later... (And yes, I'm also speaking from the point of view that I believe JXL is technically superior and thus I'm hoping for it to become popular asap, even though the politics of web formats is looking trickier for JXL than maybe expected.)

    1

投稿コメントは受け付けていません。