Jump to content


  • Content Count

  • Joined

  • Last visited

About FxRphoto

  • Rank

Contact Methods

  • Website URL

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Of course it does not affect neither the workflow or the quality. But the purpose of compression is to save space, not to increase it. For 16bits images LZW compression is not only useless but it produces files that are larger than uncompressed ones. And that's the point. Having the choice to use it or not is a key feature, and I guess, not so difficult to implement. A better choice would be to offer a ZIP compression with several degrees of compression (the best method to lossless compress 16bits files), but it is probably a more difficult feature to add. Regarding the fact
  2. After further experiment, the group is necessary. I tried without grouping, just with an adjustment layer and a fill layer with the gradient as a child. It's odd but only the layers are pasted, not the gradient. If I just make a group with the adjustment layer and its child including the gradient, then it works fine. Fx
  3. I guess so Exactly. I use a group just for the purpose of the gradient since it is the only way to apply several adjustment to the same fill layer. The only thing to keep in mind is that, with this method, everything that is copied will be pasted when the macro is runned, even the background layer. So, be sure not to copy it before creating the macro. Otherwise, the same background used to create your macro will always be pasted when you use that macro. (obvious, but it worth remind it) Fx
  4. Hi everybody, I just found a trick with non recordable features. I wanted to create a macro that sets a group of adjustment layers and a fill layer with a gradient to emulate an adjustable neutral density gradient filter. But when I tried to record the macro, I realized that the gradient tool couldn't be recorded (the position of the fill layer was also difficult to set). I created this set without recording and copied the group. Then I recorded the macro with a simple clear selection and paste. I tried this macro several time and it always creates the whole gradient set, even
  5. 1.12.15 is the version number of the whole Nik suite, you need to check the individual plugin version number and compare with the standalone one. For instance in Color Efex Pro, the new version number is (for both standalone and plugin) and the old one is
  6. Hello Christoph L, This is actually the same install method I have described above in this thread. I am quite sure you are running the old free version of the plugin (just check the version number of the plugin in AP). Stand alone apps and plugins work separately. You can run both of them at the same time if you want. So it helps, but that doesn't solve the problem, since the last paid version from DXO remains unusable as a plugin in AP. (they have released a 1.12.15 update indeed, and don't seem to bother informing their customers. We don't even know what changes they hav
  7. Hi OldRadioGuy, Actually, the new version doesn't work at all as a plugin for Affinity Photo for Mac. It freezes during the "preparing image" process and causes AP to freeze as well (need to use the force-to-quit command). Better to stick with the last free version from DXO (1.12.12) or the Google version, no major changes anyway. You will find some other threads on that topic like the one dominik has posted above, or this one :
  8. Hi Chips, For me Photo Mechanic from Camera Bits is one of the best professional choice for photographers but it comes at a cost. (about 150$) This is an Adobe Brige-like software, no catalog. However, Camera Bits is planning to release is 6th version this year, maybe with cataloging option. They have a long experience with their soft, the first release of Photo Mechanic was in 1998, and it is a very good tool, fast and efficient. The support and forum are quite good too. One limitation for now, is that the soft don't display .PDF or .afphoto previews. XNView is also
  9. No, No, as I wrote above, for the plugins, I use the last free version from DXO, which is 1.12.12 Anyway, this installation is the same for any version you want to use, even the latest paid release (1.12.14). I don't think that the installation path could change anything in the plugin working. Fx
  10. Hi Mohammed, Your plugin search folder doesn't seem to be the good one. Actually, according to your screenshot, there is twice the same path, and this is the standalone app path. You have to change for the plugin path, wich is where you create it when the Nik install dialog box ask you for third party applications, then restart AP. Fx
  11. Hi firstdefence, Yes, 1.12.12 works fine in both standalone and plugin versions (this is the latest free version from DXO). Better keep a copy of that one, there isn't any major changes in the latest paid release anyway... If you already have the latest paid version from DXO (1.12.14), the standalone app works fine, but the plugins don't work and cause AP to freeze (you have to use the force-to-quit option). So you can use the new standalone alongside the old plugins (just replace the new plugins folder by a backup of the old one) Fx
  12. Hi Mikerofoto, This screen is the new paid version, but in standalone version and on Mac at least, there isn't any issues running the standalone app. In my post I was referring to the plugin version. The difference is seen in the "save" button down-right of the UI, in the plugin running in AP it is a "OK" button (to apply the plugin to a layer instead of overwriting the file) Fx
  13. Hi Mikerofoto, I have tried your installation according to the screenshot you have provided and it doesn't work for me. Nik still freeze during the "preparing image" process. Have you check this really is the new version that you are running ? Sorry to ask but the first link they send to me after purchase was actually the latest free release 1.12.12 instead of the 1.12.14 paid one. They apologized for that, but first I have thought that everything worked perfectly. The solution I use for now, is to install the new version in standalone and the old one for the plugins. Oddly, whe
  14. Hello everybody, it seems that we are a bit scattered on this topic, there is another thread on the Affinity forum. Maybe you could have a look at the DXO forum : https://feedback.dxo.com/t/request-nik-affinity-interoperability/3203/5 We ought to show up there, so maybe the DXO team will notice that there is not only Adobe users on earth. Fx
  15. Hi everybody, The only way I found so far to use Nik plugins in Affinity for Mac, is to re-install the latest free version of the plugins (they work quite well indeed...), and the new version in standalone. Not really a solution but in the meantime... There is a thread on the DXO forum : https://feedback.dxo.com/t/nik-affinity-interoperability/3203 Maybe if some of the huge community of Affinity users post some messages on it, the DXO team will acknowledge that there is not only Adobe users on earth. Fx
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. 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.