Skip navigation

NIK plugins are not working in LR 4

Mar 6, 2012 6:24 AM

Tags: #lightroom #4 #nik #nik_plugin
  Latest reply: Vincent Vincenzo, Sep 18, 2012 9:27 AM
Replies 1 2 3 4 5 ... 8 Previous Next
  • Currently Being Moderated
    Mar 7, 2012 2:54 PM   in reply to Julie McLeod

    And if a fix is ready, i hope it can be in a form of a small patch and not a 700 mb download.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 2:54 PM   in reply to Julie McLeod

    Julie McLeod wrote:

     

    @Samoreen

     

    Thank you for your detailed and technical explanation.  Much appreciated.  Once the engineers identify the coding problem, I wonder how long it would take to get a fix pushed out?

     

    This is the problem with Adobe. Even for bugs that are easily spotted and fixed, it may takes a very long time until the fix is released. They are not used to release "x.0x" versions like Nik Software do, just to fix a specific bug. They never did this for LR. Chances are that we'll have to wait until they release version 4.1. For me, this is a major bug. If I can't safely invoke external programs or plugins, I'll stick with LR 3.6.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 2:55 PM   in reply to Samoreen

    I think you are 100% spot on the problem.  I only had LR4 and using NIK

    software.  After installing a trial version of Elements (not running,

    just install only), I returned to LR4 and all of the NIK software works

    flawlessly in "edit in" command from LR4.  I know this is only a temp

    fix and only seems to work in PC  Windows systems but at least it works

    for now.  I have 6 other people in my camera club who I called and they

    did the same thing.  They are also all working fine now.  The only

    exception was one person who had a Mac and it did not solve the issue. 

    Such a waste of time to install something I won't use (Elements) but

    worth the time to have LR4 and NIK working properly for now.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 2:55 PM   in reply to Andrehilkens

    I can confirm that the Nik plugins worked fine with Lightroom 4 Beta. However since I bought and installed Lightroom 4, when I use Photo...Edit.. for any of the plugins, I get the "Unexpected error.....bad argument #1 to 'lower' (string expected, got nil)".

     

    The only plugin that works is Nik's HDR Efex Pro which is accessed from File...Export with Preset...

     

    I have Windows 7, 64 bit with 8G bytes of RAM.

     
    |
    Mark as:
  • Currently Being Moderated
    Calculating status...
    Mar 7, 2012 3:05 PM   in reply to Julie McLeod

    Yeah, my LR-3 is just fine. Beware, though, that someone suggested we uninstall our NIK software, then re-install it. 

    I did with my Viveza 2. However, when it came time to type in the product key, NIK would't take it. I'm 

    getting a new one from them. It's shame we have to revert back to 3 until they can get this fixed. Poor Scott

    Kelby - he'll have to hold off on his new LR-4 book for a while

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 3:10 PM   in reply to Samoreen

    Great explanation. Thanks! Now, the question is: does Adobe know this?  :-)

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 3:11 PM   in reply to Samoreen

    Samoreen wrote:

     

    Julie McLeod wrote:

     

    @Samoreen

     

    Thank you for your detailed and technical explanation.  Much appreciated.  Once the engineers identify the coding problem, I wonder how long it would take to get a fix pushed out?

     

    This is the problem with Adobe. Even for bugs that are easily spotted and fixed, it may takes a very long time until the fix is released. They are not used to release "x.0x" versions like Nik Software do, just to fix a specific bug. They never did this for LR. Chances are that we'll have to wait until they release version 4.1. For me, this is a major bug. If I can't safely invoke external programs or plugins, I'll stick with LR 3.6.

     

    I was afraid of that as I can't recall getting very many "x.0x"  updates for previous versions of LR.  It's a very unfortunate thing and one which may have me looking into Aperture.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 3:13 PM   in reply to Julie McLeod

    I'm still wondering why I never had this problem going from LR-2 to LR-3. 

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 3:14 PM   in reply to Samoreen

    Thank you for the insight Samoreen.

     

    I'll post an update once we have more information from our engineers.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 3:20 PM   in reply to 7thsojourn

    7thsojourn wrote:

     

    Great explanation. Thanks! Now, the question is: does Adobe know this?  :-)

     

    I posted this in a thread in which an Adobe employee was participating. I also know that they have received at least one bug report from someone who has a tight relationship with the development team. Any skilled developer reading this error message should immediately understand what's going on. As I said above, there is no doubt about what is causing the error. Developers are using special debugging tools that are able to automatically detect such errors during program execution.

     

    So the problem is not how quickly this can be fixed : this is a matter of a few hours if not a few minutes. The questions are "when will they decide that it is a problem worth considering quickly?" and "how long will it take until the fix is published?".

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 3:23 PM   in reply to Brett N

    Brett N wrote:

     

    Thank you for the insight Samoreen.

     

    I'll post an update once we have more information from our engineers.

     

    Thanks. Now I can simply answer "yes" to 7thsojourn .

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 3:33 PM   in reply to Samoreen

    Thanks Samoreen.

     

    I am definitely not going to upgrade to LR4 as I am running Lion as well.  I do have a question which I don't know if you have an answer but would value your opinion.

     

    Just installed the complete NIK collection last week and updated then (prior to yesterday's update in reponse to the big LR4 bug). Would updating these most recent versions of the NIK plug ins do any good or harm if I still use LR3 only?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 3:35 PM   in reply to Andrehilkens

    As I read all the posted issues here, I ask myself; why have I no issues.  All my Nik plugins worked fine from the beginning.

     

    I am sorry there are so many havining issues.  Wondering; are others fine and just not posting?

     

    Also,  HDR Efex Pro (v. 1.204) posted above is version 1.203.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 4:50 PM   in reply to Andrehilkens

    Same problem here. Tried updating and reinstalling Nik but problem still exists. Topaz plugins won't load either. Windows 7, LR4, all updated Nik components. Worked fine with LR 3.6. Hope a fix is coming soon.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 5:08 PM   in reply to Andrehilkens

    This is Navah, one of Nik Software's Customer Support Specialists.  For some reason, the external editing seems to not work for certain customers using LR4.  Hopefully Adobe will address this soon.  However, it appears everyone we have talked to regarding this issue has been helped either by updating or installing the demo of Photoshop or Photoshop Elements.  I recommend doing this to re-enable functionality for ANY external editors, not just Nik Software, as it is not working on any external editors.

     

    Best Regards,

    Navah

    CSS

    Nik Software

     
    |
    Mark as:
  • Currently Being Moderated
    Calculating status...
    Mar 7, 2012 5:16 PM   in reply to aknbean

    Problem happening to me too. On a very fresh Windows 7 Pro install (I did clean sweep about 3 weeks ago). I realize bugs like this at times may be hard to duplicate in developer studio setting so here is what I noticed.

     

    I agree it is probably not the plugins themselves, rather the "Edit-In" function as mentioned. No matter what program I try to set for edit in (from MS paint to Paintshop Pro X4, to Neat Image to Topaz labs and my NIK plugins) they all return the same error message. It does not make a difference accessing Edit-In through on screen menu (right-click in Windows version) or through the top menu bar.

     

    My LR 3 is still functioning perfectly.

     

    I did try the LR4 Beta but uninstalled it before installing Lr4 retail. I don't think it has much to do with previously trying the Beta as it appears others who did not install the Beta also have the issue.

     

    I tried reinstalling Lr4 with no background processed (eg vscan) and manually setting Administrator rights. No difference

     

    I also tried making a new catalog and imported a single picture with a number only file name and lowercase extension but same error occurred. Upper or lower case file name for called program in edit function did not seem to make any difference.

     

    What did work: I have some plugins Lr/Enfuse and R C Importer that are accessed and managed by the official Plugin Manager. These seem to work just fine when I call them through the "Plugin Extras" menu option.

     

    Computer Specs:

     

    Laptop: Dell Inspiron 1520

    OS: Windows 7 Pro

    HD: WD Black 500gb

    CPU: T9500 Core2Duo @ 2.5Ghz

    GPU: Nvidia 8600m Gt OC

    RAM: 4 GB

     

    Hope this helps a bit.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 5:18 PM   in reply to Mike.101

    Mike: looks like every is having a different problem. When I go into Photo-Edit, instead of getting an "unexpected error" message, I get nothing.

    Luckily, I didn't uninstall LR-3, which I can still use. Also, like you, I can use my HDR Efex Pro 4. I wonder what they different this time around.

    Maybe, someday, we'll all get to use LR-4/  

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 5:20 PM   in reply to Samoreen

    I hear you on that, and since this is an Adobe product, it's got to be affecting users all over the world.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 5:26 PM   in reply to aknbean

    Aknbean, your question brings up what makes these kinds of bugs difficult. I too, have not run into this issue. I already have Photoshop installed, but I did not install it after installing LR4 (infact, I just reinstalled LR4 this morning from the beta to the final release). So it seems the that running the installation of Photoshop isn't what fixes the issue, but simply having the program installed is what fixes it. Strange if that is the case. Has anyone removed an installed trial of Photoshop and seen the problem return?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 5:36 PM   in reply to navah_niksoftware

    Thanks, Navah, I'll go ahead and download the demo of Photoshop Elements. With luck, Adobe will fix the problem before the demo runs its course Thanks, again. 

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 6:02 PM   in reply to Samoreen

    Samoreen wrote:

     

    ... They are not used to release "x.0x" versions like Nik Software do, just to fix a specific bug. They never did this for LR.

    Ever heard of LR 3.4.1?

     

    Beat

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 6:33 PM   in reply to Mike.101

    Mike: It seems as though nothing very consistent is happening. When I use Photo -Edit, instead of a unexpected error" message, I get nothing. Everything still works fine in LR-3, so I'll stick with that for the time being.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 6:46 PM   in reply to navah_niksoftware

    navah_niksoftware wrote:

     

    This is Navah, one of Nik Software's Customer Support Specialists.  For some reason, the external editing seems to not work for certain customers using LR4.  Hopefully Adobe will address this soon.  However, it appears everyone we have talked to regarding this issue has been helped either by updating or installing the demo of Photoshop or Photoshop Elements.  I recommend doing this to re-enable functionality for ANY external editors, not just Nik Software, as it is not working on any external editors.

     

    Best Regards,

    Navah

    CSS

    Nik Software

     

    Hi Navah,

     

    Please count me as one user whose problem has not been fixed with an update or install of Photoshop Elements.  I have uninstalled and reinstalled my purchased version of Photoshop Elements 10 and when that failed to resolve the Edit In problem, I uninstalled it again and downloaded/installed the trial version fresh from the Adobe site.  This did not correct the problem.  None of my external editors can be invoked from LR4 using Edit In.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 7:15 PM   in reply to Julie McLeod

    I was all ready to download the trial version of Elements 10 until I realized that it would take up 3 of the 4Gs I have available on my iMac. 

    I enjoy the speed I'm getting too much to take up that much space with one product. I'll stick with my LR-3 until they offer a solution that 

    works. All I can say is - whatever improvements are available on LR-4 better be worth all this trouble. I prefer to keep upgrading my systems, 

    but this is crazy. And from what you're saying, Julie, downloading all those gigs may not have solved the problem anyway. Thanks for the 

    heads-up, Julie. I feel a little better now

     

    Fred  

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 8:20 PM   in reply to Brett N

    I already had CS5 installed.  The only issue I have run up against was initial crashing.  Though I attributed that to some older Sigma SD14 RAW files that were already showing issues with earlier versions of LR.

     

    I tested again each of my Nik plug-ins tonight.  No issues what so ever. 

     

    Wonder what is going on with others here.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 8:44 PM   in reply to Julie McLeod

    I have just gone through the same process Julie, and no luck whatsoever.

     

    Antonio

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 10:12 PM   in reply to aknbean

    It's all very interesting, to say the least. Some have problems, others don't. What works for one, doesn't for another. 

    Considering there were no similar problems (that I know of) with LR-1-2-3, it seems very strange to me that this 

    has even happened in the first place.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 7, 2012 10:15 PM   in reply to achrysostomou

    For me, LR-4 is dead in the water until they get this problem fixed. When scott Kelby

    releases his LR-4 book, I'll read up on what makes it tick and start familiarizing myself

    with it. Until then, it's back to my old faithful LR-3.6 whatever

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 12:11 AM   in reply to b_gossweiler

    b_gossweiler wrote:


    Ever heard of LR 3.4.1?

     

    Ooops! I forgot this one. Sorry.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 12:19 AM   in reply to ymc226

    Hi,

    ymc226 wrote:

     

    Thanks Samoreen.

     

    I am definitely not going to upgrade to LR4 as I am running Lion as well.  I do have a question which I don't know if you have an answer but would value your opinion.

     

    Just installed the complete NIK collection last week and updated then (prior to yesterday's update in reponse to the big LR4 bug). Would updating these most recent versions of the NIK plug ins do any good or harm if I still use LR3 only?

     

    Sorry for the late answer but I'm abroad and it was time to sleep a little.

     

    There is no problem with installing the latest version of the Nik plugins and using them with LR 3.6. Actually, this is what I'm doing. These updates are here to fix (among other things) a problem that made impossible to update the metadata in the TIFF files generated after invoking the plugins from LR. The bug was first fixed in Color Efex and then they fixed it in the other plugins.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 5:14 AM   in reply to Samoreen

    My 2 cents....After all the farting around and trying this and that....where I am at now is...I have all the latest Nik plugin updates

    installed and I found Lightroom 4 beta, and "re-installed" that....everything seems to work. I might just stay with that until the "fix" for

    lightroom is available.

      BUT  I was I do have elements , which I will prob never use.(since my converting to lightroom) But since i have plenty of room on my hard drive

    I might just install that and see if the full Lightroom works. Really i should just hang tight with beta version, but thats just not me lol lol lol

    I want the full version working now....as i paid for it, !!!


     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 8:06 AM   in reply to 7thsojourn

    Unfortunately 7thsojourn there are pains with every dang release of Adobe Lightroom. I could just kick myself for forgetting my own policy and NOT being an early adopter. I feel SO stupid that I tried to put rational thought into my purchase. "But everyone really likes LR4 beta, I'm sure LR4 will be good too. Surely Adobe Lightroom team has learned from their past mistakes?" And then, for them to be so completely unresponsive about this. How much money would it cost them to delay selling this software for ONE day and actually try it's functionality on for size before release? Since they seem to be able to bungle code just by making it a release from a working fine beta, maybe they should think of testing a bit before release? Naahhhh....that wouldn't be Adobe Lightroom style would it?

    If it seems I am disgusted, I AM. Totally disgusted.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 8:32 AM   in reply to Agnus1

    I also have the unavailable "Edit-in" problem. 10.7.3 + LR3 work fine got LR4 and nothing.  Updated SFex to 2.004. This is the first time ( and I've been with it since the first Beta) that Adobe LR has given me any bother and I feel cheated and angry.  I now have a piece of useless software that I have paid for as I can't readily process my B&W images unless I use LR3.  I've tried the PE10 supposed fix - it doesn't work either.  Get the finger out Adobe and get a fix quick!  Please!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 8:56 AM   in reply to Agnus1

    I'm with you on that one, and because of all the problems many of us have been experiencing, I'm sure it's not doing Adobe (PR-wise)  any good right now. In reality, this is such a simple problem that they should have detected long before offering the final version. I'll read all I can about what LR-4 has to offer over LR-3, but continue to use the former version for now, which still works great. Think about it, the folks at Apple/Aperature must be laughing their heads off right now.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 9:01 AM   in reply to EC2Y

    I'm sticking with LR-3 until Adobe gets its act together. As far as I'm concerned, there simply is no excuse for this to happen. I mean, we're talking about friction' Adobe, folks, not some starter-up in Silcon Valley. As I mentioned to someone else, I'll bet the folks at Apple, who produce Aperture, are laughing their heads off right now. 

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 9:38 AM   in reply to Andrehilkens

    You know I agree with the above statements, I feel the same way .But on a lighter note, I am soo glad it's not just me, as I thought it was something I did wrong at first lol lol lolphoto.JPG

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 10:20 AM   in reply to Andrehilkens

    Add me to the list of those who experienced this error.  I run Windows 7 and did not have PhotoShop Or Elements installed.

    All of my plugins would not load after installing the LR4 release version.   They all worked fine with LR4 Beta and LR3.   Installing the trial version CS5 worked as a temporary fix for me.

     

    Cheers

    Richard

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 12:19 PM   in reply to rturenne

    I'm in the same boat.  Windows 7 64-Bit.  Edit in will not work with any of my plug ins.  Worked fine with Beta 4 and LR version 3.  Tried uninstalling LR 4 and plug ins and then installing again...same problem.  I'm a bit releaved that I only am doing a 30 day trial beacuse if I had paid for the upgrade I would reallly be upset.  Once agian with hundreds and maybe thousands out there with the same problem it's unfortunate that Adobe hasn't acknowledged it has a problem and make an official statement that they are aware of the problem and that they will repair it as soon as possible.  Adobe you reallly screwed up this time.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 1:12 PM   in reply to Circus Hat

    Hi,

     

    I'm Lorenzo, from Italy, and I have the same problem with Win 7 64-bit, LR 4 just installed and the NIK Silver Efex Pro 2 plugin.

    All original software, no cracks, all updates done, but this trouble!

    Work fine with LR3.6, also after the upgrade to NIK version 2.004...

    But with LR 4 no way to "edit in" any file.

     

    Hope in an Adobe solution, cause I would like to start working with this version of LR...

    Obviously I can develop my images with LR 3.6, but i've paid this new version with my sweaty money and i would like to use it.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 8, 2012 1:12 PM   in reply to Samoreen

    Samoreen wrote:

     

    Hi,

    ymc226 wrote:

     

    Thanks Samoreen.

     

    I am definitely not going to upgrade to LR4 as I am running Lion as well.  I do have a question which I don't know if you have an answer but would value your opinion.

     

    Just installed the complete NIK collection last week and updated then (prior to yesterday's update in reponse to the big LR4 bug). Would updating these most recent versions of the NIK plug ins do any good or harm if I still use LR3 only?

     

    Sorry for the late answer but I'm abroad and it was time to sleep a little.

     

    There is no problem with installing the latest version of the Nik plugins and using them with LR 3.6. Actually, this is what I'm doing. These updates are here to fix (among other things) a problem that made impossible to update the metadata in the TIFF files generated after invoking the plugins from LR. The bug was first fixed in Color Efex and then they fixed it in the other plugins.

     

    Thanks Samoreen,

     

    I will go ahead with installing the latest updates to be ready when LR4 finally works for Lion.

     

    Is there a Lion user out there where the NIK or other plug ins are working with LR4?

     
    |
    Mark as:
1 2 3 4 5 ... 8 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (1)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points