Jump to content

altae

Members
  • Content count

    117
  • Joined

  • Last visited

About altae

  • Rank
    Advanced Member

Contact Methods

  • Website URL
    https://the-digi-picture.com

Profile Information

  • Gender
    Male
  • Location
    Switzerland
  • Interests
    Photography of course ;-)

Recent Profile Visitors

912 profile views
  1. Proper support for luminosity masks. Blend ranges are nice but no real replacement as they cannot be altered manually whereas with luminosity masks I can always correct a certain area and brush something in or out.
  2. This has indeed fixed the issue. Thanks
  3. Sorry, I thought that's the name of the pen. Apparently it's dependent on the tablet model. With my tablet switching to the eraser (and back to the previous tool) is the only thing that does not work, everything else is fine. I realized that the switch for high precision tablet input in the settings is gone, maybe it has something to do with this change. Well, it's a beta after all...
  4. Nope, my table is also concerned. In my case switching to the eraser by turning the stylus upside down does not work in the beta (it does work in the stable version). The rest of the functions work though (at least the ones I use).
  5. Apparently it works with some tablets while it does not with others.
  6. What tablet you've got? With my tablet (Wacom Intuos Pro Small, standard pen that came with it) it does not work. But as soon as I switch back to the stable version it works again as expected.
  7. In the latest Beta turning the Wacom pen upside down in order to switch to the eraser does not work anymore. In the stable version it still works as expected.
  8. Beg your pardon but it does indeed affect my workflow. Until now I always thought I could rely on the histogram because it reflects the actual distribution of the tonal values. Turns out under certain conditions I cannot rely on it because it obviously does not always reflect reality. To me this is a severe flaw which every time I merge adjustment layers to a new layer leaves me wondering whether my image has been altered or not. In my opinion this should not happen.
  9. I know that in order to get a reliable preview you need to zoom in to 100 %. But shouldn't the histogram be calculated based on the actual image meaning independently of the preview zoom level (or in other words always based on 100 % zoom level)? I think it's very misleading to see the histogram change when merging layers, it needlessly alarms/ confuses the user.
  10. Here you go, simply delete the top pixel layer called "vignette" and merge the remaining layers to a new layer. Ignore the inactive "gradient map layer" as it's only there to analyze the distribution of the tonal values, it's not part of the image.6D_IMG_7017_DxO_1.afphoto 6D_IMG_7017_DxO_1.afphoto
  11. Hm, after some more tests it seems that it's a preview issue. While zoomed in to 100 % the image does in fact not change anymore. Exports apparently are fine too. But why on earth does the histogram change when not zoomed in at 100 %? I can understand the inaccurate preview below 100 % but the histogram? That's very misleading. I redacted the initial post and the title accordingly.
  12. I realized that merging all visible layers sometimes alters the image preview as well as the histogram. Take a look at the attached screenshots. The first one is with the merged layer disabled, the second one with the merged layer enabled. Do you see how the merged pixel layer reduces the contrast in the image preview (it's also visible in the histogram)?
  13. While it would certainly be nice to have a dedicated feature it can in fact be done easily: Create a new pixel layer, fill it with neutral grey and choose overlay as blend mode. Dodge & burn on this layer using a brush in either white or black color. Then use the blend range of that layer to restrict the dodge & burn effect to areas with a certain luminosity. This procedure is completely non-destructive and you can always come back to it later if you want to tweak it further.
  14. Dirty? Why? You don't lose anything. It's inconvenient, yes I already wrote that. But it works perfectly and the color space stays consistent throughout the whole processing chain. And to be honest it also does not take up too much extra time because starting the plugin from within Affinity, making the desired adjustments and handing the result back to Affinity also takes up some time. But I agree, Serif should definitely fix this issue, in fact they claim their software is compatible to Photoshop plugins when in reality this compatibility is somewhat crippled as we can see in this thread.
  15. I agree that it's very disappointing that these issues still have not been fixed. But there is a workaround: Export the image as 16 bit Tif in the desired color space, use the standalone version of the plugin (the Nik tools have them and most Topaz plugins too), process the image as desired and export again to 16 bit Tif. After this you can continue in Affinity Photo. Certainly not very convenient but it works.
×

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.