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

dolunaykiz

Members
  • Posts

    50
  • Joined

  • Last visited

Posts posted by dolunaykiz

  1. I created a macro to replicate what CTRL+SHIFT+J would do in Photoshop. That is, it is supposed to duplicate the first layer, fill that original one with white, then duplicate copy again. What I should end up with is a white bottom layer and then two identical layers with the actual picture content on top of it. Because all filters in Affinity Photo are destructive, this saves me the time to duplicate the original layer manually. And it worked until yesterday. Now, when I run the macro, it keeps the original layer and fills the other two with white. This only happens on some images, and there is no rhyme or reason why.

  2. Nik Collection just prompted me to install an upgrade to version 2.3.0.0. I am on Affinity Photo 1.7.3 and I want to avoid another disaster like what we experienced about a year ago with Nik just bombing on Affinity Photo. That was only changed when the finger pointing and shoulder shrugging caused a user community sh*t storm. However, I don't have time for the same thing this time around. Can anybody tell me if this is compatible BEFORE I install the upgrade, please? If it is not compatible, when can we expect it to be?

    Thanks.

    PS. I am on Mac OS Catalina.

  3. I am using Affinity Photo, latest version, on a Mac. As unsatisfactory as things have been, the latest fix seemed to make Nik usable again on Affinity. Until just now, when all of a sudden - and mind you, nothing had changed in my setup from one moment to the next, other than me opening another file - Color Efex and Silver Efex came up with basically empty previews. As in, you see just a B&W raster screen, that is it.

    I mean, can we make this a stable thing here, people? When it crapped up last time, we got some BS about how Photo wasn't meant to support PS plugins (which is why there's a plugins folder etc.?!?!), and I understand we can't just wave a magic wand over some things. But I mean, COME ON, PEOPLE!!!

  4. 17 hours ago, HVDB Photography said:

    Sounds a bit confusing ...
    Are you sure you're using the  "Paint Brush Tool" and NOT the "Colour Replacement Brush"  ?

    I know how to use layer masks. I know what to do w/ them. It seems that Affinity Photo doesn't. If I paint w/ black on a layer mask I expect the photo to show a result in the viewer, but it doesn't. Or it only does on parts of it and on the others it's as I'd never painted on them.

  5. I'm currently on the Beta version of Photo owing to the Nik Filter issues this resolves. However, the issue I am seeing should have nothing to do with that, it occurs on both versions. I recorded a macro when I first got on Affinity Photo which selects the background layer, duplicates it, fills the original layer with white, and as a last step renames the copied layer "Layer 1". All of a sudden every once in a while, the only thing I get is a blank layer filled with black on top of the background layer called "Layer 1". It's hit and miss. Sometimes it works, sometimes it doesn't.

  6. 9 hours ago, walt.farrell said:

    Every adjustment layer incorporates a mask. All you need to do is add the adjustment. Then, with the adjustment layer selected in the Layers panel, paint with Black to suppress the adjustment or with white to reveal the adjustment.

    Probably adding the mask manually is part of what's causing your problem.

    I should have phrased it better. The issue occurred when I put a mask on an actual layer and painted on it. Nothing happened.

  7. This is a bug regarding adjustment layers. So I have a picture open and I make a brightness adjustment. Apart from the fact that the layer mask isn't automatically added to the adjustment layer, like in PS - but I can live w/ that - when I do make adjustments, they are not reflected in the file. Like I paint on the layer mask I just manually added in black or white, and it's like I never did anything.

    This isn't just an issue w/ the new beta, it's been an issue. Is this a memory problem? What is going on here?

  8. 18 hours ago, Murfee said:

    Thank you so much for this, confirmed all Nik Plugins open & work. Color Efex Pro even opens with the correct colours now, it was always washed out before. You are going to have a lot of very happy customers when this is released fully.

    Enjoy your weekend, put your feet up ... you more than deserve it.

    Second that. Viveza still shows the washed-out colors, but I can live w/ that. Thanks!!

  9. 19 minutes ago, Hanterdro said:

    great to hear... so all plugins from Nik 1.x will work again?

     

    To bad, that I bought 2.0, because I expected that 1.x will never work again >:(

    And the worst thing is that with Nik 2.0 the for me very important HDR plugin is not working *sigh*

    Wasted 100 bucks because of that :S

    They should have provided you with an upgrade option? I'd contact DxO. On a lighter note, those plugins used to be $150 EACH...

  10. 20 minutes ago, Dewey said:

    Original Poster : I bought Affinity Photo thru the Apple App Store. [ Henceforth I will give Serif all the opportunity and money ]

    Apple is notorious for DEPRECATING  their own software over time ( not all that is new is progress) and demanding others do the same , for various reasons not all of which are defensible - unless you believe in Gordon Gecko's  ' Wall Street ' quip  that " greed is good.

    I certainly hope it was not Apple that monkeywrenched Affinity, but I suspect it probably  is .   That Xcode 10 SDK thing.

    Others posting say that SOME of the Nik apps still work in AfP v.1.7...such as the very useful DFine . I haven't tried since the ' Updating Fonts...' debacle.    I only desire that Color Efex 4 work.  It is at the least very weird to me  and at most a little sinister that some of the Nik bundle  still worked, and some did not , after the Affinity 1.6--->1.7 update. I checked to be sure that everybody was on the same Bit plane....  all were and remain 64 bit apps; and the older Niks were installed cleanly. To Wit:  my Photoshop CS 5 ( which I have not opened in a year thanks to Affinity  supplanting it )  ran the Nik bundle just fine years ago, and CS5  works all the way back to Mac OS Snow Leopard 10.6  and all the way forward to High Sierra 10.13 ( I am stuck at  El Capitan 11.6 because my Mac Mini cannot do the  Sierras )

    I just want the stuff to work today like it did last week after what should have been a  rudimentary upgrade.  Semi retired on low fixed income means my days of paying $ 600 for full Adobe Photoshop like I did in 1995 are long gone.   That would be $ 1500 in current dollars. And I am wella ware that Nik used to sell for big bucks in another epoch. But here and now being able to afford $ 150  for the new Nik v2.0 is not really a financial  option.... DXO is w-a-a-a-y  down my   $oftware wi$h li$t.   

     

    That is just it. This worked OK last week, then automatic updates are applied, and "poof". I don't have the $$ to pay for Nik 2, either. And frankly, I shouldn't have. I am not sure if they do ANY testing before they roll these out? And then the claim that b/c you got this from the AppStore, too bad for you? AFAIC the "right" thing to do here is to apply a bug fix so that Nik, whatever the version, or for that matter other plugins are usable. DxO plugins instantly crash the software. If you're building an app like this, wouldn't you be thinking about stuff like that as you develop it?

  11. 4 minutes ago, MEB said:

    Hi dolunaykiz,
    Where did you bought Affinity Photo? In the Affinity Store or in the Mac App Store?

    I am on a Mac. And if you now try to tell me that too bad, it's not possible because that's how I got it, we all know these are files in the end, and if you have them for Windows, you can make one available for Mac. I want to like this software, but you're not making it exactly easy.

  12. 23 hours ago, MEB said:

    Only Nik Collection 2 by DxO works with Affinity Photo 1.7. The version you own only works with Affinity Photo 1.6 (see first paragraph here in this same thread for more info).

    Well, then give me an option to roll it back. And it would have been nice to know before the update.

  13. 38 minutes ago, fde101 said:

    It is those expectations which need a reality check.

    There are a few standards for professional audio plugins which are designed to work across different hosts - audio units, VST, etc. - and even those have issues between some plugins and some hosts.  In some cases, a plugin that works perfectly in one host will crash another - and those standards are designed to support different developers' plugins on different developers' hosts.  Some hosts actually spin up separate processes for each plugin so that if a plugin crashes it doesn't bring down the host along with it, as this has become a common occurrence...

    The Photoshop plugin SDK is designed to allow plugins to work with... Photoshop, and possibly Lightroom.  Nothing else.  The fact that the Affinity apps can work with any of them is already more than the plugin format was designed to handle, so being able to use any Photoshop plugins within Affinity Photo is an accomplishment to begin with.

    I've waited for decades for somebody to take on Adobe's monopoly. I am not expecting Photoshop. I expect a program I can actually work with, not something where a bug is fixed here and then something else breaks.

  14. 1 hour ago, MEB said:

    Hi Max123456, dolunaykiz, everyone,

    ...The Nik Collection (and other third-party plugins) were originally developed for Photoshop using the Adobe Photoshop SDK (software development kit). Due to the lack of feature/functionality parity not all plugins work in Affinity Photo - we only support basic image filters. Any other plugins types, import/export file formats support or any plugin relying on automation is not supported/will not work in Affinity....

    You do realize what you're saying here, right? If you didn't want to be an alternative to Adobe's overpriced products with a similar functionality, why do this at all? You must have known that professionals switching to you would expect their plugins to work, or at least not crash like this. I'd recommend y'all go back to the drawing board and decide what business you want to be in. In the meantime, please make it possible to roll back from the 1.7 update to Photo so I can go back to editing pictures. Please and thank you.

×
×
  • 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.