Jump to content
You must now use your email address to sign in [click for more info] ×

coranda

Members
  • Posts

    157
  • Joined

  • Last visited

Posts posted by coranda

  1. Yes, that's on the roadmap but I'm also not sure what that means.  Most raw adjustments (in raw convertors) are actually made after raw conversion, which is why it's possible to load jpegs and tiffs etc. into ACR.  So, I'm not sure whether Serif are planning to follow the PS model and make the raw processor just another adjustment layer or whether they will leave raw processing as the first stage but allow you to go back and change the raw processor parameters and have that ripple through to all of the post raw processes that have been made in the photo persona.

     

    Both approaches would probably be useful.

  2. Raw conversion is an essential first step in processing any digital image (whether in camera or in post processing) because without raw conversion there really isn't an image in the sense that most users expect.  All a raw convertor really needs to provide is:

     - demosaicing

     - gamma correction

     - exposure adjustment

     

    Modern raw convertors offer all sorts of options that, arguably, are not a good idea because best practice is to use exposure control to recover highlight details and do nothing else in the raw conversion.  Subsequent processing requires features not available in raw conversion - in particular, double processing.

     

    However, that approach means turning every image into a tiff/psd type file which requires a substantial amount of storage space.

     

    So, in an ideal world, raw convertors would have nothing more than an exposure slider for highlight recovery.  In practice, when you have hundreds/thousands of images to process, it's often more convenient to completely process most of them in a raw convertor like ACR and reserve PS/AP for those special images you want to extract the most from.

     

    The problem with AP is that its raw convertor must convert all processed images into separate, large files.  ACR makes it possible to store all of the processing in small sidecar files.

     

    So what I'm basically saying is that it can be advantageous to have a very capable raw convertor that avoids the need to use PS if it gives you an advantage in terms of compact storage of the raw processing.  But, if the ultimate intention is to load the image into PS/AP for further processing, the raw convertor should have nothing more than a single exposure slider and all other processing should be in PS/AP - which may include offering the traditional raw processing options as an adjustment layer the way PS does.

  3. Lock,

     

    The jpeg you get from your camera will be heavily processed and designed to look, at least superficially, good.  Most raw convertors I've used seem to do some default processing to also make most images look good, AP for example has, by default, the assistant turned on and so does some tonal correction.  My pet gripe is that Lightroom performs highlight recovery by default which can't be turned off.  Personally, I find this annoying as I'd rather have a minimalist conversion and hence have full control over post processing.

     

    I don't use the raw convertor in AP for two reasons:

    • It is still a relatively new product with a number of shortcomings.  Affinity, to their credit, acknowledge that they have work to do and intend to improve it.
    • But most importantly, AP's raw convertor cannot save your conversion settings in a space efficient manner but needs to save the whole, processed file as afphoto, tiff or some other format.  These files are huge compared to the xmp sidecar files of ACR or the database entries of Lightroom and Aperture.  If I'm creating a special image for printing then that overhead would be fine but if I take 500 shots of my grandsons playing cricket or granddaughters at calisthenics then I need a way to process raw files that isn't going to consume gigabytes of extra storage.
  4. There are people for whom ACR is their only raw convertor and who use no DAM software.  They simply copy the raw files from their memory cards to their hard drive.  For that reason I think it's important for AP to have its ACR equivalent.  This will become particularly relevant if AP eventually takes on some of the current features of ACR/PS.  In particular I'm thinking about:

    • Storing just the develop settings (side car files for example) so that it is possible to develop images without the need to convert them all to .afphoto files which are necessarily very large files by comparison.  Many people don't take most of their images into PS and so they don't need to store psd files as well as raw.  There is currently no equivalent workflow for AP. 
    • The ability to insert the develop settings as a layer so that they can be modified after the image has been edited in the photo persona.
  5. This is just a guess but I suspect Serif is just being progressive.  The idea of 3 a character file extensions harks back to the memory/storage limitations of very early microcomputers where the standard was 8.3, that is, file names of no more than 8 characters followed by a 3 character extension.  Modern operating system long ago ditched the 8 character name limitation but, for some reason, the 3 character extension has lived an artificially long life.

     

    Also, 3 characters is very limiting in terms of creating a unique file type identifier that is also mnemonically meaningful.  The extensions .ade and .aph, for example, have already been used by other software.

  6. So, as I had assumed, it's not an intellectual property issue but an unknown file structure that would have to be reverse engineered?

     

    I can see why users would see AI export as a very valuable asset for AD to have.  However, having myself reverse engineered file formats (that were far, far less complex than I imagine AI would be) I suspect that putting that effort into AD would mean substantially holding back the development of other functionality in both AD and AP (as they seem to be largely integrated code bases).

     

    It's a developers call but I can certainly see why they have chosen not to support AI export.  Remember that every time the AI format is changed or augmented by Adobe Serif would have to make another reverse engineering effort that, if it failed, would render all previous efforts essentially worthless.

  7. I'm all in favour of giving people the options they want but my point is that bright, colourful, high-contrast displays are the enemy of good colour management. I'm not a graphic designer but I can see why a paper white background might be useful.  However, that's a canvas rather than UI issue.  If you want to see your graphics on a white background then expand the canvas and drop an appropriate fill layer underneath.

     

    The UI, on the other hand, should be as unobtrusive as possible - by default at least.  If you are finding that the AP display has too little contrast to be clear then, unless you have a vision problem (which is a whole other issue), it's almost certainly a problem with your working environment.  In that case the best practice is to calibrate your monitor for the level and colour temperature of the ambient light.  If you work day and night it may be necessary to have two separate monitor profiles.

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.