Jump to content

kirkt

Members
  • Content count

    141
  • Joined

  • Last visited

About kirkt

  • Rank
    Advanced Member

Recent Profile Visitors

536 profile views
  1. Thee are usually a bunch of different ways to do things, I agree. Apply Image must be partially broken in Lab equation mode on the Mac in V1.7.2. I can use Lab equations (DL = SL, Da = 0.5, Db = 0.5 - if you do all SL, you get a color image that reflects the mix of the a and b channels) to generate the equivalent of the L* channel. Let's say I want to apply a Curves adjustment through an inverted L* mask, a typical task to boost shadows or target shadow tones for color correction, etc. So I have a layer stack that has the working image (background layer) and a curves adjustment layer above it. Recall that adjustment layers have their own inherent mask built in. So, I select the Curves adjustment layer to make it active (the target of the Apply Image command): 1) Open the Apply Image dialog (Filter > Apply Image) 2) Drag the background layer onto the dialog box to make it the source of the Apply Image operation 3) Use Equations - DL = SL, Da = 0.5, Db = 0.5, DA = SA And apply image. The result gets applied to the mask of the Curves adjustment, but the resulting image is distorted and scaled up and is not the L* channel of the background. (see attached screenshot). To make this work properly, I have to create an empty pixel layer and generate a pixel-based representation of the L* channel - i.e., new pixel layer, fill it with white, then do the apply image operation to generate the L* channel on this pixel layer (the second screenshot is what the L* channel should look like). Then I have to rasterize it to a mask, then drag it to the curves layer. That is a lot of steps for a simple operation. The use of the Levels filter with your settings at the top of the stack will also generate the desired L* output, but then you have to stamp the layer stack, rasterize the resulting pixel layer and then apply it as a mask. It is a nifty way of doing things though. I prefer the Duplicate Image method because I can work in Lab mode with Lab tools to choke the mask, etc. and then simply apply the L* channel to the working master image (to an adjustment layer or as a pixel-based layer, etc.) when I am finished in the duplicated image. I can also leave the duplicate image open and tweak the operations and reapply the result to refine or edit the result for use in the original. Kirk
  2. I second this request. The Photoshop equivalent is Image > Duplicate and is useful for myriad tasks, especially when you want to perform an action or a color mode change for a particular purpose and then introduce the result back into the master working document without having to Save As... and create another file in the OS (for example, you would like to create a mask from the L* channel of your current RGB document - dup the current RGB document, change the dup's mode to L*a*b*, and Apply Image > L* channel to the RGB doc's active layer as a mask). The duplicated version is simply a document that exists in memory and is usually something that is temporary or can be saved after the fact if that is its intended purpose (for example, if you create an action that duplicates the master document, flattens it, reduces the size and performs output sharpening and color space change for output). This seems like a no-brainer and I am repeatedly surprised after major updates that AP has not implement this. Kirk
  3. You can export 16bit TIFFs of each channel from Raw Digger, using the option to fill in the missing pixels with zeros (black). Then you can open each of the four channel TIFFs (R, G1, B, G2) and convert them to 32bit (they are linear) and stack them in linear dodge (add) mode - for each of the four layers, you can clip a recolor layer to add the CFA color that corresponds to that layer. This will effectively give you a UniWB image - you can clip an exposure adjustment to the R and B layers and adjust the exposure of R and B to white balance the image. kirk
  4. kirkt

    Affinity can't handle shadows...

    Good insights, re: the Develop persona. I have a feeling that if the Photo app gets a DAM-type auxiliary app, the raw converter will get spruced up too. I do not use or depend upon DAMs for my work, but I can imagine that a DAM will place more emphasis on getting a larger portion of the heavy lifting of raw to RGB image editing done at the raw conversion stage, as many folks prefer in applications like LR and C1. I agree, these suggestions have been floating around for while and a gentle reminder is always good - considering what the Serif team have managed to push out in the last few years, I have no problem cutting them some slack in the priorities department. If any Mac users are looking for a raw converter that offers exceptional control over tone and color, consider the free (upgraded features for a donation) application called Raw Photo Processor (RPP). Do not let its spartan interface fool you into thinking that it has limited functionality - it is, hands down, one of the best raw converters I have used and produces exceptional output (including 32bit if you prefer). The interface and workflow take some time to get used to in the GUI world of sliders and instant previews, but once you get the hang of it, it is so much more efficient and gets you to the converted output quickly and efficiently. See: http://www.raw-photo-processor.com/RPP/Overview.html kirk
  5. kirkt

    Affinity can't handle shadows...

    I have always found AP's handling of black point, contrast and shadow detail in the Developer (I.e., raw conversion) persona to be extremely sensitive and twitchy, with very little room between default rendering and pure crushing of significant shadow tones. kirk
  6. kirkt

    Affinity Photo Customer Beta (1.7.2.146)

    Hey now! Here is a link to a ZIP with a bunch of icons and art, including a "Beta" splash screen. Put them in the Resources folder in the .app package if you want to give it a try. It includes the green "beta" icon for the Photo persona, dimmed and active, light and dark interface, as well as Dock icons, and app icons. https://www.dropbox.com/s/d0xpstb9fmdajcx/APPICONS Test.zip?dl=0 kirk
  7. kirkt

    Affinity Photo Customer Beta (1.7.2.146)

    If you start to rummage around in the Resources folder, you can probably figure out which PNG files can be swapped to help you identify the Beta App's photo persona icon, again to help you from getting confused visually once you are in the app itself... kirk Also - MODS - if what I am doing is violating terms of the beta usage, or is just morally reprehensible in general, please let me know and I will delete these posts. Just trying to be helpful based on the previous posts. kirk
  8. kirkt

    Affinity Photo Customer Beta (1.7.2.146)

    Here is a Dropbox link to a .icns file I created so you can switch out the existing beta icon with one that will stand out: https://www.dropbox.com/s/w7m5vdm48anqtsl/AppIcon.icns?dl=0 I just inverted the existing icon art and added a "beta" character in the existing magenta-ish hue. The .icns file just needs to be dropped on the icon for the beta app when you open the "Get Info" window: 1) Select the beta application in the finder (click on it); 2) Use the keyboard shortcut CMD-I (the letter "eye") to bring up the Get Info window for the application; 3) Drag the <AppIcon.icns> file onto the existing icon for the beta application in the upper left corner of the Get Info window. 4) Easy peasy. Attached images show a preview of the icon and its appearance in the dock (i compressed the posted images for quick upload - the icon art is not JPEG-artifacted as it appears in the previews). The icon artwork was made in the 1.7.2 beta and contains all of the resolution variations that the original .icns file contains. To convert the .icns file to a .iconset (folder of images), use the OS X command line utility called "iconutil" - type: man iconutil for help on how to use it. If you convert the existing .icns file to an iconset, you can see all of the PNG files used to make the icns file and you can create your own - then you can convert the iconset back to a .icns file and drop it on the Get Info window and you will have your own, custom icon. If you want to make a copy of the existing icns file that ships with the beta, so you can alter it for your custom icon, it lives here: /Applications/Affinity\ Photo\ Beta.app/Contents/Resources/AppIcon.icns Here is a brief rundown of Apple's human interface guidelines for creating icon artwork, resolution, etc.: https://developer.apple.com/design/human-interface-guidelines/macos/icons-and-images/app-icon/ Have fun! Kirk
  9. kirkt

    Any ideas

    You will have to use Adobe DNG converter on a PC or Mac desktop - there is no iPad version. However, you can batch convert RAFs from your older S5000 and then make them available to your iPad through a number of different transfer/storage paths, including iCloud, Dropbox, a WiFi accessible drive, Airdrop, etc. Once you convert your files to the appropriate form of DNG and upload them to your preferred storage/iPad accessible location, you are good to go. Easy peasy. Astropad is simply an application that permits you to use your iPad as a second display, a feature that the upcoming MacOS will have built into it. It does not permit you to transfer files to the iPad, etc. kirk
  10. kirkt

    Any ideas

    I was able to convert the raw file in AdobeDNG Converter using some custom settings: (Change Preferences > Custom (Compatibility) > Backward Version DNG 1.1, Linear (demosaiced). Play around with the custom compatibility settings to see what works best for your workflow. In this example the raw data were demosaiced, so the file has been rotated appropriately. Attached is a screenshot of your raw file, converted to DNG, opened in the Develop persona. Here is a Dropbox link to the converted DNG: https://www.dropbox.com/s/0rfzunzpx8jxk6i/DSCF2600.dng?dl=0 kirk
  11. kirkt

    Any ideas

    Ok - the camera uses the Fujifilm SuperCCD, which has its quirks. I was able to use a Mac desktop application called LumaRiver HDR (meant to blend raw exposures into a single HDR DNG, TIFF or EXR). This application must use a more robust technical implementation of the DNG API, because I was able to open your raw file in it and then export a DNG from it that I was able to open in AP on my iPad. Here is a link to the DNG: https://www.dropbox.com/s/rfdzu8z3fi9ty1r/testDNG.dng?dl=0 and attached is a screenshot of the DNG opened in the Develop persona in AP on the iPad (Import from Cloud, loading the file from my Dropbox). The image is rotated 45 degrees because of the orientation of the photo sites on the sensor of the SuperCCD. kirk
  12. kirkt

    Any ideas

    The Fujifilm Finepix S5000 is a pretty old camera. There is a raw converter for MacOS and iOS called Photo Raw - here is the camera support webpage: https://mcguffogco.freshdesk.com/support/solutions/articles/8000063657-supported-cameras the list of supported cameras includes the S5000; however, I cannot open your file with Photo Raw. Perhaps the file itself has an issue that is causing applications that would otherwise support it to fail to recognize the file format or open the image. Do you have other raw files shot with this camera available to test, or, even better, do you still have the camera and can you update it to the latest firmware and shoot some test images to try? kirk
  13. kirkt

    Any ideas

    @Rob Chisholm Bummer. Obviously it would be nice to have AP work properly on the iPad, but in the interim you might want to try using Raw Power as a raw converter for iPad. It is made by the former lead of the Apple Aperture application and has a similar control UI. kirk
  14. kirkt

    Any ideas

    I had the same issue with my new iPad and my x-h1. Restart your iPad (shut it down and turn it back on). Then try again. Worked for me. I found this solution in another similar thread in the forum. The mod was puzzled as to why it worked, but it worked. Who knows what the iOS is doing to adapt to the user in the background. Kirk
×

Important Information

These are the Terms of Use you will be asked to agree to if you join the forum. | 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.