Home | Notifications | New Note | Local | Federated | Search | Logout
Phoronix@phoronix@masto.ai (2026-09-06 19:39:05) Slackware 16 Alpha 1 Available Following GCC 16.2, Glibc 2.44 & Binutils 2.47 Upgrade
The timing on Saturday's Slackware-based Zenwalk ISO "current milestone" update is now more clear with upstream Slackware having prepared what is its first alpha release of the upcoming Slackware 16...
https://www.phoronix.com/news/Slackware-16-Alpha ---Attachments--- image: https://s3.masto.ai/media_attachments/files/117/223/662/884/464/733/original/8a303a2c84962afb.webp
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:32:17) 逆にJXLはマキシマムな感じだから低品質な部分では適応の仕方を変えるくらいしてもいいような気もするけど
Ganbold@ganbold@sns1.hydranlab.com boosted: @arce (2026-09-06 19:04:43) Cloudy. Quiet. Early. Peaceful.
Ganbold@ganbold@sns1.hydranlab.com boosted: @mametsuko@mk.absturztau.be (2026-09-06 19:06:19) das Brot ---Attachments--- image: https://misskey-taube.s3.eu-central-1.wasabisys.com/files/webpublic-9a44b2ac-6c28-447d-a71b-dba57f49033f.webp
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:29:01) まあそもそもAV1のロスレスがDNxHRとかProResを想定してるとそれロスレスなのか？って感じだし、想定していないもんなあ
Ganbold@ganbold@sns1.hydranlab.com boosted: @mametsuko@mk.absturztau.be (2026-09-06 19:12:00) more fedi couples are ... welcome :neocat_cool:
Ganbold@ganbold@sns1.hydranlab.com boosted: @lina@vt.social (2026-09-06 18:25:33) TIL that nobody knows how to convert nits to lumens properly.
If you search the question, the AI overview is wrong. nits are a unit of brightness per area, so first of all, you need to multiply by screen area (in square meters).
1 nit = 3.426 lm/m2 (?)
But where does that constant come from anyway? If you search around, you will find various websites using that number. Others say it is just 1.
Apparently the 3.426 factor has to do with conversion from foot-lamberts... so completely unrelated.
1 nit = 1 cd/m2. 1 cd = 1 lm/sr. So 1 nit = 1 lm/sr⋅m2. For a perfectly uniform Lambertian surface, the integral over 180 degrees (the screen only emits forward) works out to π (3.14). So 3.426 is impossibly large.
But of course, real screens aren't uniform emitters. For OLED screens it would be a fairly small factor, since they tend to maintain brightness at steeper angles. LCD screens have much stronger falloff, which depends on the specific technology.
You'd have to integrate the brightness curve for a specific display to arrive at a number. Eyeballing and extrapolating the graphs in the previous link and plugging into Wolfram Alpha, I get around a factor of 2.9 for OLED and 2.2 for IPS, give or take. Probably a lot worse for TN. Take these numbers with a grain of salt, but that's the ballpark.
So, for a screen, lumens = k * nits * area (m2 ), where k is in the ballpark of 2.9 for OLED, 2.2 for IPS, and pi ideal. ---Attachments--- image: https://media.vt.social/media_attachments/files/117/223/241/753/290/260/original/34cde59415677cc3.png
Ganbold@ganbold@sns1.hydranlab.com boosted: @snow@cofe.rocks (2026-09-06 17:07:05) it's done!
honestly tastes p ok for a cheese this young
next time i think i'll add more spices
also can't wait to try making an aged one ---Attachments--- image: https://uploads.cofe.rocks/media/66fdcf432a477e821a82a42597bd51a330112c0509679dc6a8c69f398d06e8d3.jpg
image: https://uploads.cofe.rocks/media/7faab5a5b350a3555444338a8873e08030d481ea9e159cebc13fb650d7b2e413.jpg
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:18:06) クローズドソースでも今のLLMからしたらソースあるのとあまり変わらない気がする
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:17:05) あと、webで使うようなAVIFの品質50くらいとかだとJXLよりAVIFのほうが良いって話はあったっけ？今どうなんだろ
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:14:25) まあAVIFはRawに近いような写真データとかを扱う前提でやってないんで画像制作寄りで使うワークフローでどうやってもJXLより弱いだろうけど
mame muumimamma@mametsuko@mk.absturztau.be (2026-09-06 19:12:00) more fedi couples are ... welcome :neocat_cool:
arkw@2日目(日)東W28a@arkw@mi.arkw.work (2026-09-06 19:11:57) I'm at カネスエ 四日市フレスポ店 in 四日市市, 三重県 swarmapp
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:11:37) あ、今調べたらAVIFのバージョンがあるのか、そして1.2ではかなりHDRもいけそう
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:09:26) AV1と違って写真向けの豪華な機能に対応していて良い
mame muumimamma@mametsuko@mk.absturztau.be (2026-09-06 19:06:19) das Brot ---Attachments--- image: https://misskey-taube.s3.eu-central-1.wasabisys.com/files/webpublic-9a44b2ac-6c28-447d-a71b-dba57f49033f.webp
YAHB@arce (2026-09-06 19:04:43) Cloudy. Quiet. Early. Peaceful.
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:04:01) あーぜんぜんアニメーションもいけるな
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:03:03) JPEG XLってwebpも殺せるの？
アニメーションとかはwebpが残る？
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:02:45) JPEGを殺すために頑張ってるんだなあ
おだら@s3_odara@mastodon.hakurei.win boosted: @syobon@post.syobon.net (2026-09-06 18:56:29) Brunsliってやつ
https://github.com/google/brunsli
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 19:01:18) ああ、これが元技術なのか、で、それが組み込まれたと、へぇー
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 18:59:13) デフォルトだとJPEGとGIFはロスレスに圧縮するのか
https://man.archlinux.org/man/cjxl.1.en
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 18:58:19) 公式のcjxlも使える、確かデフォルトだとロスレス
https://github.com/libjxl/libjxl
SyoBoN@syobon@post.syobon.net (2026-09-06 18:56:29) Brunsliってやつ
https://github.com/google/brunsli
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 18:55:38) まあ数割くらいしか縮まないと思うけど
おだら@s3_odara@mastodon.hakurei.win boosted: @ponkotuy@social.mikutter.hachune.net (2026-09-06 18:54:38) JPEGを追加で圧縮、ほぼ無理筋では
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 18:55:03) JPEGXLならJPEGを追加でロスレスに圧縮できる!
ぽんこつ 27L@ponkotuy@social.mikutter.hachune.net (2026-09-06 18:54:38) JPEGを追加で圧縮、ほぼ無理筋では
おだら@s3_odara@mastodon.hakurei.win (2026-09-06 18:50:09) 止まれも徐行も譲れの意味を含意しているのでまあ近いといえば近いが
Older Notes