1 3 4 5 6 7 Previous Next 99 Replies Latest reply: Mar 4, 2014 7:20 PM by William Lloyd Go to original post
  • 60. Re: Aperture 3 and NIK- plugins, problems...
    Paul Klenk Level 1 Level 1 (80 points)

    Apparently NIK does not see it that way from a business perspective.

     

    First, NIK knowingly released a product that is defective. And, as you noted, it is easy to reproduce.

    Second, NIK will provide a refund if a request is made. It must, by law, under the Sales provisions of the UCC.  However, the great majority of users cannot be bothered, so NIK profits from selling a defective product. NIK has blamed Apple and transfers the burden to the Apple engineers. Should not this be the jurisdiction of the NIK engineers? Furthermore, the Adobe engineers indicated that the error originated with NIK.

     

    So, short of a class action suit, nothing will be done because NIK is still making a profit. You can file a consumer complaint with the AG's Office and the purchase price will be refunded and nothing more.

     

    This is common practice among many businesses because consumers find it an annoyance to take action. At this very moment, the writers of MacPilot are doing something similar, but even more devious. Read the reviews at macupdate.com.

  • 61. Re: Aperture 3 and NIK- plugins, problems...
    Paul Klenk Level 1 Level 1 (80 points)

    I like the plugin results as well.  They are certainly better than the first iteration.  However, the original version worked, and it worked flawlessly.  So, in version 2.x what has changed?  Rather a rhetorical question because I don't write code.  However, the engineers at NIK do this for a living, so they know.  I find the matter an unprofessional display of arrogance.  Believe me, the letter I received from old "Dino" out of California was devoid of arrogance, but perhaps that's because he was answering to the Attorney General's office.

     

    My position is to pester people/businesses into submission.  Unfortunately, that seems to be par for the course in our current society.  People are fleeced and don't know it or are to lazy to take action.

     

    Still on a quest for a solution . . .

     

    How about this:

     

    Just upgraded to Aperture 3.4.3 and tried HDR v2.x.  Believe it or not, it worked on the two images that I tried with no skewed results.  However, it remains to be seen how long this lasts.

  • 62. Re: Aperture 3 and NIK- plugins, problems...
    Christian Barrette1 Level 1 Level 1 (55 points)

    Paul, the skewed preview hit me right on the first use, after upgrading to Aperture 3.4.3. GPU is still disabled. There has been two minor upgrades from Aperture since HDR 2 came out and there is still no relieve ahead. We Aperture and HDR 2 users just don't count. How many are we ? Less than a dozen ?

    It is useful to remind that HDR 2, as it is, works flawlessly in Lightroom.

  • 63. Re: Aperture 3 and NIK- plugins, problems...
    Daveid99 Level 1 Level 1 (0 points)

    Hi Paul

     

    Have had several contacts with Nik Software now.

     

    Here is the body of the first reply:

     

    When HDR Efex Pro 2 opens please click on the orange Nik logo at the top of the window and confirm it does show v2.003.  If it shows any earlier version we do need to get the update from the Downloads heading at www.niksoftware.com.

     

     

     

    Assuming we are running the latest version please check the three options listed below first.

     

     

     

    HDR Efex Pro 2 takes advantage of the Graphics Processing Unit (GPU) of the computer system. The GPU is also sometimes referred to as the Display Adapter or Video Card, in any case they are all the same. Sometimes certain video cards will not handle this additional processing. You will note this when opening an image into HDR Efex Pro 2 and one or more of the following

    happens: 1.) HDR Efex Pro 2 will crash right away, or 2.) if it opens the imported image will sometimes not be displayed correctly (solid gray, black or white image), or 3.) the buttons will not display correctly, or 4.) the responsiveness is simply very slow.

     

    In order to resolve this, the first measure would be to update the Display Adapters or GPU driver.

     

    Option1:

    Mac Users: Generally the video card that comes with your Mac will be updated automatically. The exception may be when there has been an additional video card added. In that case the user may need to go to the video card manufacturer's website to download an updated driver for their secondary GPU. If you are using Mac OS Snow Leopard (10.6) ensure to update to 10.6.6 or higher as this can affect performance. If this does not apply to you, please go to the next section below.

     

    Option2:

    If after following the above steps you are still experiencing the same issue, the next step will be to either disable the GPU (if possible) or force HDR Efex Pro 2 to not use the GPU (safe-mode). In order to disable the GPU in HDR Efex Pro 2 please do the following:

     

    1. If you are able to open HDR Efex Pro 2 and can see part of the

    interface, see if you can click on the"Settings" button in the lower left.

    1. In Settings locate the section "GPU" and expand it, in this section

    you will see a check box "Enable GPU Processing", uncheck this so the GPU will be disabled, then close the settings window.

    1. Close out of HDR Efex Pro 2 (click Cancel), quit out of any and all

    host applications (Photoshop, Lightroom, Aperture), and then relaunch HDR Efex Pro 2 to see if this corrects this issue.

     

    Option3:

    If you are unable to disable the GPU via Settings or if the issue has not been resolved (e.g. HDR Efex Pro 2 crashes or the buttons are not displaying correctly), please try the following steps below after quitting out of all host applications (Photoshop, Lightroom, Aperture):

     

    Mac Users:

     

    1. Open a finder window (or double click on the Macintosh HD on the

    desktop) and navigate to:

    Macintosh HD : Users : <user name> : Library :Preferences : Nik Software :

    HDR Efex Pro 2

    1. Locate the file, HDREfexPro2.cfg and right-click and choose "open
    2. with..." and then click "Choose" and then locate the applications, "TextEdit" to open this file.
    3. At the very beginning (before all the text) of the configuration

    file, paste the following code below verbatim:

     

    <configuration>

    <group name="INTERN">

    <key name="UseSafeMode" type="bool" value="1"/> </group> </configuration>

     

    1. Now save the file, close it and relaunch HDR Efex Pro 2 and see if

    the issue has been resolved.

     

    I tried everything and emailed them back - then they asked me what version of OSX I was using. Then no further contact.

  • 64. Re: Aperture 3 and NIK- plugins, problems...
    Paul Klenk Level 1 Level 1 (80 points)

    Dave:

     

    You certainly were persistent and you were given NIK's standard answer regarding the GPU settings.  We have all tried it, but it didn't seem to make a difference.

     

    However, the last suggestion that starts with "Mac Users" is new to me.  Obviously, that did not work for you. By the way, that file is in the ROOT directory and not the User /libary/preferences.  I created a copy and dragged it to the desktop.  Here's the content of the file (not very much):

     

    <configuration>

              <group name="Information">

                        <key name="TimeStamp" type="string" value="2012-08-14T10:57:50"/>

              </group>

              <group name="Installer">

                        <key name="BID" type="string" value="0402"/>

                        <key name="Type" type="string" value="la"/>

              </group>

              <group name="Error">

                        <key name="al" type="int" value="-4"/>

                        <key name="av" type="long" value="14"/>

                        <key name="ca" type="int" value="-4"/>

                        <key name="cv" type="long" value="1"/>

              </group>

              <group name="Activation">

                        <key name="key" type="string" value="0402008265000026201388144"/>

                        <key name="name" type="string" value="Paul Klenk"/>

              </group>

    </configuration>

     

    So, now I'll use the suggestion from your message and I'm going to show it here for the benefit of others.  However, I'm not sure if I should copy and paste before the existing configuration or after it?  I'm going to assume before. So now the context of the file should look like this?

     

    <configuration>

    <group name="INTERN">

    <key name="UseSafeMode" type="bool" value="1"/> </group> </configuration>

    <configuration>

              <group name="Information">

                        <key name="TimeStamp" type="string" value="2012-08-14T10:57:50"/>

              </group>

              <group name="Installer">

                        <key name="BID" type="string" value="0402"/>

                        <key name="Type" type="string" value="la"/>

              </group>

              <group name="Error">

                        <key name="al" type="int" value="-4"/>

                        <key name="av" type="long" value="14"/>

                        <key name="ca" type="int" value="-4"/>

                        <key name="cv" type="long" value="1"/>

              </group>

              <group name="Activation">

                        <key name="key" type="string" value="0402008265000026201388144"/>

                        <key name="name" type="string" value="Paul Klenk"/>

              </group>

    </configuration>

     

    Dave . . . can you verify this for me please?

  • 65. Re: Aperture 3 and NIK- plugins, problems...
    Christian Barrette1 Level 1 Level 1 (55 points)

    Hi Paul and Dave.

    Just to let youy know that I have edited the HDREfexPro2.cfg file as specified and exactly as Paul has posted it. It did not bring any benefit.

     

    -- Christian (B->

  • 66. Re: Aperture 3 and NIK- plugins, problems...
    Paul Klenk Level 1 Level 1 (80 points)

    My configuration may not be correct, because I'm still uncertain as to precisely where, in the string, the new text should be placed.  We need to hear from Dave.  Looks as if he copied and pasted directly from an email, but there still ambiguity.

  • 67. Re: Aperture 3 and NIK- plugins, problems...
    One Big Wookie Level 1 Level 1 (40 points)

    Unfortunately, Nik says that it's a problem with Aperture, and Apple up to this point has refused to respond (at least to me) regarding the issue.

     

    Thoroughly disappointed with both Nik and Apple on this.

  • 68. Re: Aperture 3 and NIK- plugins, problems...
    Paul Klenk Level 1 Level 1 (80 points)

    Quite typical but more so in the PC world.   The consumer is caught in the middle.  However, in this case, software engineers for Adobe (yes, I know it's not Aperture), found errors in NIK's coding and this has been documented.  Read further up the thread.

     

    This still begs the question, if NIK knew about an Aperture issue, then why did NIK release software destined for trouble?  It's all about money!

  • 69. Re: Aperture 3 and NIK- plugins, problems...
    One Big Wookie Level 1 Level 1 (40 points)

    Paul - thanks for reemphasizing that point.  Quite telling as to where the fault actually lies.

     

    FWIW, HDR Efex Pro (v1) doesn't have the issues that v2 has.

  • 70. Re: Aperture 3 and NIK- plugins, problems...
    Daveid99 Level 1 Level 1 (0 points)

    Hi Paul

     

    Sorry for the late reply.

     

    My HDREfexPro2.cfg file actually does not look like yours.

     

    Here it is after the modification:

     

    <configuration>

     

    <group name="INTERN">

     

    <key name="UseSafeMode" type="bool" value="1"/> </group> </configuration><configuration><configuration>

        <group name="Information">

            <key name="TimeStamp" type="string" value="2012-10-12T15:23:36"/>

        </group>

        <group name="Installer">

            <key name="BID" type="string" value="0402"/>

            <key name="Type" type="string" value="pal"/>

        </group>

        <group name="Activation">

            <key name="key" type="string" value="0402007265000222656644083"/>

            <key name="name" type="string" value="David Naude"/>

        </group>

    </configuration>

     

    By the way, this did not work at all.

     

    I am also frustrated by the fact that I never had this problem with HDR efex pro 1.

  • 71. Re: Aperture 3 and NIK- plugins, problems...
    Paul Klenk Level 1 Level 1 (80 points)

    Time to get rough and there is strength in numbers. I forced NIK to refund the purchase price AND keep the product. Furthermore, Dino Danner was forced to respond. Since I have already followed this course, I cannot join the party.

     

    You need to file a complaint with the AG's office alleging fraud and failure on the warranty of merchantability. This is part of the Uniform Commercial Code for Sales. In other words, it is not fit for the ordinary purpose for which it was designed. Here is your defendant info:

     

     

    Corporate Headquarters

    Google Inc.

    1600 Ampitheatre Parkway

    Mountain View, CA 94043

    USA

    Phone (619) 725-3150

    Fax (619) 374-7339

     

    Try here:

     

    http://oag.ca.gov/consumers/general

  • 72. Re: Aperture 3 and NIK- plugins, problems...
    herenow Level 1 Level 1 (10 points)

    I've found that when I launch HDR Efex Pro to edit an image from the Browser in Aperture (instead of Viewer) it doesn't cause problems when after editing I open the image in Viewer...

  • 73. Re: Aperture 3 and NIK- plugins, problems...
    Christian Barrette1 Level 1 Level 1 (55 points)

    Excellent !

     

    I have tried it some 4 or 5 times, and it seems to work. Stay tuned !

    That would be a simple and decent workaround.

     

    -- Christian (B->

  • 74. Re: Aperture 3 and NIK- plugins, problems...
    John Mather Level 1 Level 1 (0 points)

    I'm not sure if this will help. I have been struggling with HDR ƒ since installing the new Nik Collection full download. No matter what I did the plugin would try to save the processed images as a file outside of Aperture. Then, of course, all the dreaded whacked out previews. Nik among other things suggested it was a permission problems though I had explained it was ONLY HDR ƒ.

     

    Here's the email I just sent to Nik that describes my solution.

    *****************email to NIK***********************************

    The problem was simply one of HDR Efex Pro preferences (.plist). After reading this thread on the Apple Aperture Support forum I though I might try to locate the actual .plist file. (BTW you have some pretty ****** customers).

     

    1) I searched in the ~/Library/Prefences folder and found this:Nik plist usr files.jpg

    In addition to these files there was a folder "Nik Software" that contained a folder  " HDR Efex Pro" with this list of files:HDR folder.jpg

     

    2) I moved the "Nik Software" to the desktop.

     

    3) I restarted Aperture & tried HDR Efex. Both crashed.

     

    4) I ran the Nik Collection installer again.

     

    5) I opened Aperture & ran the plugin. It operated completely normally. Problem solved. Including the strange preview issues mentioned in the above thread & experienced by me every time I ran HDR Efex.

     

    At least its solved for me. It appears to me that installing the Nik Collection over the old plugins leaves old files that may interfere with the operation of, at least, HDR Efex. Please remember that I ran the uninstaller from my original HDR Efex installer after experiencing these problems. It must not remove associated files that linger in the ~/Lib/Pref folder that cause the issue.

     

    I don't think my solution will help those in the Apple thread but I will post this there in case it does.

     

    I hope you will test this situation and find a way to resolve the issue via your own installation software. BTW I thought it might force me to re-enter my registration but it did not. Bravo for that.

    ****************end email********

     

    Hope this helps.

     

    Cheers...  John

1 3 4 5 6 7 Previous Next