How exactly does one fit 128 frames of lossless data from a 12 megapixel sensor into an 18 megabyte file?
Or is ProRAW not as RAW or as lossless as the name would imply?
How exactly does one fit 128 frames of lossless data from a 12 megapixel sensor into an 18 megabyte file?
Or is ProRAW not as RAW or as lossless as the name would imply?
"RAW files contain uncompressed and unprocessed image data, allowing photographers to capture practically every detail they see in their viewfinder. The RAW file format stores the largest amount of detail out of any raster file type, which photographers can then edit, compress, and convert into other formats. Learn more about the benefits, drawbacks, and best ways to work with a RAW image."
If Apple is giving you JPEG-XL they are compressing the file, so it is not RAW.JPEG-XL is lossless compression.
"Lossless compression uses an algorithm to shrink the image without losing any IMPORTANT data." and the algorithm decides what is important.
Why does it matter? Why does that make Apple deceptive? Lossless compression is as good as no compression, the only difference is the decompression time.
You could store the uncompressed RAW file on a filesystem with built in (lossless) compression, or you could store the losslessly compressed RAW file on a filesystem with no compression. Once you have opened the image in your editor or photo viewer, the bits in that application's memory that you are editing or viewing are identical.
Moreover RAW does not mean 'uncompressed'. It doesn't even mean losslessly compressed. Often RAWs use lossy compression. Both Canon and Nikon RAWs can.
https://photographylife.com/compressed-vs-uncompressed-vs-lo...
There is no such definition. Most cameras’ raw files nowadays are losslessly compressed. The compression being lossless means that the bits that were taken out can be reconstructed identically.
It seems you might be confused as to what lossless compression means?
What you quoted is a confusing phrase: "visually lossless" which is in fact a lossy compression. It's like People's Republic which is neither a republic nor is it the People's, it's just a dictatorship.
Finally, JPEG-XL supports both lossy and lossless compression.
You can make a perfect copy of a file, however.
Is it some kind of industrial camera you are talking about maybe?
(Also, try reading the thread you linked and reconcile it somehow with your previous claim that losless compression of raw files is unacceptable)
Are you unaware that most DNG files are compressed using Lossless JPEG? Including ones that are storing raw sensor data rather than debayered data like ProRaw?
And I am talking about apple in this thread.
The ProRAW format that the default app offers has a different use case: it combines the automatic advanced processing of multiple exposures into a file format that offers more flexibility for post processing than a standard photo does. With the new lossy compression option it gets more attractive for some users that are willing to trade in some quality for space. I don’t see the problem in offering that option next to the lossless compression.
Lossless compression is something I’m not going to argue about, as there is literally nothing lost by doing that and many professional cameras do the same thing, though with different algorithms. Well, unless your argument is that it’s not yet compatible with many photo editors, because that’s a fair point.
Many professional cameras offer lossy and lossless compressed RAW, and have for over a decade now and most are processed to some degree before it’s even written.
RAW hasn’t meant literally raw in a very long time.
You will get a little compression storing multiple frames, but not much, because the photon shot noise is independent for each frame - and in lossless images, the noise (which does not compress according to information theory) often has more entropy than the ideal image (which compresses well).
Or you could store one post-processed frame, after you have combined 128 frames and done the computational photography stuff. But at that point, it isn't exactly raw data anymore.
That is not why noise is created in digital photographs. And Noise or Grain in a photograph is not always a negative.
"Noise in photography is the arbitrary alteration of brightness and color in an image. The onset of this random variation generates what is called “noise”or “grain”, which is basically formed by irregular pixels misrepresenting the luminance and tonality of the photograph. These pixels are visible to the eye due to their large size."
A signal RAW image does not have to have noise. Noise can be created by incorrect exposure and low light.
>Or you could store one post-processed frame, after you have combined 128 frames and done the computational photography stuff. But at that point, it isn't exactly raw data anymore.
Yes, and Apple should not be calling any images it captures from an iPhone "RAW".
You always have noise. It's more noticeable in low light, but it never goes away. It's due to physics - there's real world noise in photons hitting the sensors and read noise in the A/D converters behind them. That's long before the image is captured into any format - RAW doesn't help you here.
There's quite a bit of analog and digital post processing and I doubt you can bypass all of it
I suspect not, because the data output rate from a high end sensor can easily be 32 Gbps, and I don't think any phones have fast enough flash storage to write data at 32Gbps.
You have to process the data in mostly-realtime or lose the data. Storing it isn't an option.
Full sized cameras do use a buffer to deal with burst activity, take series if shots - process - save to slower storage. Also, modern cameras start switching to CFexpress/SDExpress (which are NVMe)
> Version 8.0 was announced on 19 May 2020, with support for two PCIe lanes with an additional row of contacts and PCIe 4.0 transfer rates, for a maximum bandwidth of 3,938 MB/s
That's true in theory/isolation, but in practice we know the noise has much lower maximum amplitude than the original image. I.e. if you take a difference between two frames, almost all of it will require less bits per pixel than the signal. (And that allows compression in practice)
[1] https://medium.com/halide/understanding-proraw-4eed556d4c54