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

wtwolf

Members
  • Posts

    16
  • Joined

  • Last visited

Everything posted by wtwolf

  1. Thanks for your reply. Upon further investigation, based on your comment alluding to forward compatibility, prompted me to launch the back-level (1.7.3) version of Affinity Photo and import a collection of macros, primarily to ascertain if they were compatible (and would install) in 1.7.3. Out of curiosity, I "quit" 1.7.3 and launched 1.8.3. The macros carried forward to the current 'production' version without having to reinstall them. Apparently, I had never installed them in the previous version and accidentally launching 1.7.3, seemingly regressed the imports in 1.8.3. I'm still not sure whether this would be considered a bug, but at least I understand the <apparent> reason for the disappearance.
  2. I'm unsure if this is a bug, but I'm using the latest production version of Affinity Photo (1.8.3) on an OS X Mojave platform. I noticed that all previously imported macros had inexplicably disappeared. Retracing the steps prior to this, I had inadvertently launched a previous version of Affinity Photo (1.7.3) -- the default macros remained, but all imported macros vanished. After re-importing the macros, I quit and reopened Affinity Photo (1.8.3), and all remained in the library. Then, I decided to quit 1.8.3 and open 1.7.3 to determine if that might be the cause. I immediately shut down 1.7.3 and again launched 1.8.3. The imported macros had in fact, disappeared. I'm assuming this is a bug and it can easily be recreated by launching a back-level version. Obviously, the workaround is not launching the back-level version of Affinity Photo, but from my perspective, this shouldn't behave in this manner.
  3. Did Affinity Photo Beta v1.7.0.107 change the default program association to open in Beta....? Rather than the latest GA v1.6.7? Everything with an *.afphoto extension launches the Beta version of Affinity Photo after the 1.7.0.107 download and install. I've changed Finder to reflect the default program of Affinity Photo 1.6.7, but somehow it it was changed and it seems to have been consistent with the latest Beta download.
  4. Hi Raymondo, There's no doubt that the beta version of Affinity Photo "broke" several of the Nik plug-ins, but it may not necessarily be the fault of Serif. Also, I'm not ruling out that it is possible the defect could be in Affinity Photo code. Like you, the Nik Collection works fine with AP 1.6.7, though it was quite obvious to me that downloading the trial version of the Nik Collection from the DxO site would have the same result. (I'm using the Google free Nik Collection). I might add that I'm not convinced the problem lies with the Nik Collection, I'm saying it's a definite possibility, and it may not actually be a coding problem, but a simple recompile of the source may result in correcting the problem.
  5. What I believe, Chris_K is saying is that the Affinity Photo beta versions are exploiting changes made in OS X. The fact that Nik plug-ins behave differently under Affinity Photo beta code could very well be related to compatibility issues between Google (DXO) and OS X. I'm experiencing the same issues, where the Nik Collection behaves correctly with Affinity Photo 1.6.7, but with Affinity Photo Beta 1.7, several of the plug-ins display the "Updating Fonts" window and requires a Force Quit to recover. In my case, this is using High Sierra, as I've not yet implemented Mojave. It might be as simple as recompiling the Nik Collection using the latest Apple OSX macros, for lack of more accurate terminology. Which, is probably not going to happen with the free Google Nik Collection. If in fact, it's a defect in Nik code, I wouldn't expect Serif to regress Affinity Photo to accommodate obsolete program code. From what I see, Serif has taken this report for further investigation.
  6. It appears that after installing the Nik Collection a problem with a message "Updating Fonts" surfaces with several of the Plugins. This requires a Force Quit of Affinity Photo. The problem seems related only with the beta version, the Plugins install and work without issue in Affinity Photo 1.6.7.
  7. Thanks for both replies. I did some searches before posting, and didn't find any clarification pertaining to my question. I apologize as it appears my inquiry has been previously addressed.
  8. The Serif website states that Affinity Photo is compatible with the iPad Air 2 (among other models in the current line). I have an older iPad Air (A1475) and it would seem that it is not supported. However, when I go to the App Store, using my iPad Air, under 'Compatibility' it says, "Works with this iPad", also stating, with iOS 11.1 or later. Any clarification? Thanks, Scott
  9. I'm curious as to where custom presets are stored. Rather than recreate several presets in a Beta version, I'd like to copy from the 1.6.6 GA version. Any advice is welcomed. Scott
×
×
  • 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.