Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Your dead right. But there will always be a tiny thought at the back of my brain that says I'm losing something by applying any form of compression. Nothing to base it on, just a feeling!You could shoot in Lossless Compressed RAW and save 40%-ish
It's been proven, but I know exactly how you feel. There's always that nagging doubt.Your dead right. But there will always be a tiny thought at the back of my brain that says I'm losing something by applying any form of compression. Nothing to base it on, just a feeling!
Your dead right. But there will always be a tiny thought at the back of my brain that says I'm losing something by applying any form of compression. Nothing to base it on, just a feeling!
Panasonic's RAW is lossless compressed, there is no other option. They just call it RAW.If you shoot the original Sony "Compressed RAW", then yes, you are losing some data. We could talk about how it works, and the situations where it can affect your files, but many people find it completely acceptable. I have too much experience with data compression to be happy with it, even though I understand it.
Starting with the A1, Sony introduced "Lossless Compressed RAW" - this is a genuinely lossless compression, and you lose no data using it. Think of it as being like ZIP, where you compress a file, then decompress it, and the content of the decompressed file is identical to the file before compression. You will lose NOTHING using Lossless Compressed RAW. I can explain why it is able to compress the data without loss, but I'll refrain unless you really want to know. Suffice it to say that you will not lose anything by using lossless compressed files, except that some bodies won't shoot at their maximum frame rate using lossless (all the older bodies, and many of the newer ones, only shoot their the maximum frame rate using lossy compressed).
Interesting to note that Sony omitted the "Uncompressed RAW" option on the A6700. I think we will see Sony dropping the uncompressed format in newer bodies. There is no need for uncompressed now that lossless compressed is supported by most of the RAW processing software.
Canon has been using a lossless compressed RAW format since at least 2007 (and probably earlier), and has not offered uncompressed for at least that long.
Panasonic's RAW is lossless compressed, there is no other option. They just call it RAW.
Do you have a cite for that? Not saying you're wrong, but I'd need to read that from an informed source before I believe it. TIFF files can be viewed by any computer like a jpeg, RAW files have to be decoded. Below are couple of articles from Sony. One discusses the differences between RAW and TIFF, the second describes the different types of Sony files and suggests when each is appropriate to use.About the only unique thing I know about Sony lossless is that lossless compressed is really a compressed TIFF; however, Sony did not follow the TIFF standard.
Do you have a cite for that? Not saying you're wrong, but I'd need to read that from an informed source before I believe it. TIFF files can be viewed by any computer like a jpeg, RAW files have to be decoded. Below are couple of articles from Sony. One discusses the differences between RAW and TIFF, the second describes the different types of Sony files and suggests when each is appropriate to use.
Not in that order, no. You have to decompress the data first. Think about it. Almost all the data in a RAW file is the samples from the Bayer mosaic - millions of numbers, each representing the intensity of light received by one cell on the sensor - that's the data which the compression must compress to make any real difference to the size of the file. The Bayer de-mosaic process has to access that data, and it cannot do it in compressed form (OK, in theory it could, but the performance would be appalling). So it decompresses the data first, but it does so in memory (not on disk). Your 60-80MB lossless compressed ARW file becomes ~120MB of uncompressed data in memory, then the de-mosaic process turns that into almost 3 times as many 16 bit values (you get a value for each of red, green, and blue); if you save the processed RAW data in uncompressed form it's around 360MB = 60Mp x 3 colours x 16 bits (2 bytes).A TIFF standard varies based on purpose I think. The TIFF/EP standard is probably the one being used with the vendor deciding the JEITA EXIF standard differences that they might want to use. At least that is my best guess on it. On top of demosaicing the raw file and then decompressing the tiff (if in that order, I don't know), I can see why the photo editor will be working the computer harder.
TIFF/EP - Wikipedia
en.wikipedia.org
Was hoping you'd chime in.Not in that order, no. You have to decompress the data first. Think about it. Almost all the data in a RAW file is the samples from the Bayer mosaic - millions of numbers, each representing the intensity of light received by one cell on the sensor - that's the data which the compression must compress to make any real difference to the size of the file. The Bayer de-mosaic process has to access that data, and it cannot do it in compressed form (OK, in theory it could, but the performance would be appalling). So it decompresses the data first, but it does so in memory (not on disk). Your 60-80MB lossless compressed ARW file becomes ~120MB of uncompressed data in memory, then the de-mosaic process turns that into almost 3 times as many 16 bit values (you get a value for each of red, green, and blue); if you save the processed RAW data in uncompressed form it's around 360MB = 60Mp x 3 colours x 16 bits (2 bytes).
TIFF is a general purpose file format, and it's convenient for people to use parts of the format as something familiar - I suspect that a lot of RAW formats resemble TIFF under the covers. If nothing else, it makes it easier for third party software to support new cameras as they arrive. But some parts of the TIFF standard may require a company to reveal things they do not want to reveal, so maybe the company "neglects" to fill in a "mandatory" field or two. or something like that. Or maybe their coders get a little lazy, or don't read every page of the standard! I've implemented standards in the past, and it can be a pain to handle everything.
I suspect that the Time Fix people could have been supplied with object code to decompress Sony's lossless compressed files (it would be a smart move on Sony's part to get third parties to support their files more quickly). If that's the case, I can imagine Sony only supplying decompression code (after all, the companies are decompressing it to do things like run de-mosaic processing, right? They don't need the compression code!). Supplying just decompression code would keep Sony's options open - they could tweak the compression process in the future, if need be, and still decompress it using the same code. That would explain why Time Fix cannot re-compress the file. And you may get various "explanations" as to why that's the case (I've been on both sides of those conversations in the past)
it sounds like the email pointreyes posted is legitimate?
That's pretty much what's happening when you open an image in a RAW processing software though. Demosaic, for example, is automatically applied along with some basic things in order to have an image that you can see.Sounds like it is legitimate, but not in the way many people, including me, would immediately understand it. My misunderstanding would be that TIFF is necessarily an image, whilst everything I read about RAW files always stresses that they are not images until they have been through at least the rudimentary first steps of processing.
I think they all do. DxO Deep Prime creates a huge DNG file after applying denoise, but you can delete it after you finish processing.That said, the file size grows when using that noise reduction feature, so no escaping needing more storage at some stage of the process.
I found out from DxO, that I can only use large for processing raw files.I think they all do. DxO Deep Prime creates a huge DNG file after applying denoise, but you can delete it after you finish processing.
Was hoping you'd chime in.
So, given your experience, it sounds like the email pointreyes posted is legitimate?
I found out from DxO, that I can only use large for processing raw files.
To use denoising tech with the mRAW and sRAW files, I have to use the post processed results with Topaz.
This was also discussed at: https://www.alphashooters.com/community/threads/what-settings-for-raw.8108/#post-51564
Yes, that is correct. The APSC mRAW is a true RAW file. With the A1, I have been comfortable using mRAW for events and noticed that the images I took in APSC mode could be fed through DxO denoising.I suspect you can use APS-C M-RAW, too - it is a true RAW file, like RAW-L. The others are something else.
I would be rather curious to hear if DxO works on any other company’s M-RAW or S-RAW.
As a new A7RV owner, your comment about LR's de noise not working with medium lossless was news to me. I have worked little with the R5 but I was planning on some testing to see the difference in photos that I took using different levels of compression. You have just saved me a lot of time. I'll do testing AFTER this coming week, as a Surgeon is going to have his way with me next Thursday.On my A7RV I shoot in lossless RAW Large. While travelling I was running out of storage so dropped to lossless Medium. Turned out to be a mistake as a lot of shooting was in low light/high ISO and I wanted to use Lightroom Classic’s noise reduction feature but found that would only work on Large not Medium lossless files. That said, the file size grows when using that noise reduction feature, so no escaping needing more storage at some stage of the process.
As a new A7RV owner, your comment about LR's de noise not working with medium lossless was news to me. I have worked little with the R5 but I was planning on some testing to see the difference in photos that I took using different levels of compression. You have just saved me a lot of time. I'll do testing AFTER this coming week, as a Surgeon is going to have his way with me next Thursday.