4 Replies Latest reply on Dec 15, 2015 8:09 AM by OwenLR

    updating to cc lightroom


      I am about to update to the CC LR and have a few questions.


      My current setup is as follows:


      1) I'm on a mac

      2) My master LR catalog lives on an external SSD. When I travel I take the catalog with me as needed to access/reference files


      When i go to update my master catalog, will it need to be re-written? And once this is done will I be able to open it on my laptop which also has CC on it?


      Do I need to have room somewhere to rewrite the entire catalog?




        • 1. Re: updating to cc lightroom
          dj_paige Level 9

          The catalog file will be copied and the copy will be converted to Lightroom CC 2015 format. So, yes, you will need the space on your external SSD. This new catalog file can be opened on any computer that has Lightroom CC 2015 installed.


          The photos are not touched, so they will take up the same amount of space as before.

          • 2. Re: updating to cc lightroom
            OwenLR Level 1

            thank you for the quick reply.


            one last question. I'm assuming during this process i will be asked where to save the new catalog? My catalog is about 600gb so i'm juggling space to copy/save/move, etc..



            • 3. Re: updating to cc lightroom
              dj_paige Level 9

              Sorry, I tried to make this clear, but apparently not.


              Your catalog file is what will be converted, this may be a few gigabytes at most. No, you do not get asked where to save the new catalog.


              Your photos (which make up the bulk of the 600gb and are not technically part of the catalog) will not change or be copied/duplicated, you will not need another 600gb, you will not need even a single extra byte for your photos.

              • 4. Re: updating to cc lightroom
                OwenLR Level 1

                Ok, got it. So it basically 'converts' the catalog in place. I have it backed up should anything go wrong. So this seems straight forward.


                thanks again.