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 ... 4 5 6 7 8 Previous Next
  • Currently Being Moderated
    Mar 15, 2012 5:26 AM   in reply to shopaholicann

    Know how you feel..  Live long and prosper!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2012 6:21 AM   in reply to rrr_hhh

        Well !!!!! Never used a patch before, don`t know how it works, but dam it does...

     

    Thanks to you all.. Tron, rrr-hhh, Brett, and those whose tags I`ve lost.. Your help has been greatly appreciated. LR4 with the Nik Suite is fully functional as of 13.00 GMT ...

     

    Hats off the the chap that wrote the patch: back on page 4 of thiis forum.. Was unsure - read very not confident - and concerned that I may inavertatly screw up the OS..

     

    But hey it works..

     

    If I can do it - hope this may give those who are not totally PC confident - like me - to have a go...

     

    THANKS AGAIN...  off to have a coffee now , I`m knackered.

     

    Vince

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2012 6:28 AM   in reply to Vincent Vincenzo

    I am glad it works for you, but it doesn't work for me on my MAC OS Lion. Even more ironic is that Elements 9 also doesn't work as a plugin in Lightroom 4.

     

    It's an Adobe problem and they should get it fixed with an update. Lamely saying it worked on the beta version isn't an answer. It just shows how sloppy the Adobe crew is to get out the full version so they can start making money even though their program doesn't fully work.

     

    Ed

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2012 6:54 AM   in reply to bonaprof@gmail.com

    Must admit to not being overly impressed with many of the s/w companies. But going by the dates on the messages in this forum, they go back to August 2010.

     

    Considering they make a LR edition of Nik plug-ins, seperate to the CS5 edition, I would imagine Nik are not totally without blame.

     

    But I thought I read for MAC users download a trial edition of CS5 would solve your problem; Or have I miss-understood the thread?

     

    Nothing is more frustrating to have s/w you cannot access, through no fault of your own..

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2012 7:26 AM   in reply to Vincent Vincenzo

    I think you are misunderstanding the issue. Adobe recognizes that plugins not working (including Elements 9) it is their problem and are seeking a solution. Apparently, the plugins worked for the beta version of Lightroom 4, but the full upgrade, which Adobe started selling a week ago, does not. Adobe says its engineers are working on the problem.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2012 7:56 AM   in reply to bonaprof@gmail.com

    I think I can offer a solution.  If the beta worked perfectly but the new full version doesn't, why not simply switch them round? Sell the beta as the full version, and the full version can be taken back to beta whilst they put back the code they took out.  Can only take an hour or so surely.

     

    Of course, they'll need to swap the spplash screens too. Expect they'll rememebr that though.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2012 9:08 AM   in reply to Brett N

    To save time for new folks just joining the thread who are hopefully skipping to the end to cut to the chase, here's a link to the post by Brett (Adobe customer support) providing the workaround info for both Windows and OS X users.

     

    http://forums.adobe.com/message/4264823#4264823

     

    Brett N wrote:

     

    Thank you all who have reported on this forum post. We are aware of the issue, we are working on a fix. We do not have a release date for this fix yet.

     

    Having ready through every post, the conclusion is there are currently one workaround per OS:

     

    Win:

    Artificially create the registry keys required by Lightroom (Thank you justme06 and b_gossweiler):

    1) Open Notepad

    2) Copy and paste everything in bold below into Notepad

     

    Windows Registry Editor Version 5.00

     

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Photoshop.exe]

    "Path"="C:\\Program Files\\Adobe\\Adobe Photoshop CS5\\"

    @="C:\\Program Files\\Adobe\\Adobe Photoshop CS5\\Photoshop.exe"

     

    3) Go File > Save As

    4) In "File Type" Select "All files"

    5) Name it "LightroomPatch.reg" and save to your Desktop

    6) Close notepad and double-click "LightroomPatch.reg".

    7) When it asks if you trust the source, click "yes"

     

    Mac:

    Download and install the trial for Photoshop CS5

     

    When the patch is released, I'll post an update here.

     

    Mac OS X users note: Installing Photoshop Elements 10, on a trial or paid basis, will not resolve the problem. Installing Photoshop CS5 will. This workaround will continue to work even after the trial period expires.

     

    At this point we'd be best serving newcomers to this thread if we keep pointing them to this information rather than engaging in verbal jousting.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2012 3:49 PM   in reply to awyvr

    As an addendum to the redirect that awyvr posted above for those seeking the Windows and Mac fixes and in particular for those like Vincent earlier who are not fully au fait with computery things I'd just mention the following.

     

    1. Windows users only need to apply the patch as copied to Notepad and linked above. However, Windows users who are not comfortable releasing a patch they don't understand on to their computer can instead download and install the CS5 trial software.

     

    2. Mac users apparently can only sort the problem by downloading and installing the CS5 trial. The patch doesn't apply to Macs.

     

    3. Both Windows and Mac users who decide to go the CS5 route only need to install the software NOT run it. In other words once the CS5 software trial is installed i.e. added to the list of programs on your computer you don't need to launch/open/run the program. Its presence on your computer is enough. This has the added advantage of not initiating the trial period so if an Adobe fix is not available before long the CS5 trial will continue to sort the Edit In problem without expiring.

     

    Plenty of people have now got LR4 working using the above methods. The CS5 install is straightforward apart from the download time and risk free. The Windows patch is one of those things which tinkers with the fuel fods of your computer but so long as the very concise and simple instructions are followed it too is completely effective. Anyone wading this far through the thread and still not convinced LR4 can ever be worth the price paid please be reassured that these answers that other forum respondents have come up with do indeed do the trick.  

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 15, 2012 4:24 PM   in reply to Vincent Vincenzo

    I just received a mail by Nik Software. Among other things they say:

     

    "Important information on compatibility of Nik Software plug-ins with Lightroom 4

     

    Adobe update for Lightroom 4 to be released soon

     

    Some users have experienced problems when using external plug-ins within Lightroom 4. The reason for this a bug in the retail version of Lightroom 4, which unfortunately may also affect Nik Software plug-ins under certain circumstances. Adobe is already working on a solution, which will be available with their next update.

    Upon release of this update by Adobe Nik Software plug-ins can be used within Lightroom 4 as usual. Please make sure to download the newest version of your plug-ins before using them in Lightroom".

     

    I shared this info just to let everybody know that Adobe, Nik and most probably the other plug-in companies are collaborating to solve the problem. When I noticed the bug in my just-bought LR4 I was very upset, as most of us. But seeing that companies, and especially Adobe are working seriously on it, makes me feel better.

    We are not being left alone with the software we bought, let's be patient.

     

    A suggestion to Adobe customer care: maybe sending a mail to customers who bought LR4 on Adobe's site, explaining the situation, could be a good way of letting customers know you care about them. This will not avoid completely angry messages on fora, because many people may have bought it somewhere else, but sure it would help in keeping things smooth.

     

    Good work everybody!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 16, 2012 2:28 PM   in reply to Brett N

    Justed triwed the work around(Windows Registry Editor Version 5.00

     

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Photoshop.exe]

    "Path"="C:\\Program Files\\Adobe\\Adobe Photoshop CS5\\"

    @="C:\\Program Files\\Adobe\\Adobe Photoshop CS5\\Photoshop.exe")

     

    When I het yes a error message came up telling me

     

    "Cannot import C;\users\Mike\Documents\LightroomPatch.reg: The specified file is not a registry script. You can only import binary registry files from within the registry editor.

     

    Followed the following:

    Win:

    Artificially create the registry keys required by Lightroom (Thank you justme06 and b_gossweiler):

    1) Open Notepad

    2) Copy and paste everything in bold below into Notepad

     

    Windows Registry Editor Version 5.00

     

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Photoshop.exe]

    "Path"="C:\\Program Files\\Adobe\\Adobe Photoshop CS5\\"

    @="C:\\Program Files\\Adobe\\Adobe Photoshop CS5\\Photoshop.exe"

     

    3) Go File > Save As

    4) In "File Type" Select "All files"

    5) Name it "LightroomPatch.reg" and save to your Desktop

    6) Close notepad and double-click "LightroomPatch.reg".

    7) When it asks if you trust the source, click "yes"

     

    Whats up.

    
     
    |
    Mark as:
  • Currently Being Moderated
    Mar 16, 2012 2:41 PM   in reply to MikeWaddell

    And you included the line "Windows Registry Editor Version 5.00" and the rest of the bolded text up to and including "...
    Photoshop.exe "?

     

     

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 16, 2012 2:48 PM   in reply to cinerama

    What kind of text editor did you use ?  You really need a very basic text editor, not one which would format your text a little. WordPad for instance could create problems.

     

    Try creating the document again. Open NotePad and create a new document. Paste the text again. It was written in bold to make clear what the text to paste was. Make sure that you have only unformated text; if you are really in Notepad, you shouldn't see bold character anymore. If you see that, you are not in a basic text editor and this may be the cause of the problem.In order to be sure that you are saving only text and not any format, save your file as text only and keep the .txt suffix. Then rename the file second Brett's indications, after it has been correctly saved as text only.

     

    Well, give it a try at least, this may be your problem, or may be not.. Good luck.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 16, 2012 3:07 PM   in reply to cinerama

    "And you included the line "Windows Registry Editor Version 5.00" and the rest of the bolded text up to and including "...
    Photoshop.exe "?......

     

    Yes, that is necessary.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 16, 2012 3:52 PM   in reply to leicabill

    I have uploaded the file PhotoshopCS5.reg for download. To use it, download it to your desktop, double click it and when it asks if you trust the source, click "yes" (possibly several times).

     

    Beat

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

    Thanks. It worked for both Nix and Topaz Labs.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 22, 2012 12:51 PM   in reply to Andrehilkens

    Can anyone tell me where to look to find out why I don't have the individual Chanel controls inTone Curve in LR4 ? - (as well as not being able to use any of my plugins!)

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 23, 2012 11:24 AM   in reply to Brett N

    Hiya Brett,

     

    I tried installing the Photoshop CS5 trial. I already had Design Premium CS5 installed, as well as the CS6 trial. but I installed the Photoshop CS 5.1 trial anyway. No dice - Nik plugins still don't show up in the "Edit in..." menu. Any thoughts?

     

     

     

     

     

     

    Cheers,

    Sohail

    ---

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 23, 2012 11:26 AM   in reply to sohailmamdani

    Had you already installed the updates for your Nik plugins? They came out with a minor update to make their products compatible with Lightroom 4.

     

    http://www.niksoftware.com/downloads/usa/entry.php?view=software

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 24, 2012 5:06 PM   in reply to Brett N

    Can someone explain how the registry edit for windows works, which appears to install photoshop CS5 references, for someone who has never had photoshop installed and doesn't use photoshop?

    Does it actually work in this case?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 24, 2012 5:27 PM   in reply to mr.nik

    I'd also like to respectfully remind those who have judged this bug to be a "minor inconvenience": please don't judge the impact on others by the impact on yourself.

    It may well be that your workflow rarely relies on this feature. In contrast, mine totally relies on it.

    Most of my projects (paying and non-paying) are stalled until this is fixed (by whatever means - will try the reg fix if I the answer to my previous question is positive).

    That impact is not a "minor inconvenience" regardless of how brilliant LR4 is in every other feature/function. 

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 24, 2012 5:59 PM   in reply to mr.nik

    Those people who want to treat this whole incident as a minor inconvenience fail to realize that there are many 

    photographers out  there (pros included) who use these plug-ins, especially NIK plug-ins, on a daily basis 

    as part of their normal work flow. Take the plug-ins away, and productivity come to a stand-still. I still want to 

    explore all that's new about LR-4, but I can't do much with the upgrade until they fix this problem. Thank God

    I have LR-3 to fall back on.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 24, 2012 6:50 PM   in reply to mr.nik

    The registry fix works whether you had Photoshop installed or not. I'm sure this has been addressed a number of times in this thread. The Mac OS X fix works.

     

    You are correct, I do consider the problem to be a minor inconvenience. Since reliable work arounds exist for Lightroom 4 running on either Windows and Mac OS X, for now, the "problem" is solved. No (more) downtime.

     

    Or, don't upgrade, use LR3 until the next LR4 release comes out. Problem solved.

     

    Or, if you've upgraded, downgrade. Problem solved.

     

    No one needs to be down. Do the workaround, or stay with LR4, or go back to LR3.

     

    In my books, LR4 delivers advantages worth any minor inconvenience.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 25, 2012 3:31 AM   in reply to 7thsojourn

    @7thsojourn - i think, unfortunately, there are some who confuse the complexity/nature of the problem/fix itself with the actual impact on a user. Or certainly give that impression. User experience often comes low down the food chain. Let's hope none such work for Adobe, who I'm sure are making double efforts to test a core fix.

     

    A certain feature might seem simple and trivial, broken for a silly reason, fixed by a simple manual intervention. But that doesn't mean that while it is broken it doesn't have a large impact. It's a bit like saying that a missing a SAVE command is a small hiccup, because you can poke around the web and find a simple set of instructions to create a workaround. Meanwhile, until you have done so and the feature is unavailable to you, it is a big impact on your work. Missing that feature will always be a big impact. And so it is with the "edit in" feature in my own workflow.

     

    It actually doesn't matter what anyone else *thinks* - it's you, or I, that determine what the impact/incovenience is to ourselves if the function is broken. The functionality is essential for me. Missing an essential fuction is more than inconvenient for the duration it is missing.

     

    Thankfully, the hours wasted sorting it are reasonably small. But upgrading, downgrading, hacking around, installing stuff or whatever strategy one chooses - all takes time and effort, may or may not end up with the desired result (I fail to see how reverting versions "fixes" anything, it merely "avoids")  and it's down to ourselves to value that effort.

     

    For the benefit of others: I applied the registry fix and it has indeed eliminated the parameter error generated by the "edit" function. In my case it was not NIK software, but all my other editors including Tiffen DFX, Topaz, various Corel...

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 25, 2012 8:32 PM   in reply to mr.nik

    Shortly after writing my comment that you received, I got a note from someone more or less blasting me 

    for begin so dependent on plug-ins, and not being flexible enough to proceed without them. I had tried to 

    explain that many professional photographers use these plug-ins as part of their regular workflow when 

    they're in the editing pictures. Regardless of the new features found in LR-4, if you need to use these 

    plug-ns, then you can only proceed just so far in the upgrade and then, as in my case, transfer to LR-3 to 

    use my NIK and Topaz plug-ins. 

     

    Who knows, it could be that the guy who wrote me wasn't making a living as a photographer and, therefore, 

    couldn't feel the sense of urgency that the rest of us feel. Meanwhile, I'm still not hearing of a fixes appearing 

    on the horizon.   

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 25, 2012 8:52 PM   in reply to 7thsojourn

    7thsojourn wrote:

    Regardless of the new features found in LR-4, if you need to use these

    plug-ns, then you can only proceed just so far in the upgrade and then, as in my case, transfer to LR-3 to use my NIK and Topaz plug-ins.

     

     

    But that's not true. If you want to use your plug-ins from within Lightroom 4, you *can*, right now, provided you follow the temporary workaround steps that have been clearly documented.

     

    Instead you seem to be making a choice to make your workflow more complicated than it need be at this point. I'm honestly interested - what holds you back from following the appropriate workaround?

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 25, 2012 9:05 PM   in reply to awyvr

    There are many of us "photographers" that are not necessarily "registry savvvy" I am one and while it works it can be a very risky move if you do not know what you are doing and mess up. Also downloading another product to get LR to function as advertised is a step no one should have to do. You purchase software with an expectation it is going to work as advertised.

     

    While I appreciate the dedicated folks on this forum for finding and testing the workarounds and doing Adobe's job for them. I do not have that luxury and spend most of my time in the field earning my living and not being a computer jock. I will stick with LR 3.6. By the way, this is not the only issue that is impacting many users - LR4 should go down in history - the public Beta worked better than the released version!!!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 25, 2012 9:45 PM   in reply to MikeKPhoto

    On the "Registry" boogeyman...

     

    Adding a single key to the registry is less risky than allowing anyone, including a photographer, from using Windows Explorer (or Mac Finder) in the file system where one keystroke - the delete button - can, conceivably, wipe out an entire disk. Is that dangerous? Yes, you bet!

     

    The Windows Registry seems all mysterious but at its core the Registry is a central database of information that Windows and programs running on Windows can use to gain access to configuration information. Adding a key (an entry in the database) with a value is somewhat akin to adding a contact in your email address book.

     

    Sure, it is possible to horribly screw up. Theoretically possible. No doubt some do.

     

    I've never seen it happen myself, and I've seen plenty. I have however seen the aftermath of people deleting files by accident, plenty of times. So which is more dangerous - performing a routine task (file manipulation) or performing what might be a once-ever task (updating the registry manually)?

     

    Updating your registry by hand with the information provided is a relatively low risk activity. Further reducing the risk of an accident, a file containing the edits required has been created and distributed (see up thread) which will eliminate the possibility of user-driven keystroke mistakes fouling up the edit.That makes the fix simple and safe enough for the masse  - point and right-click and install. Done.

     

    Warnings come along with such activity because it's just prudent to put the burden of responsibility on the user, not because the activity in this case is inherently dangerous.

     

    I would not criticize your choice to say behind at v3.6, Mike, not at all. Staying with the prior version to LR4 was one of the options I outlined a few points above and is a perfectly valid approach that allows you maximum productivity using software you already know and the third party plugins you depend upon will continue to work with no effort on your part.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 25, 2012 10:30 PM   in reply to Andrehilkens

    OK, I am not sure if people are still watching this...

     

    My issue was LR4 was not giving me an OPTION of sending the file to PS with the edits intact. When I would click on edit in PS, it would not bring up the secondary option box; it just sent the original image to PS CS5.5 without any edits.
    I installed ACR 6.7, and now the optional box to send the file to PS with or without edits comes up and it sends the right file to PS CS5.5

     

    Hope this helps.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 25, 2012 11:09 PM   in reply to awyvr

    The problem is that, according to a lot of the messages I've read on this forum, for every person who 

    finds that a workaround works for them, there are just as many who have found that it doesn't. One of 

    the primary suggestions was to download the trial versions CS5 or Elements on my iMac. Well, for 

    some it worked. For others, it didn't.  Some didn't want to take up the required space on their computer 

    for a temporary fix. I'll keep discovering all the new features in LR-4.   

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 25, 2012 11:12 PM   in reply to MikeKPhoto

    Mike: some excellent points. Thanks for sharing.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 26, 2012 11:48 AM   in reply to Andrehilkens

    I my previous post I mentioned falling back to LR 3.6; this has restored my workflow and back in business. But I have to say I am really peeved; as I have put in a lot of time and effort in converting catalogs, trouble shooting, trying to find out why some of the basics do not work as advertised. The big peeve is I paid for this upgrade and Adobe is using my hard earned money - yet I cannot use the product as advertised; something is not right here.

     

    While I know this is not an Adobe support site, I know that Adobe does look through these posts and sometimes, usually at the engineer level post comments; but would be nice to hear from Adobe what their customer support plan is for this release and when we can expect a product that is equal to, or better than the public beta.

     

    While I understand that there will always be bugs in software there are some that should never have made it out the door. </rant>

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 26, 2012 11:58 AM   in reply to MikeKPhoto

    Mike: more good points. My point to the folks who keep saying we have to press on and use the workarounds (which, by the way, don't work for everyone), is that in the end, the bottom line is that's it's the principle of the thing; we've paid for something that we're not totally able to use. As far as features are concerned, does anyone know if the released version of LR-4 offers that much more than the Beta version? 

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 26, 2012 12:05 PM   in reply to 7thsojourn

    You must ignore them ...

    Here a site of a pro using Nik plugins introducing his results with the new Nikon D800

    http://www.outthereimages.com/blog/

     

    cheers

    /

    Karl

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 26, 2012 12:44 PM   in reply to Tron777

    Great. Thanks, Karl. I know some people are waiting for the price of used D3s to come down, now that the D4 is out. 

    Heck, if yo can't afford a new D4, the D3 is still a great camera. I'm sure, in time, those who can't afford the D4 will be 

    able to a good deal on a used D3. Hopefully the 800 has noticeably improved ISO and focus. Thanks, again for the 800 

    info, Karl.

     

    Fred 

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 27, 2012 9:19 AM   in reply to awyvr

    Yep, tried that too. No dice


    Wondering if the fact that I already had Design Premium installed, then installed Photoshop CS6, has anything to do with this?

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

    Greetings,

     

    Unofficial Registry patch removal (for windows Vista/Win7 32 and 64 bit users)

     

    With the official patch looking like it is comming out soon (RC is apperently out at http://labs.adobe.com/technologies/lightroom4-1/), those who have tried the unofficial registry patch can safely remove it to make know whether or not the official patch works for them.

     

    There are a few ways to remove it but here is what I feel is the safest and most fail proof way.

     

    1) Open Notepad

    2) Copy and past everything between the ******'s (not including the *****'s) into Notepad

    *****************************************************

    Windows Registry Editor Version 5.00

     

    [-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Photoshop.exe]

     

    ****************************************************

     

    3) Now go File--> Save As

    4) In "File Type" Select "All Files"

    5) Name it "RemovePhotoshop.reg" and save it to the desktop or another place where you can remember where it is.

    6) Close notepad and double-click the file you just made

    7) When it both asks if you trust the source (you made it) and after when it says it will "add" the information to the registry click "yes" (it will actualy remove the key not add it).

     

    Reinstalling the Unofficial Patch - if needed (for windows Vista/Win7 32 and 64 bit users)

     

    If the Official Patch does not work for you (remember it is still in RC stage - just a bit above Beta) the unofficial patch can be put in place again by the following instructions (almost the same as above) - True it is a few pages back but hopefully this makes it easier to find

     

    1) Open Notepad

    2) Copy and past everything between the ******'s (not including the *****'s) into Notepad

    *****************************************************

    Windows Registry Editor Version 5.00

     

    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\Photoshop.exe]

     

    "Path"="C:\\Program Files\\Adobe\\Adobe Photoshop CS5\\"

     

    @="C:\\Program Files\\Adobe\\Adobe Photoshop CS5\\Photoshop.exe"

     

    ****************************************************

     

    3) Now go File--> Save As

    4) In "File Type" Select "All Files"

    5) Name it "LightroomPhotoshopPatch.reg" and save it to the desktop or another place where you can remember where it is.

    6) Close notepad and double-click the file you just made

    7) When it both asks if you trust the source (you made it) and after when it says it will "add" the information to the registry click "yes"

     

    Hope the official patch works well for all and hope this was helpful. Thanks for all the other users (like Beat) that helped out

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 1, 2012 5:34 AM   in reply to Andrehilkens

    I had the same problem with Nik and Topaz--got error message when I tried Edit In in Lightroom 4. I installed the latest updates from Nik (3/6/12) and Topaz. Problem did not go away. I installed the trial version of Photoshop Elements, and the problem is solved. I did not even have to open PE.

     
    |
    Mark as:
  • Currently Being Moderated
    Apr 1, 2012 3:17 PM   in reply to justme06

    Justme06 --

     

    Thanks for this!  Both the install and uninstall worked great for me, and kept me from having to install PS or PSE or anything else!

     

    Well done!

     
    |
    Mark as:
  • Currently Being Moderated
    May 13, 2012 4:20 AM   in reply to 7thsojourn

    Hello

    I thought I pass on my expaerience.

     

    Just loaded the AVG 2012 Internet Security S/W that comes with a PC tune-up..

     

    The point is once installed and completed their scans, with me following prompts as they appeared. I went back to using my LR4 and Nik s/w.. Only to find that the famous

    message returned: " Unexpected error performing command: bad argument #1 to `lower`(string expected,got nil) "

     

    After panicing for a bit and swearing .  Came back to this forum.

    Found on my computer the Lightroom Patch I had previously saved and right clicked it to re-save it.

    All now works again, once I`d opened LR.

     

    So for you this may be no great suprise, but as people will use AVG with its PC support alot of people may be suprised when they open their LR4 S/W.

     

    Hope this helps / for-warns anyone.

     

    Vince

     
    |
    Mark as:
  • Currently Being Moderated
    May 13, 2012 5:09 PM   in reply to Vincent Vincenzo

    Vincent: 

     

    I hadn't heard anything on this for quite a while, and was wondering if Adobe had come up with an answer to the software problem by now.

    Guess not. Can't believe it's been such a long time since the problem originally came up. Have you, or anyone else, heard if NIK, Topaz, and others are 

    working with Adobe to fix the problem - or is Adobe just going to forget about it and let us come up with our own solutions? Luckily for me, I still have

    LR-3, and simply switch over to that when I need other software. Thanks for the note. Glad to hear some people are still concerned about this issue.

     

    Fred  

     
    |
    Mark as:
1 ... 4 5 6 7 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