rscheffler
Offline
• • • • • •
Upload & Sell: Off
|
The current Canon cameras no longer shoot sRAW or mRAW. It's now called cRAW (or maybe CRAW). It's a full resolution raw file, but is lossy compressed to reduce file size.
leethecam wrote:
So firstly, does the R6 and R6 Mk2 use exactly the same Raw file type (CR3) with the same sRaw file type. (ie can the current Raw processors work happily with the new R62 ?)
exdeejjjaaaa wrote:
they might check camera model tag inside a raw file and refuse to work w/ it , unless you exiftool the tag for example to an older model
Exactly. Even though both shoot CR3 raw files, a camera released after your standalone version has received its last update won't be readable without workarounds. I know changing the exif tag has worked with some apps... but for example with the R6 and R6II, the new camera has a different resolution sensor and pretty certainly requires unique profiling for optimal results.
Does C1 work with DNG files? A brief browsing of their support suggests it does. One option for you might be to convert unsupported camera raw files to DNGs with Adobe's DNG converter. It sounds like if a camera is not natively supported by C1, it will apply a generic color profile to the DNG file. But you'll still be able to process the DNGs with C1.
In theory, this should allow you to continue to use C1 indefinitely. You will lose camera-specific profiles, but it will still work.
Where this is likely to eventually fail is computer OS support for standalone C1. Either your hardware will be too old for the latest OSes, holding back other apps you may need to update, but allowing you to continue using legacy apps, or your old hardware dies and forces a hardware update whose OS is no longer backwards compatible with your legacy apps.
This is kind of what I ran into. I hadn't bought a new camera since 2016 and was successfully using a 2010-era Mac with LR6, the last standalone (non-rental) version. If I needed to, I could work on files from newer cameras released after the last LR6 camera support update, by using DNG converter. But Adobe is a bit sneaky with DNG converter - support for the latest cameras is in the latest versions, and those seem to have fairly limited backwards compatibility with older OSes. And because my Mac was so old, I couldn't (and didn't want to anyway) update it far enough to retain DNG converter compatibility with the latest Canon mirrorless cameras.
Since I was planning to upgrade cameras anyway, it resulted in new computer hardware. And because I didn't want to do the DNG conversion route and not knowing how much longer LR6 would work on future OSes, I bit the bullet and am paying Adobe rent. I figured now that I'm in the middle of a big upheaval with new cameras and a new computer, I might as well update software too.
I probably could've found some decent used Mac hardware at OWC that would be new enough for a recent enough OS to use DNG converter with the latest cameras, be fast enough for some years still with 24-30MP files and allow me to continue using LR6 for some time still. But it would always be a balancing act keeping software supported and trying to maintain some degree of camera compatibility. Frankly, I wasn't keen on relying on DNG conversion just to keep using LR6.
IMO I'm going to pay one way or another. Trying to keep a specific configuration running as long as possible is just deferring the inevitable. And the longer it's deferred, it seems the larger the lump sum outlay is to overhaul the system. It could also cause workflow inefficiencies that cost in other ways, such as requiring more time to get something done. But only you know if that matters.
|
)
