Forum Replies Created
-
Posts
-
Hi Ken,
I am thinking about purchasing an M10-R. I am wondering how the Apple raw converter is performing with Leica M10 DNGs? And did you create your own presets?
Thanks,
ErikHi Ken,
I am thinking about purchasing an M10-R. I am wondering how the Apple raw converter is performing with Leica M10 DNGs? And did you create your own presets?
Thanks,
ErikHi Guy,
thanks a lot for sharing your thoughts. I think it is always good to think workflow over and then validate what you are doing or modify the approach. I agree that the lack of renaming functionality in Photos is a gap, but I can see where it is coming from: On iOS devices, one doesn’t want to mess around with it, and in iCould, people shouldn’t need to worry about file names. Then, when you archive raws and edited images to some archive on your Mac, on a NAS or even another cloud service, you would rename during export. I think Apple should then allow users to change the title of images in Photos for iOS, as I normally use the title for naming files while exporting images. Even in Photos for Mac OS adding titles to images is a very cumbersome, manual, one by one process, unless you use Apple scripts which I do and which work really well.
My approach obviously has a gap: All editing done using RAW Power within the iCloud Photos Library is residing only there, except when I use Fuji X-Raw Studio to create the first in-camera iterations of jpgs from raws. But in all honesty, if one switches from one raw processor and image editor to another, I guess in most cases that new setup wouldn’t be able to consume the editing metadata from the previous application(s) anyhow. So if I ever were to change, I would still have the raws and the final JPGs, not only in the iCloud Photos Library, but also in my archive where for each event I have two sub-folders: “Original” for the raws and “Modified” for the final jpgs. So if that change ever happened, I could still selectively redevelop some of the raws into whatever jpg or TIFF I want to create out of them.
But I have no plans changing my workflow for now. I hope Apple Photos and RAW Power will continue to exist for the years to come and will only get better.
Cheers,
ErikHi Guy,
That’s exactly it: Me too, I was hesitating to beef up my iCloud storage plan from 200 GB to 2 TB, but I made that move at some stage and don’t regret it at all. At the end of the day, we moved from 3 individual storage plans amounting to 7€ per month to a shared family plan for 10€ per month.
Now iCloud Photo Library is my master where I store raws and modified jpgs, and I do export raws and final jpgs to a RAID NAS, plus iCloud Photo Library is also being backed up via Time Machine.
Overall, I am super happy with that setup.
Cheers,
ErikAre you shooting compressed RAF? Apple’s raw engine can’t handle those. You need to shoot uncompressed RAF.
I looked into this matter again. So ColorSync remains a good choice for post-editing profile embedding. Preview can be used for soft-proofing post editing. GIMP appears to offer soft-proofing while editing. So A possibility is to do most editing in RAW Power, export as 16 bit TIFF ProPhoto RGB or AdobeRGB and then check the expected print output including out of gamut colors in GIMP. I will try that when I will have my next larger format print made.
Hi there!
Maybe I don’t manage to consider all of your iPad workflow requirements, but given the storage limitations on most iPad models, you may need to consider storing all of your image assets in iCloud Photo Library. RAW Power 3.0 can access it and also store all the adjustment data there. So you have everything in one place. You would want to subscribe to a 200 GB or 2 TB storage plan (I chose the latter – to cover the whole family at the same time), and latest when your iPad runs out of storage space, you would need to set iCloud Photo Library to optimize storage. As soon as you select images in Photos or you access them straight from RAW Power 3.0, the full res images will download from iCloud.
The one thing that would concern me is that all of your image data now exclusively resides in iCloud. I have an iMac alongside the iPad which I use to keep an archive of all raw files plus edited jpgs, besides having it setup to keep all original full size images in parallel to iCloud Photo Library. Plus of course a whole host of backups of everything.
Maybe you could overcome this issue when using an iPad only by exporting jpgs and raws (haven’t tried the latter) from the iCould Photos Library through the RAW Power export function first into the iPads file system and copy them from there over to an external storage device attached to the iPad. Then delete the local copies from the iPads file system to free up space. For my personal liking, this workflow is too cumbersome.
Another aspect to consider: I find it very hard to use the iPad to produce predictable outcome for printing images, even when setting the screen brightness to a lower level. The iMac with a its display calibrated to 100 cd/m² and properly profiled is much better at that task. It would be even better if RAW Power were to support soft proofing based on output profiles for your targeted output device and output substrate. I filed a feature request for this a while ago.
Hope this helps.
Best regards,
ErikThank you, Nik, I think it would be really great, as in these dark corners of an image (think architecture at night, astro with horizon and buildings on it), you don’t even see these corners.
It is possible. When you save an adjustment set as a preset, you can tick a box to automatically apply this preset to images from this camera. You would have your additional adjustments saved in a separate preset which should NOT be automatically be applied to images from this camera. The images from this camera would first automatically receive the auto presets, and then you would incrementally add the other preset(s), i.e. NOT replace.
