Jump to content

Dewey

Members
  • Content count

    18
  • Joined

  • Last visited

About Dewey

  • Rank
    Newbie

Recent Profile Visitors

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

  1. FYI to Nik users on MacOSX ---> Affinity Photo Customer Beta update to v 1.7 starts out fresh. Preferences will be blank ( all of them ! ) . That means you have to install the Niks back into Aff Photo manually . The Beta of 1.7.1 will not access your existing Photo version 1.6 Photoshop Plugins folder after installing . It's an all new app. You can of course use your existing Nik plugins from their home folder , such as the directory named " Google" if you installed the free Niks in the past two years or so. No need to uninstall and reinstall a new set of Niks , unless you want to . But why ? They are already there... Here is the best tutorial I have found for getting Nik 1.x to work with Affinity Photo: https://www.photography-raw.com/install-nik-collection-plugins-affinity-photo/ SInce you likely already have the Niks onboard in a home folder, you can ignore the first series of steps. Go straight to the section called ' Setting up the Plugins in Affinity Photo ' . Pay special attention to that second step called " Add plugins folder " , where you direct your Aff Photo to go all the way to root on your system drive to enable all the Nik plugins ( for some reason not all of the seven Nik apps work the same in the core Mac OSX system, which is why we had this ' Updating Fonts ' SNAFU in the first place ) . This requires a very short safe hack to allow your Mac to find and use all of the Niks. Be sure and check the box under the left setup column titled " Allow Unknown plugins to work ' . For some reason I remember having to also check ' Authorize global ' over under the righthand column at some point as well. FInally , you will be prompted to restart Affinity Photo for all this to take effect. ----- Although the Nik apps themselves did not change, they certainly do seem to run better and faster in Affinity 1.7 than 1.6 or 1.5 ! Even on my 2009 Mac Mini running El Capitan on a spinning hard disk ( not an SSD ) , this was quite noticeable. We owe the Serif coders a great debt of gratitude for taking care of this nasty little Nik bug in a week. In fact, the v 1.7.1 Beta did a lot of work under the hood and improved many things. Great job.
  2. I am thrilled that a beta fix has been issued for the Nik bug and other improvements. ( re : the GM seed of 1.7.1 out today ) My question : how does one install an Affinity beta release if I purchased my Photo app via the Apple App Store ? Do I have to wait till Apple blesses it and makes it available ? < groan >
  3. Dewey

    Updating Fonts

    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.
  4. Dewey

    Updating Fonts

    The base differences between Affinity Photo 1.6 and the new version 1.7 were not dramatic, mostly incremental. I see NO reason why the Nik plug-ins that worked in v. 1.6 should not also have worked in version 1.7 with proper coding . But I have a theory why it may have gone down this dark path. That the Nik bundle does not work or result in some really bizarre behavior is highly suspicious to me . Honestly- hanging the app and dishing out an alert that says " Upgrading Fonts... " in a horrible loop ? ---WTF do Fonts have to do with anything here ? Macs are really smart about Fonts in most cases. Always have been. This is not a Font issue... it's something else. If after ruling out a simple coding mistake or a previously unknown software incompatibility , that 'something else' could be something a little more sinister. NIK plug-ins a long time ago were a very pricy software bundle. Then Google bought them to acquire the wonderful tech for its own photo editting platform ( Picasa and friends ) to add value to Google's suite of useful docs. Once Google extracted what theyw anted , they CHOSE to make the entire Nik bundle a free app. Gave it away , with the caveat they would no longer support it or upgrade it. Google was done with NIK and gave it all away. Yes, NIK could be installed into Affinity Photo as it turned out, but that was never a snug fit. There were " issues" and many folks were flummoxed by the atypical means required to install any alleged Photoshop compatible plug-in to Affinity ( Meanwhile over at Thorston Lemke's excellent GraphicConverter, all you needed to do was ' Click-Drag-Copy ' the Nik folder into GraphicConverter's own plugins folder, and it immediately and seamlessly worked. I use it there all the time. It is my saving grace for this whole fiasco ) So---enter DXO. They saw an opportunity to acquire NIK and improve it, adding their own features and values, and turn it into a new/old commercial product. Except that DXO is not the most savvy software marketer on the planet. They made it known right away that the NIK bundle would be wothdrawn from the market as a free bundle, and from then on we had to go back to paying for it. Nik went from being a few hundred dollars at first ; a free bundle when Google reissued it ; and finally DXO makes it a paid bundle again.... I believe they sold it for $ 69 or something while they were developing it forward from version 1.2.1 to the latest version 2.0...... which DXO says they will sell at retail for a startling $ 150.00 ( but if you hurry you can get it now for a mere $ 100.00...........twice the price of the Affinity Photo app it can be installed to. During this travail, DXO went into bankruptcy. Yup. They had to reorganize. The Nik bundle was obviously a company asset that came into play, and was worth something. So--- why does the old Nik version 1.2.1 bundle not work in the new Affinity Photo upgrade 1.7 ....??? After ruling out other motives, it comes down to one basic thing. A LOT of people are dumping Adobe CC Photoshop these days and switching over to our beloved Serif Affinity line. DXO is watching a large portion of its market for the Nik bundle evaporate. The Adobe sector. I am going to postulate a theory --- and it's just a theory --- that DXO and Serif came to some kind of arrangement to neutralize Nik v. 1.2.1 going forward. Yes, it still runs in AFP 1.6.7 as we all know. What we don't know is this: Was Nik purposely deprecated by the new version of Affinity Photo ? That could only have happened by Serif and DXO colluding to make it so. DXO needs to make money ...that whole bankruptcy thing, plus just plain old general business in an increasingly competitive photo imaging world. My theory is the old Nik 1.2.1 bundle was purposely deprecated to not work in Affinity 1.7 and beyond. Purely for monetary reasons, with both software companies looking past one another with a wink and a nod. Serif improved Affinity Photo's plugin handling and feature set, and that is good. DXO needs to make money, and that is desirable and necessary , especially with the specter of Chapter 11 bankruptcy lingering . Although the company exited bankruptcy last year, there have to be consequences met. Serif Affinity probably considers NIK to be a nuisance at worst, or a distant relative's orphan they were forced to adopt at best, so they reluctantly agreed to nurture it , without investing much into it beyond feeding it. Today we have a new deal all around. We Affinity users are forced to purchase version 2.0 of a perfectly good software bundle we already have that was working great last week , but hardly at all this week. I really REALLY want my Nik Color Efex 4.0 to work in A. Photo 1.7 --- I use it several times a week . I also make good use of the other Nik apps, especially DFine. Oh by the way , I am a commercial photographer, so all this goes straight to my bottom line. The frustration with Nik not working for me this week is real. I can still use GraphicConverter 10.7 to do my Nik work...in fact my workflow has both Affinity Photo and GraphicConverter open all the time and I use both together, with Nik commonality. It's sweet. But now has soured somewhat. If it is just a simple software coding fix and we get existing Nik 1.2.1 to work in Affinity Photo 1.7 + , that would be most excellent. The best solution . Just...Fix...It. If however it turns out that Nik won't work in AFP 1.7 and we are forced to purchase version 2.0 of Nik from DXO for what I consider a gouge price of $ 100- $ 150 to get back Nik compatibility, I probably won't buy DXO's version of Nik. Not because it doesn't work , just because I feel I am being played. Taken advantage of. The new NIK from DXO as an Affinity plugin is not and cannot be worth more than the Photo app it is being installed into... the MOST I would ever pay for Nik now is $ 50.00 , tops. Take it or leave it, DXO. If you expect me to pay $ 150 for your new Nik bundle, it is incumbent on you to add a very huge amount of new features , capabilities, and real value to justify that steep price jump. It had better make rainbows out of thin air... Bottom Line : I really hope Serif comes thru with a clean fix for restoring Nik 1.2.1 to Photo 1.7 , and very soon.
  5. I have the same issue. The brand new AF 1.7 hangs when trying to use the older free version of Nik plug-in filters, specifically Color Efex 4. A one line alert box came up " Updating Fonts" with the spinning sprocket. It persisted. No other apps affected, just AF I had to go deep into the MacOS utility Activity Monitor and select Affinity as a process, then Force Quit the AF app using an Activity Monitor menu command called " Send signal to process" . That process showed as HUNG (sigh ) or somesuch. The standard Quit Process command did not work...had to look for another means and found that command under Activity Monitor's VIEW" menu I use my NIK plug-ins a lot, and they were working just fine in AF 1.6.7 before I updated. ----- Serious bug for me
  6. Updated to AF 1.7 . The first time I opened my Nik plug-in to Color Efex 4, Affinity Photo hung . An alert apepared " Updating Fonts..." with the spinning sprocket gear . After many minutes AF was still hung. I had to go deep into Activity Monitor to Force Quit Affinity Photo 1.7. I'm calling this a serious bug, because I use my Nik plug-in filters a LOT... ------- Mac OS 11.6 El Capitan
  7. Dewey

    Updating Fonts

    I just encountered this same exact issue. After updating to new AF version 1.7.0, the first time I opened my Nik filters, AF hung and an alert popped up " Updating Fonts " with the spinning sprocket. After 5 minutes of this, I had to use Activity Monitor to Force Quit Affinity Photo to kill the process. It's a serious bug, for sure.
  8. Dewey

    Scanner support

    Does Affinity photo not link to Apple's Image Capture ? That is a system level utility that while it looks like a standalone app is used by a lot of image apps in the background. For instance, I use Nikon Transfer 2 to download direct from my DSLR cameras to the folder of my choice. Activity Monitor shows the Image Capture extension is doing the work. Surprisingly, Nikon's software is the default for getting photos off my iPod Touch tablet , too . Image Capture has ways to set preferences for handling incoming images and devices. I learned that when I needed to utterly blackball Apple Photos from ever showing up on my Macs for any reason. Image Capture is suprisingly adaptable. Dunno why it couldn't be a bridge between Affinity Photo and most scanners. It's worked with everything I've tried. ( But there are better choices. My Epson Perfection 600 flatbed scanner does not play well with anything but EpsonScan except for the most basic quickie scan jobs ) I've heard that Image Capture is not unique to Apple or even created by them . It's generic or even open source, and Apple just appropriated it. There may even be a Windows version , but I'm illiterate and antagonistic to Microsoft
  9. I would very much like to purchase a copy of that huge glossy Affinity photo hardcover workbook. But I understand that an update to Affinity Photo is pending, from the current version 1.6.x to the 1.7 in the near future As much as I use the online video tutorials , they are too often on the arcane side. I feel the hard copy " encyclopedia" would be much more valuable to learn from, and of course as a reference, to supplement the tutorial vids. This is about my only criticism of Affinity ... getting up and over the learning curve. Videos good. Textbook better ! Will the workbook be updated any time soon ?
  10. Worse, I believe DxO Labs went into recievership and possibly bankruptcy back in April. https://www.ephotozine.com/article/dxo-labs-on-brink-of-receivership--32198 DXO always intended to release Nik as a paid bundle late this year or early next after " improving" it....$ 50 to $70 . I'm not so sure they didn't try to sell the existing " free" version they got from Google for $ 49 for a while. Nik used to be commercial software and sold for something like $ 250 or more. I am glad I downloaded the installer DMG files for Mac, and it's wonderful that the entire latest/last Google-Nik bundle works in both Affinity Photo and my venerable GraphicCoverter 10.x. My workflow uses all three apps all the time. I haven't opened my Photoshop CS5 at all this past year, and I'm a pro
  11. Has anyone attempted to install the new retail DXO - Nik bundle into Graphic Converter 10.x in addition to ojur beloved Affinity Photo ? ( Adobe Photoshop does not come into my life these days.... haven't opened it in months ). It sounds like DXO did not alter the functionality of the various Plugins themselves, but somehow the installation process has been modified, and in many cases is failing. I do hope DXO realizes that many of us here are trying very hard to dispense with Adobe Photoshop CC and Lightroom altogether. It's why we use Affinity Photo. But I never have used Lightroom or Apple Aperture. I've always used GraphicConverter's browser and other functions as my digital image catalogue and management app for over 20 years. We need to double down with both Serif and DXO to assure that Nik will work for us going forward. Sounds like it's off to a rough start.
  12. Fine. WIndows 10 workaround [ check ] What about us Mac OS-X users ? What works there ?
  13. Here is the link provided me by Riley at DXO Support today.... the OFFICIAL compatibility chart for new ( paid version) 2018 Nik software for both Mac and Windows 7-10 https://support.dxo.com/hc/en-us/articles/115015298887-Licensing-and-Compatibility-paid-version-only- Compatibility is charted only for Adobe family of apps , and Apple Aperture 3 . I note again that the Nik bundles have NOT yet been up[dated in any way for features, bugs , etc. They are the same plug-ins ( version 1.2.11 bundle ? ) that DXO acquired from Google. They're just been converted from a free to a paid bundle . DXO has promised all new updated version with new features and OS usability later this year. I also note that the DXO support rep said the' new' paid version may work with other apps , like Affinity, but they do not support that... also note in red the official NON-support for Mac OS-X El Capitan and Yosemite. YMMV So--- It's probably a good idea to rustle up an installable .dmg or .exe for the older free Google version of Nik if you can still find it
  14. I wrote DXO - Nik Support earlier today asking about the ' new ' ( paid) version of the Nik Software bundle compatibility going forward, since DXO really hasn't changed to functionality of Nik for now, and won't until the new upgrade comes out later this year. Specifically , I was asking about compatibility between Nik , Affinity Photo , and GraphicConverter on my Macs running OS 11.6 El Capitan. Riley at DXO Support responded with an official compatibility chart of old/new Nik with past/present apps. https://support.dxo.com/hc/en-us/articles/115015298887-Licensing-and-Compatibility-paid-version-only- It was disheartening to see that the 2018 version of Nik will NOT be compatible with OS-X El Capitan 11.6 or older ; NOT compatible with latest Lightroom or Apple Aperture 3.x - at least not officially. DXO does not even mention Affinity or Graphic COnverter by name, saying only that Nik plug-ins may work but are not supported. (quote) " they may work with other programs, but they are not officially supported by us to do so. ( endquote) Well, obviously they do work , since I am using them flawlessly.... Nik 1.2.11 on Affinity Photo 1.6 and Graphic Converter 10.6 on OSX El Capitan. I'm guessing DXO considers Affinity to be a strong competitor and simply does not want to steer them any business. I do have Nik full install .dmg for my Mac, and it certainly looks like I will not be upgrading to OS X 10.14 Mojave , the new Nik bundle, and worst of all , new Mac computers. I only hope that Affinity Photo remains compatible with El Capitan for the forseeable, since I am leery of upgrading to Sierra or High Sierra. YMMV
  15. June 11, 2018 --- I received notification today that DXO software has issued the paid license version of Nik Software, which they purchased from Google late last year. The Nik bundle is no longer available for free from DXO or anywhere else near as I can tell. DXO has not altered or improved the Nik plug ins much , if at all. Same features and functionality except now you have to pay for it....$ 69 retail, currently on sale till end of June for $ 50. DXO has promised a new improved and updated version of the Nik bundle by year's end. Which brings up a couple of questions. Nowhere on DXO/Nik website does Affinity come up. Nik is stated to work with Photoshop, Elements, Lightroom , and even Apple Aperture. But Affinity is omitted. I use my Nik bundle with both Affinity Photo v. 1.6 AND Thorston Lemke's amazing GraphicConverter v. (10.6 presently, Mac only ). Using Affinity, GC, and the Nik bundle is so feature rich and easy that I have not even opened my Photoshop CS5 in many months. It's almost dead to me. I'm running older Mac's c. 2012 and El Capitan OS nad have no intention of advancing. So I wonder for the rest of you ---- will Nik continue to work with Affinity Photo if either is cleanly installed ? Also, Apple just announced the next version of the Mac OS , called Mojave, which TOTALLY rejigs graphic processing. Apple is moving away from Open Cl and Open GL altogether, instead migrating to Metal graphics management ( say goodbye to 32-bit apps as well ). I will be a sad day for me when I can no longer stay current with Affinity , Nik, and GraphicConverter after apple force-marches us into the Mojave promised land. I simply cannot afford the expense of massive upgrade of all hardware and software. Thoughts ?
×