My Lightroom i s closed ???

Hi .
I bought an fullversion of Lightroom in january 2014 .
In april i bought a monthly photoshop cc with Lightroom as well ...
After a couple of months i found out i didnt use photoshop that mutch so i canceld the monthly paying of photoshop cc and lightroom .
And now when im trying to use my Lightroom i youst get the message : Develop module is disabled. Please renew your membership to reactivate the develop module ....
Does that mean that i have to buy an another new fullversion of Lightroom , ore can this be fixed easily ???
Please help me fix this ..

https://forums.adobe.com/search.jspa?q=%22Develop+module+is+disabled%22&place=%2Fplaces%2F 1383621&depth=ALL

Similar Messages

  • My Lightroom defaults now closely match Nikon CaptureNX

    I want to speak to anyone struggling with the lack of "punch" and diminished colors of Lightroom compared to their camera manufacturers software (Nikon, and CaptureNX in my case). I can say that at least in my case, I have matched the output of CaptureNX (color and "punch") using a hybrid of 2 techniques I found in this forum. The effort was minimal (less than an hour to set up new defaults for my camera), and it cost me NOTHING! No need to buy a Greytag MacBeth color checker. Because of that, it may not be PERFECT for the purists, but it's close enough to perfect for me and I'll let you judge by my few examples.
    I want to thank Eric (Madmanchan) for his EASY to follow instructions on matching ACR to any given manufacturers raw converter. Reading this made my solution possible for me.
    http://people.csail.mit.edu/ericchan/dp/acr-color-match/
    I used that along with another radical concept mentioned by Will Rees at http://www.reesweb.com/calibrate2jpg. This approach was to try to use a downloadable image of the MacBeth chart, photograph it with Raw+Jpeg, and try to adjust your calibration settings using Bruce Fraser's scripts and ACR.
    I decided to instead try the concept of using a RAW image taken by my camera, of a downloadable MacBeth chart image, and then develop that RAW image using CaptureNX. I then followed the rest of Eric Chan's method (VERY easy) to manually calibrate the ACR image to match what CaptureNX gave me.
    Once I had the calibration numbers, I put them into Lightroom and saved them as the camera default. The whole process took me about 1 hour, and cost me NOTHING. I have tested this with direct comparisons of the CaptureNX output to Lightrooms now default treatment of my raw images and I cannot say enough how happy I am with the extremely close conversions.
    Here is a screenshot of the comparison of my color checker images (the ones I used to compute the calibration)... The one on the left is the NEF developed by Lightroom using the new default settings, and the same NEF developed in CaptureNX. Pretty close IMHO.
    http://www.sbsutherland.com/samples/colors.jpg
    The next images are a comparison of a sample photo which has a variety of colors on it, using the same new defaults in Lightroom for my camera. Top is Lightroom, and bottom is CaptureNX. I had to boost the brightness of the Lightroom image a bit to make them similar, but that is it.
    http://www.sbsutherland.com/samples/photo.jpg
    I have yet to find a sample in my collection of photos that isn't really, really close to the CaptureNX colors and "punch". I am not qualified to comment on the itty-bitty pixel level details of the conversions.
    The point of my post, is that it is possible to use a combo of the Will Rees, and the Eric Chan methods above to quickly create an acceptable (to me at least) calibration that closely matches the look I was used to out of CaptureNX.
    For what it is worth (and I mean that since my numbers seem SO different than other Nikon calibration numbers I've seen)... my calibration settings were (Nikon D70S):
    Shadow Tint: 0
    Red Hue: -3
    Red Saturation: -8
    Green Hue: -9
    Green Saturation: +38
    Blue Hue: 0
    Blue Saturation: -28
    I would encourage others to try this and I would be happy to try to build a complete step-by-step which combines the two methods. I admit, I had to dig deep (basic algebra) to figure out how to keep the color Values "proportionate" using the Eric Method.
    I know that there will be purists that rightly state that a photo of your screen showing a Greytag MacBeth downloadable image is not an accurate way to do this. HOWEVER by comparing the same image taken by your camera off the same screen as you do the adjustments on, using the software you like (with the image the way you like it), and lightroom/camera raw, it is possible to get that image extremely close.
    Looking forward to comments (good or bad) on this... Regardless, I love my ACR/Lightroom conver

    Thanks for this.
    Your numbers are very different from the other numbers for cameras like this purely because you're in fact extracting an approximation of the Capture NX conversion (which is probably far from ideal from a colorimetric sense) instead of to where the patches actually need to come out if you were going for color accuracy. Your method will, in fact, yield what people have been asking for (conversions close to what the camera manufacturers software does) instead of the more correct but duller closer to the actual world parameters that calibrating with a shot of a colorchecker will yield. Very interesting.

  • Cannot open Lightroom 5.6

    "Cannot open Lightroom 5 Catalog because another application already has it open"
    Would anyone know how to deal with this problem? LR is up to date. I have images due for delivery.
    Thanks for any comment!

    This is most likely caused by a "lock" file. It is created if Lightroom is not closed down in the correct manner.
    Jim Wilde has a great answer to a post on lightroomforums.net
    Can't Open LR 5.7 - Lightroom Forums

  • Can't open Lightroom 5.3 catalog. Get  ".. it is not writable and cannot be opened" message.

    Hi everyone,
    I'm having a problem opening a lightroom catalog. I get a message "Lightroom cannot use the catalog because it's not writable and can't be opened".
    The catalog and several thousand RAW files are stored on an external drive.
    Here are the steps which I believe caused the problem:
    1. Worked with the catalog on my PC laptop. Disconnected the drive without closing Lightroom first (big mistake).
    2. Plugged the external drive into desktop PC and did additional work. Closed Ligtroom (on desktop) and disconnected the drive.
    3. Plugged the drive back into the laptop while original catalog was still open (see #1 above). Clicked on an image at which point Lightroom crashed and closed by itself.
    The problem now is that the catalog no longer opens on either computer. Any attempt to open results in  "Lightroom cannot use the catalog because it's not writable and can't be opened" message. There are no lock or journal files that can be deleted, just the lrcat file and tons of folders with preview data.
    I'm hoping that it's not a lost cause and I can still recover the catalog. There are 2 days worth of work there.
    Thank you for any help/advice in advance!

    Ok. I found a solution. Since Ligthroom catalog is a SQLite database, you can use a database tool to fix it. Simply download SQLite from www.sqlite.org for your OS (Windows 7 in my case) and unzip to C:\SQLite for ease of use. Copy your corrupt catalog to C:\SQLite folder as well to keep things simple.
    Go to command prompt Start>Run, type 'cmd' and click Enter. This will open the command prompt where you will need to execute the following commands:
    1. cd sqlite
    2. echo .dump | sqlite3 yourcatalogfilename.lrcat > tempcatalog.sql
    3. sqlite3 -init  tempcatalog.sql  newcatalogfilename.lrcat
    After executing line 3, you may or may not see error messages. No worries, it simply truncated faulty database records which is what cause the catalog to crash.
    Now, copy the newcatalogfilename.lrcat back to your lightroom catalog folder and launch it. You should be able to get things back up and running to where you left of, or to the point where the original Lightroom catalog got corrupted in the first place.
    Hope this helps. It took me a few hours to find a solution, but it saved me at least 2 days of work. The original credit goes to the author of the following article http://www.simplyness.com/more-photography-tips/recover-corrupted-unrepairable-lightroom-3 -catalog-with-sqlite.html. It seemed to have worked for Lightroom 3 and still worked for Lightroom 5.3 in my case.

  • LightRoom Color Management

    Apart from the unique color space and behavior on certain export operations, Lightroom seems rather closed mouthed about color management. (This is a bit unsettling for someone used to all of the control offered by Photoshop) For instance, 1) is there any way to reveal the embedded profile of legacy PS files which have been imported? (all I can presently find for profile is "embedded") 2) what profile (and what gamma) is sent to a printer when printer color management is selected? 3) Is ColorSync enabled? and 4)Finally, is there any source which might make all of this clear?
    Bob Hesse

    Raw files have no color space, they are essentially Grayscale data.
    Existing rendered images have their own embedded profiles and thus color space but IF you apply ANY corrections using LR, you're converting into its internal color space to apply the edits. At that time, you're basically now in ProPhoto RGB (with a linear tone curve) so you might as well export back to 16-bit ProPhoto RGB.
    IF you don't apply an edit, the embedded profile will be honored if you open it in Photoshop.
    You might want to read this:
    http://www.ppmag.com/reviews/200701_rodneycm.pdf

  • Cant download trial Photoshop CC keeps telling me to close Lightroom!

    I am trying to download a trial of Photoshop and it keeps getting to 42% and then keeps giving me this message:
    Photoshop CC Install
    Please close the following applications to continue:
    - Adobe Photoshop Lightroom 64-bit (lightroom.exe)
    Cancel retry
    When I began the download I did have Lightroom open and closed the program upon first receipt of this message.  Clicked retry and continually receive this message.
    What do I do to download the trial?

    Terminate the process in task manager.
    Mylenium

  • Lightroom 2 error

    Hi Everyone,
    I am new to the forums (but not lightroom).
    I was moving around a few thousand photos from within Lightroom.  I closed down the program and when I reopened it, I received the following error,
    attempt to index field 'root folder' (a nil value).  And I cannot open my catalogue.
    The problem with going to my previous backup is that the program no longer recognizes the several thousand photos that I moved.
    Any help highly appreciated.  Thank you,
    Jonathan

    Some more things in random order:
    I think you're right about something deeper going on. The bad install for Flash sounds bad.
    The C++ error sounds like it could be a missing file from something that didn't get installed right.
    You might go buy yourself a new hard-drive, reinstall vista and see if you can get things to work, then, and either use that as your new boot drive or go back to the other one and try again.
    Presumably ScanDisk doesn't show any problems?
    You might disconnect all your USB drives and use just C and see if things work.
    Do you have any permissions issues at all?
    Look in event log and see if it says anything leading up to the C++ error.
    Have you tried reseating the hard-drive cables and memory chips on your MB although usually these things would cause a blue-screen not a C++ error.
    Remove any extra peripherals that you don't need.
    Does the error you get indicate a recognizable GUI-related thing? If so perhaps changing the graphics-card acceleration or other settings could affect it.
    After you system-restore back, are you then installing LR 2.1?
    Why didn't it let you do a Restore and what did you do to finally get it to work?
    This thread started pretty late at night, so the Adobe types are probably not reading things at this point and will have some ideas, tomorrow.

  • Lightroom crashes, won't import catalog

    I added a couple of pictures to a collection via "drag and drop". I selected one and opened the Develop window and got a message something like "unexpected error". I exited Lightroom and restarted. While Lightroom is initializing and has drawn all the windows I get the Microsoft Dialog "Adobe Photoshop Lightroom has encountered a problem". Dismissing that I get a Microsoft Visual C++ Runtime Library error "The exception unknown software error (0x0000015) occurred in the application at location 0x605dabf6. Click OK to terminate the program. Then I get a dialog Program E:\Prog... R6025 - Pure virtual function call". When I click OK Lightroom goes away.
    I restarted and held down the CTRL key. I then let Lightroom test the integrity of the database. That finished successfully, but Lightroom then crashed the same as above.
    I then restarted and held down the CTRL key again. I created a new catalog and Lightroom came up correctly. I then tried to import the old catalog. I get a Warning dialog "Cannot import from this catalog at this time. The catalog is either in use by another copy of Lightroom or was closed improperly. If it was closed improperly, please consider doing an integrity check when opening".
    There's no other copy of Lightroom running. I rebooted. I did the integrity check and it seemed to pass. So I'm stuck at my end. I'd rather not lose the whole day's work if I could avoid it. I do have a backup from yesterday, but I'm hoping there's another solution.

    Lacking any other alternative, I tried to restart Lightroom the next morning with the intent of looking for other options, and it opened without complaint and all was well.
    I'm glad it worked, but it doesn't make me feel real comfortable about the program.
    Bill

  • Major print module issue in LR3

    I've hit a wall in trying to figure out an extremely frustrating issue with the print module in Lightroom 3: every time I attempt to print a contact sheet to PDF, the entire system locks up immediately upon "rendering images," system usage seems at 100% across the board, and I have to forcibly shut down the application via the task manager. After Lightroom has finally closed, I see an error dump txt on my desktop from Adobe Distiller which reads as follows:
    %%[ ProductName: Distiller ]%%
    %%[ Error: syntaxerror; OffendingCommand: --nostringval-- ]%%
    Stack:
    /build_pattern
    %%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
    %%[ Warning: PostScript error. No PDF file produced. ] %%
    I don't know if this Distiller error is in fact initiating the crash or if it's just the result of having forcibly shut down LR-- thus, I guess question #1 is whether this is an Acrobat or LR issue. I have uninstalled/reinstalled Lightroom at least three times; deleted and recreated the catalog; and updated to the latest version 3.2, and the error persists. I've also tried the print procedure with different batches/folders of images residing both on my local and external drives with the same behavior.
    My system info is as follows: ThinkStation E20 w/ X3450 Xeon and 4GB RAM, nVidia FX580 video card, running 64-bit Windows7 and 64-bit LR 3.2; also running latest updated version of Acrobat Pro, i.e .9.3.4.
    Only other thing I can think of that I haven't already tried is to uninstall and reinstall Acrobat Pro, which I've kept from the CS3 suite, although I'd rather avoid doing so if possible. I'll also add that this is a brand new system with fresh installs of *all* software including the CS5 suite.
    Printing contact sheets is one of my most common tasks in LR, so any help is *greatly* appreciated.

    well, interesting development here-- I have to humbly rescind my particular criticism of LR3 with respect to this issue, as much to my surprise after downgrading to 2.7, I experienced the exact same problem-- i.e. upon printing a contact sheet, the program locks up at "rendering images" and brings the whole system to a halt.
    in light of this development, it occurred to me to uninstall (64-bit) 2.7, and reinstall 32-bit LR3-- and lo and behold the print issue seems to be no more. so now the question is why would this be? an issue between LR3 64-bit and the OS (Windows 7 64) ? or perhaps a conflict between LR and Acrobat? maybe a driver conflict?
    any ideas/insights are welcome.

  • Broken link files. unable to link

    I am using lightroom 5 on a new mac. Everything was brought over from lightroom 4 on a pc. Of course everything was unlinked. No big deal, I was expecting this. When I click the exclamation point it asks to link. I navigate to the RAW file and select it. but the preiew doesn't update (never sharpens up) and the exclamation point doesn't go away.  If you click it again it says this photo is already linkded and cannot be linked to a second photo.
    Seems like a bug or a bad install. any other suggestions?

    small update... there is definately a bug. I can relink the file but the warning exclamation point never goes away. I can click to a few different modules (print, web, etc.) then back to develop and it will sharpen up. any that were in that folder also can be viewed at 1:1 clearly. If lightroom is completely closed and reopened the exclamation points will go away.
    Very tedious to relink.

  • My Pictures Locked Up After Download Attempt

    I downloaded some RAW files from a folder in My Pictures.  Lightroom picked up 399 images from a previous trip at the same time.  I deleted those pictures from that folder in Lightroom. I went back to My Pictures to get those 399 pictures back in Lightroom in their proper folder.
    When I tried to download Lightroom told me there were "No Pictures" in that file.. I tried it a few more times slightly altering the Import settings thinking I might have done something there.  When I would try to download a second (or third, etc) time it told me there was a Disk Process going on & I could only do one at a time.  I checked the box to stop the import in the upper left corner.  Nothing happened.  I closed Lightroom, reopened it & tried again..
    Now I cannot open My Pictures with Lightroom open or closed.  Apparently I've clogged something up with so many X's & O's that My Pictures doesn't want to work at all.  When you click on it nothing happens at all.
    Does anyone know how to refresh My Pictures & Lightroom to get things back to normal so the programs aren't feuding & will talk again.  

    I want to thank each of you for your suggestions.  I was going to try each and everyone of them.  Actually, I didn't get a chance.  The night I was having the problem with the mac not shutting down, I unplugged the power connection.  By the time I got home from work yesterday, the battery had died and therefore the mac was finally off.  I reconnected power and waited....it came back up as normal and seems to be just fine.  And no, I didn't get hit by that lightning bolt.  Thanks again!

  • Extension Manager closes down as soon as i try to open

    I am a creative cloud member.  I have downloaded and updated the Extension Manager CC on my cloud desktop, also acquired Paper Textures Pro and Watercolours. I have Photoshop CC 2014 as part of my membership,   When I try to open the Extension Manager I get a message saying it has stopped working and Windows is trying to find the problem and closes the program.
    I have tried uninstalling and reinstalling no different result, I have Lightroom and Photoshop closed down.
    please please can someone advise me what to do to get it to work? - I'd be ever so grateful if I could get it up and running.

    Without exact system info and the crash details from your Event Viewer nobody can tell you much.
    Working with your Operating System’s Tools | Mylenium's Error Code Database
    Mylenium

  • Corrupted thumbnails??

    I use Lightroom 2 to import photos onto my Mac Pro (Snow Leopard OS), then move to Adobe Bridge (most current version) to browse and choose which to open into Photoshop CS4. On a recent shoot, about 5 to 10% of the images (taken on three different compact flash cards) from my Canon 5D Mark II had corrupted thumbnails in Bridge. They either showed no image, just the CR2 RAW logo, or the image showed with a significant portion of it blocked by random colored vertical and horizontal lines. The photos all were fine in Lightroom. I closed Bridge, threw away the cache, and reopened and all was well.
    My question is what is going on? Getting rid of my cache is a pain, because I have to wait many minutes for many files to reappear in Bridge. Is there a way to prevent this from happening again? Could it have been related to the fact that I imported 700 or so very large files (RAW files from a 21 megapixel camera are 25 to 30 MB each)? Thanks!!

    I closed
    Bridge, threw away the cache, and reopened and all was well.
    You first could have used the option to Purge cache for folder using the
    Tools/cache menu instead of deleting the whole cache folder.
    I use Lightroom 2 to import photos onto my Mac Pro (Snow Leopard OS), then
    move to Adobe Bridge (most current version) to browse and choose which to open
    into Photoshop CS4.
    If you only use LR to import your files why not use Bridge for this?, You
    can add several options for it in Adobe Photo Downloader that is in Bridge
    (get photo's from camera). Explore the advanced option window.
    My question is what is going on? Getting rid of my cache is a pain, because I
    have to wait many minutes for many files to reappear in Bridge. Is there a way
    to prevent this from happening again?
    It might have been a corrupt folder but it might have also been something
    else. I tried using LR for import files (include to convert as DNG as I'm
    used to for all my Raw files) but have no problems with viewing them in
    Bridge. Personally I prefer the renaming options in the Photo Downloader but
    that's my opinion )
    Could it have been related to the fact
    that I imported 700 or so very large files (RAW files from a 21 megapixel
    camera are 25 to 30 MB each)? Thanks!!
    I really doubt that, (I have the same files, did not try this amount but do
    work with this amount, and more in Bridge without this problems) unless you
    did something in between with removing card from reader in an incorrect way
    or closed one of the apps during caching but still can't imagine that to be
    the cause, or if you copied the files manual to an other location, etc. etc.
    Nevertheless you might consider to refresh the preferences for Bridge (hold
    down option key while restarting Bridge and choose reset preferences)

  • Exported Library to External HD, error in attempt to link to files on HD

    Hello,
    I recently began using lightroom and stored the files on the local drive of my macbook pro (current os) until I ran out of space. Exported the catalogue to an external HD, then deleted the files from the local drive. As I tried to import the .lrcat file associated with the export to the external HD and received this error:
    "Can not import from this catalog at this time. The catalog is either in use by another copy of Lightroom or was closed improperly. If it was closed improperly, please consider doing an integrity check when opening."
    I am not running LR on any other computers so I figure Lightroom was "closed improperly". However I cannot figure out what to do and tech support will not help me without the serial number which I cannot get as I am travelling. Any advice would be sincerely appreciated.
    Jordan

    If you indeed exported the catalogue to the external drive, you don't need to import it. Simply double-click on the copy of the catalogue that's on your external drive.
    By the way, your serial number is available in the Help/System info menu item.
    Hal

  • Can't Open a Certain Catalog

    I can't open a certain LR catalog. It actually opens briefly, but then LR crashes within 5 seconds. No warning or dialog box shows up, the program just disappears.
    I can open other catalogs, but these are old and are of no use to me. I have also deleted my preferences, but to no avail.
    Is there any way to repair a corrupted catalog if you can't even keep it open? Any other ideas?
    Thanks.
    --Shaun

    Beat,
    Thank you for your response. You seem to be an invaluable resource for the LR community.
    Upon trying your suggestion, I received this message: "Can not import from this catalog at this time. The catalog is either in use by another copy of Lightroom or was closed improperly. If if was closed improperly, please consider doing an integrity check when opening."
    Using the Task Manager, there doesn't seem to be any other instances of LR open. I have LR set to ask what catalog I would like to open when the program starts, and the box is checked to test the integrity of the catalog before opening. When opening my "problem" catalog, the integrity will be checked, no other dialog box will appear, the catalog will load, and then it will crash in 5 seconds.
    I have also uninstalled LR and then re-installed it. No help.
    I'm not sure how to import the catalog in chunks.
    Also, I'm using LR 3.6 and Windows 7 64bit.
    Any other ideas? Thanks so much.
    --Shaun
    Edit: I do have a backup, but it is a month old. I have LR set to back up everytime I close the program, but in the past month it hasnt been backing up properly. It would crash near the end of the back up. I'm now paying for not dealing with that problem sooner...

Maybe you are looking for

  • Link operation and functional locatio

    According to this thread (PM Order - Functional Location and Equipments on Operations) it should be possible to link object list to operations in the Maintenance order. Does anybody know if this functionality is also possible in 4.6c regards peter

  • I have forgotten the password to my ipad

    I have forgotten the password to my ipad & dnt have a way to connect to itunes or a pc .... What do I do know ??

  • Itunes doesnt detect music, even though the file wasnt moved or changed

    hi guys my itunes is annoying the **** out of me.... for some reason i get teh exclamation point next to my song files even though i never changed or move the actual song file.... is it because i have too many songs in the folder? is there like a pro

  • Is Java 100% Object Oriented?

    Is java 100% pure OOP? I said no.. the reason is we can use primitive data types(which is not a object)also....and also static method which can be accessed without creating objects...Hope u understood my problem. Can anyone give clear idea about this

  • CHANGE THE OUTPUT MEDIUM FOR SRM PURCHASE ORDERS

    We are using SRM 5.0 I tried to change the SRM purchase order's output medium from 'XML' to 'Print' using a function module 'BBP_OUTPUT_PO_PARAMS_SET' within the BADI 'BBP_ECS_PO_OUT_BADI'. Though it changes the output medium and chooses the right ra