Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
lonjil
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
8 ms
·
31.
▲
by
lonjil
2y ago
I don't think you can use Chrome to view any raw image files...
32.
▲
by
lonjil
2y ago
> Animated AVIF is widely supported, and can represent GIFs losslessly. Doesn't lossless AVIF have terrible compression ratios?
33.
▲
by
lonjil
2y ago
They aren't switching from HEIC to JXL. Apple uses HEIC for regular photos, but they use DNG with Lossless JPEG for "ProRAW". They are switching the latter to use JXL inside DNG instead of L-JPEG.
34.
▲
by
lonjil
2y ago
> So Google killed XL a while ago already and I feel like either Microsoft or Mozilla at least considered following suit. There's been JXL stuff visible in Windows 11 preview builds for months now. They might roll out support next y
35.
▲
by
lonjil
2y ago
Apple's ProRAW format is Linear DNG, that is to say, already debayered, not what most people would call "raw". Previously they've used Lossless JPEG for compression inside these DNG files, but now they use JXL. The DNG s
36.
▲
by
lonjil
2y ago
There's literally no way Apple developed a hardware accelerator for JXL encoding. So they're definitely using some kind of a CPU or generic DSP.
37.
▲
by
lonjil
2y ago
> In lossy mode I think there is no difference between AVIF, HEIC or JXL. AVIF is even a little bit ahead. AVIF is definitely not ahead for the high quality levels you'd use in photography. AVIF is ahead at lower quality levels. >
38.
▲
by
lonjil
2y ago
They aren't doing JXL encoding in hardware though. Zero chance that the new iPhone chip has hardware acceleration for JXL. Definitely just plain old CPU encoding. And we're not talking about video anyway, this is about ProRAW, a s
39.
▲
by
lonjil
2y ago
Adobe added JXL as a compression option for the DNG format last year. Previous options were JPEG, Lossless JPEG, Deflate, and nothing. Apple used Lossless JPEG. Apple engineers have decided to take advantage of the option Adobe added last y
40.
▲
by
lonjil
2y ago
AVIF is worse than JXL both for high fidelity compression and for lossless compression, which is what Apple is using JXL for here.
41.
▲
by
lonjil
2y ago
One aspect may change (file size) while another remains the same (the actual data you get when you read the file).
42.
▲
by
lonjil
2y ago
> Why make the distinction if there is no difference? There is a difference, which is that the compressed lossless version is smaller and requires some amount of processing time to actually be compressed or uncompressed. But there is zer
43.
▲
by
lonjil
2y ago
ZFS can help you with backups and data integrity beyond what RAID provides, though. For example, I back up to another machine using zfs's snapshot sending feature. Fast and convenient. I scrub my machine and the backup machine every we
44.
▲
by
lonjil
2y ago
> If Apple is giving you JPEG-XL they are compressing the file, so it is not RAW.JPEG-XL is lossless compression. Are you unaware that most DNG files are compressed using Lossless JPEG? Including ones that are storing raw sensor data rat
45.
▲
by
lonjil
2y ago
That number includes all the different extra tools in the repo, and all tests. And as mentioned, the encoder.
46.
▲
by
lonjil
2y ago
You've got it backwards. Before M1, most Macs that regular consumers owned were incredibly bad GPU-wise. M1 was an enormous upgrade and finally made Mac usable for gaming for the average Mac owner. But years of most Macs being useless
47.
▲
by
lonjil
2y ago
> Firstly, several games engines and rendering libraries support it. So? If no one is using that support to ship PC games using Vulkan, who cares? Those same engines all support Metal, so clearly this is irrelevant to the question of Ma
48.
▲
by
lonjil
2y ago
Did you paste the wrong link? That is about M1 Max, which is a very different, much bigger, chip.
49.
▲
by
lonjil
2y ago
> Though, I don't see true sideloading (like on Android) specified. If apps still need Apple's approval, we will get "freedom" who to pay, not what to run. I still don't see device liberation within the scope of
50.
▲
by
lonjil
2y ago
> The other CPU catch back after several months, the Apple Silicon is a good marketing prowess, the reality is that Apple CPUs wins because they are the first on to be produced on a new lithography node, because Apple can book a larger q
51.
▲
by
lonjil
2y ago
That 50m+ figure is surely iPads in general, rather than iPads Pro? iPad Pro is specifically marketed to media production professionals as a viable replacement for a laptop, but media production professionals (like the aforementioned tech y
52.
▲
by
lonjil
3y ago
I recently noticed that all the thumbnails on my computer are PNG, which I thought was funny.
53.
▲
by
lonjil
3y ago
> Their claims about Jpegli seem to make WebP obsolete regarding lossy encoding? Similar compression estimates as WebP versus JPEG are brought up. I believe Jpegli beats WebP for medium to high quality compression. I would guess that mor
54.
▲
by
lonjil
3y ago
All the developers involved are part of the JXL team at Google Zürich, as far as I can tell.
55.
▲
by
lonjil
3y ago
Jpegli, of course, does this when you ask for 8 bit output.
56.
▲
by
lonjil
3y ago
> Not sure if you are part of the research team but a follow up question nevertheless. I am not. > what would it take to develop another widely supported image format? Would the research stage already need to be carried out as a multi
57.
▲
by
lonjil
3y ago
Jpegli encoded images decode just fine with any JPEG decoder, and will still be of great quality. All the tests were done with libjpeg-turbo as the decoder. Using Jpegli for decoding gives you a bit better quality and potentially higher bit
58.
▲
by
lonjil
3y ago
8-bit JPEG actually uses 12-bit DCT coefficients, and traditional JPEG coders have lots of errors due to rounding to 8 bits quite often, while Jpegli always uses floating point internally.
59.
▲
by
lonjil
3y ago
It's regular old JPEG1. I don't know the details, but it turns out that "8 bit" JPEG actually has enough precision in the format to squeeze out another 2.5 bits, as long as both the encoder and the decoder use high preci
60.
▲
by
lonjil
3y ago
Not sure what the rate is, but Asahi Linux uncovered FS corruption on MacBooks. Before you can install Asahi, you have to do a fsck, and a bunch of people reported failures with that step.
More ›