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

c-s

Members
  • Posts

    20
  • Joined

  • Last visited

Everything posted by c-s

  1. I think that what Roaring Fish is asking for is the same thing that I'd like to see: Being able to call an external program to edit a pixel layer that -- after editing -- is reloaded by AP. One use case would be the NIK Collection. You could work in Affinity Photo to do some editing. You can then put the result into a new pixel layer which you can edit with any of the NIK tools (e. g. export it as TIFF-16, call one of the NIK tools, edit it there, save the same file and import the changed file as the same pixel layer in AP). That would be really helpful.
  2. When working with lens correction in the Develop Persona, a "Crop to opaque" option would be really useful (the same as in the panorama function). I'd highly appreciate if you could implement this feature. Thanks in advance. Keep up the excellent work! :)
  3. Please let me stress that I love Affinity Photo and appreciate the hard work you are putting into it. I have one suggestion to make AP even better. ;) When developing RAW images in the Develop Persona, a lot of presets heavily depend on the camera you shot the images with and on other circumstances like ISO value, aperture, zoom level etc.. One example would be that heavy noise reduction doesn't make a lot of sense for ISO 80 but it really does for ISO 6400. My feature request is this: please introduce a function to make presets sync to EXIF data. What I mean by this is this: When creating a preset on any of the tabs in the Develop Persona, add an option called "Sync to EXIF" in the preset creation dialogue. This should allow you to select one or more EXIF keys to sync to. This will basically create a "sync rule". You can have more than one "sync rule". All sync rules should be logically connected with "and" (e. g. "camera model is x AND ISO is greater than y AND shutter speed is lower than z"). Whenever a ruleset matches, the according preset is selected. Let me give you an example: I created a preset that looks really nice with my Sony DSC-RX100M3. When I created that preset, I used the wonderful new "Sync to EXIF" option and created a sync rule to always apply the preset when the EXIF key "tiff:model" matches "Sony DSC-RX100M3". From now on, whenever I process a RAW image by my RX100M3, the preset is automatically applied when loading the Develop Persona. Any other preset can be selected manually afterwards if the user wishes. Another example: On the "Details" tab of the Develop Persona I created a preset that has two sync rules:"tiff:model" matches "Sony DSC-RX100M3" AND "exif:ISOSpeedRating" is greater than or equal to "3200". In this preset, quite a heavy noise reduction is applied to the image. From now on, whenever I process a RAW image by my RX100M3 and the ISO is >= 3200, this preset is automatically applied when the Develop Persona is opened. If creating rulesets is a little too much, please at least offer an option called "Match camera model" which applies presets if the camera is of a certain type (using "tiff:model"). Does this make sense?
  4. Hi all, I'm currently trying to work on my RAW image development workflow and I'm struggling with two problems. The first problem is that there's no automatic lens correction in the Develop Persona. While I appreciate that by default the image isn't heavily treated by the automatic assistant, I still think that doing lens corrections automatically would greatly improve the workflow. I'm working around this by using presets for certain lenses and zoom factors. However, saving a preset isn't a good way to solve this problem because you would have to create several presets for a zoom lens and still could only cover discrete zoom steps. Automatic lens correction would solve this problem. If any of the developers are reading this: please add the possibility to use lense correction. Cheers! :) The more serious problem which causes quite long interruptions of the workflow is to properly crop the raw image that has been lens-corrected. Especially when working with wide angle lenses you get quite a severely concave image with transparent areas on top & bottom and left & right. In the panorama tutorial for AP 1.4 there's an option called "Crop to opaque" (timestamp 2m30' in the video) in the crop tool. However, I don't seem to find this option in the crop tool in the Develop Persona. I might be missing it but if not, I really hope that this features gets introduced to the Develop Persona because it would be really really useful, especially if it would work together with the option to keep the original aspect ratio of the image. The magnetic alignment tool doesn't help because it doesn't snap to the visible edges of the image. Any hints how to facilitate the cropping are highly appreciated. :)
  5. Hi Ronny, I just realized that it matters whether you export an 8 bit or a 16 bit TIF to AP from aperture. If I open "Preferences ... > Export" in Aperture and set the export file format to "TIFF 16-Bit" and use Affinity Photo as external editor, I can actually simply save an edited file in AP after agreeing to flatten it in the dialogue that appears. However, when I set the export file format to "TIFF 8-Bit", I can't save the file from with AP. I hope that this helps.
  6. Hi Jake, very nice tutorial, very instructive and easy to understand. Thanks for all the work you put into it!
  7. Maybe I'll revisit my original request then. :) I think that it would improve the workflow, especially since some labels are not close enough to their text fields (in the HSL adjustments dialogue for example) to intuitively use this feature. I'd highly appreciate this enhancement. Cheers! :)
  8. Hm, you're right. Now that you mention it, I feel kind of stupid not to have thought about this. :rolleyes: Still, adding this function for the case that you simply close the dialogue window with the window controls on top would be quite helpful.
  9. When working with any type of adjustment that has the option to enter values into a textfield (e.g. HSL adjustment where you can manually enter values for color shift, saturation etc.) I've noticed that when you click the text field, none of the text in the box is preselected. This means that when you want to change something from "0%" to "50%", you either have to double click the value again or manually delete everything that is in the text box to enter a new value. I would find it far more practical if clicking a text box would immediately preselect all the text in the box so that I can simply type a new value and press enter right after clicking the box. This would improve the usability and smoothness of the workflow significantly. Cheers!
  10. When working with AP it sometimes happens to me that I select a new Live Adjustment Layer or Adjustment Layer that I don't really want (either because I change my mind or because I selected the wrong adjustment). Right now a new layer is created and after closing the adjustment window I have to delete the new layer (that has no adjustments) by hand. This is not practical in terms of usability. I would suggest this workflow: 1) Creates a new adjustment layer. 2) The adjustment window appears 3) The user either makes changes or doesn't do anything. These cases should be considered like this when the adjustment window is closed: - Changes were made: keep the new layer with its changes. - No changes were made: remove the new layer because it doesn't do anything to the photo anyhow. Does this make any sense? I think it could be useful to add this functionality.
  11. Thanks for the explanation. I have one more question regarding the 16bit layers: if I add pixel layers with a copy of the original image that I'm working on (either parts of the picture or the whole picture), I'd expect AP to use the copy of the image already present in the .afphoto file for all of the layers without making additional copies -- is that correct? I have a suggestion regarding the option to not include a snapshot of the original file: wouldn't it be helpful to simply include the original RAW file instead of e.g. a TIFF snapshot of the RAW file within the .afphoto file? The fact that the RAW file (due to differences in color depth etc.) is smaller than e.g. a TIFF copy should drastically reduce the size of the .afphoto file without losing functionality -- would that work? What email address would you like me to send the link to the file to? Or would you like it as a private message in the support forum.
  12. Hi TonyB! Thanks for looking into this issue. I really appreciate it. After working with AP a little more I found that I sometimes get file sizes between 160-180 MB. Again, thanks for looking into it, please let me know if you need sample files or something, I'd be happy to help you out.
  13. Is there any news on the file size issue? I've started using Affinity Photo today. I love it, however, the fact that the .afphoto files have about 4x-6x (!) the size of the original RAW file strikes me as odd. I have .CR2 RAW files produced by a Canon 50D. I didn't include the editing history in the .afphoto files. Some 20 MB RAW .CR2 files turn into 120 MB .afphoto files for no apparent reason (it only contains material from the original .CR2 file and very few pixel and adjustment layers). If there's anything I can do to help identify a potential bug, please let me known, I'm happy to help.
×
×
  • 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.