How to free space with new LR 14.4 Classic Denoise (non-destructive, non-DNG)?

• It's non-destructive.
• You can adjust its "intensity" on the fly.
• You don't get DNG duplicates.
• And much MUCH more important: overall it takes about 10% at most of the former disk storage. It'll depend on the exact case but, as example, in my Sony a6700 38 denoised enhanced DNGs took 2.5 GB but now those very same pictures take a bit less than extra 200 MB on the *.lrcat-data folder.

ARSPR said:

But there's a catch or something I don't know how to do. If I wanted to free up space because I don't need that denoised pictures anymore, well I just can delete their huge DNGs. But I can't find a way to free the *.lrcat-data folder.

I mean, I've "cleared history above xxx" (just before the new denoise was applied), I've "optimized catalog" and *.lrcat-data folder is still the very same. More over, if I re-denoise it grows bigger...

Click to expand...

dj_paige said:

If you remove the photo from LrC, the program should also remove data from that photo from lrcat-data. Of course, this removes all of your edits for that photo from LrC.

Click to expand...

bakubo said:

ARSPR said:

But there's a catch or something I don't know how to do. If I wanted to free up space because I don't need that denoised pictures anymore, well I just can delete their huge DNGs. But I can't find a way to free the *.lrcat-data folder.

I mean, I've "cleared history above xxx" (just before the new denoise was applied), I've "optimized catalog" and *.lrcat-data folder is still the very same. More over, if I re-denoise it grows bigger...

Click to expand...

I do not know if this will remove the no longer used ADAI data, but you can try it. Create a virtual copy of the photo and use ADAI on it. Then delete the virtual copy and see if the ADAI data seems to be removed from *.lrcat-data.

I think there should be an option to do it the old way and create a DNG.

Click to expand...

Zeee said:

To add to the few comments from other members. There is no way for you to free you to free up catalogue space manually but there is one important part about that.

-The catalogue is just a database so it won't be very big thus not a real concern.

-There is no known limit to the size of the catalogue. The biggest I have read so far was for about 13 million files.

- Getting rid of the DNGs will be a bit of work. If you do this using your OS LrC will lose track of them and you will the ! beside every file. I would suggest to use the metadata option in the Library page to locate and delete them using LrC. You can try this with all the files or in groups or by years. I've not done this personally but you just gave me an idea. I decided to leave all my DNG's alone but I may change my mind. I can't try this for about a week. I'm traveling with a new travel catalogue so I will have no DNG's to try and delete. Besides I'd rather do this at home in my own cave.

Click to expand...

• I've made a small test going back in the "History" to the step just before applying the new AI Denoise.
• I've "Right Click on that previous step -> Clear History Above this Step" so the Denoise step is definitely gone.
• Just in case, I've "File->Optimize Catalog..."
• I've closed LrC
• And *.lrcat-data folder keeps the same size. Therefore it somehow contains "rubbish": it contains the AI data for an AI operation not needed anymore.
• Moreover, I've re-opened LrC and I've re-Denoised that very same picture and two things happen:
• 1) Denoise calculation is done again. So yes, whatever AI data remained stored in *.lrcat-data are in fact "rubbish"...
• 2) *.lrcat-data folder actually grows bigger again...

Zeee said:

-Once you have done that exit LrC and make sure the Check Integrity and Optimize Catalogue boxes are checked. This will reset the catalogue to what files you are actually using and should reduce inbound size.

Click to expand...

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

Zeee said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

Zeee said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

ARSPR said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

ARSPR said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

buildingsights said:

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

buildingsights said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

buildingsights said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

i thought that when you 'optimise' your catalogue, you 'defrag' it, it gets condensed and reorganised to function more efficiently...

Click to expand...

buildingsights said:

(the use of the xmp file is handy, even if you only work in LR... e.g. as a backup or to share your edits of the raw file with friends or colleagues)

Click to expand...

ARSPR said:

bakubo said:

ARSPR said:

But there's a catch or something I don't know how to do. If I wanted to free up space because I don't need that denoised pictures anymore, well I just can delete their huge DNGs. But I can't find a way to free the *.lrcat-data folder.

I mean, I've "cleared history above xxx" (just before the new denoise was applied), I've "optimized catalog" and *.lrcat-data folder is still the very same. More over, if I re-denoise it grows bigger...

Click to expand...

I do not know if this will remove the no longer used ADAI data, but you can try it. Create a virtual copy of the photo and use ADAI on it. Then delete the virtual copy and see if the ADAI data seems to be removed from *.lrcat-data.

I think there should be an option to do it the old way and create a DNG.

Click to expand...

Thanks for the tip, but it would be suboptimal. One of the reasons the new behaviour is great is that the dng/original raw duplicity is gone for good. A virtual copy as a workaround would be somehow the very same duplicity...

Click to expand...

ARSPR said:

buildingsights said:

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

ARSPR said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

ARSPR said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

i thought that when you 'optimise' your catalogue, you 'defrag' it, it gets condensed and reorganised to function more efficiently...

Click to expand...

Sure, that was what I thought and how I'd expect it to work both within the *.lrcat part and the *.lrcat-data one. But either it doesn't seem to be the case, (I mean it's a bug/missing feature), or I'm doing something wrong...

Click to expand...

ARSPR said:

ARSPR said:

(the use of the xmp file is handy, even if you only work in LR... e.g. as a backup or to share your edits of the raw file with friends or colleagues)

Click to expand...

Sure, everything has its usage in the proper conditions. It's just not my case. I'm not a pro but an amateur and my friends only need final jpgs, (even WhatsApp ultra-compressed ones). They'd get quite nervous with raw and xmp files...

Click to expand...

buildingsights said:

ARSPR said:

buildingsights said:

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

buildingsights said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

buildingsights said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

i thought that when you 'optimise' your catalogue, you 'defrag' it, it gets condensed and reorganised to function more efficiently...

Click to expand...

Sure, that was what I thought and how I'd expect it to work both within the *.lrcat part and the *.lrcat-data one. But either it doesn't seem to be the case, (I mean it's a bug/missing feature), or I'm doing something wrong...

Click to expand...

I thought that when you select 'optimise', LR does its thing without intervention from the user. is there something in particular where you think it might be going wrong?

buildingsights said:

buildingsights said:

(the use of the xmp file is handy, even if you only work in LR... e.g. as a backup or to share your edits of the raw file with friends or colleagues)

Click to expand...

Sure, everything has its usage in the proper conditions. It's just not my case. I'm not a pro but an amateur and my friends only need final jpgs, (even WhatsApp ultra-compressed ones). They'd get quite nervous with raw and xmp files...

Click to expand...

i should try that with some of my friends less into the arcane mysteries of LR and video their reaction at the mere thought of my sending them raw and xmp files!

Click to expand...

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

ARSPR said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

ARSPR said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Click to expand...

ARSPR said:

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

Click to expand...

ARSPR said:

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

buildingsights said:

buildingsights said:

ARSPR said:

buildingsights said:

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

buildingsights said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

buildingsights said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

i thought that when you 'optimise' your catalogue, you 'defrag' it, it gets condensed and reorganised to function more efficiently...

Click to expand...

Sure, that was what I thought and how I'd expect it to work both within the *.lrcat part and the *.lrcat-data one. But either it doesn't seem to be the case, (I mean it's a bug/missing feature), or I'm doing something wrong...

Click to expand...

I thought that when you select 'optimise', LR does its thing without intervention from the user. is there something in particular where you think it might be going wrong?

buildingsights said:

buildingsights said:

(the use of the xmp file is handy, even if you only work in LR... e.g. as a backup or to share your edits of the raw file with friends or colleagues)

Click to expand...

Sure, everything has its usage in the proper conditions. It's just not my case. I'm not a pro but an amateur and my friends only need final jpgs, (even WhatsApp ultra-compressed ones). They'd get quite nervous with raw and xmp files...

Click to expand...

i should try that with some of my friends less into the arcane mysteries of LR and video their reaction at the mere thought of my sending them raw and xmp files!

Click to expand...

.
just another thought... when you have finished your editing, and after exporting the raw to jpg, tiiff, psd... and if you are sure that you don't need the 'history' steps any more .. you could first make a 'Snapshot' (or several) of different stages of your editing, and then go back to the beginning of the 'history' and right-click on it, and select 'Clear History Above This Step' (which could be at any step you choose in the history list). i would imagine that all these steps will be marked as deleted, and they will be gone at the next optimisation of the cataloque...

Click to expand...

Zeee said:

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

Zeee said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

Zeee said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Click to expand...

Correct about the data. Still in the world where TB storage is common still is not that much to me. But that is just me.

Zeee said:

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

Click to expand...

Yes

Zeee said:

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

I’m not but suspect optimizing the catalogue does this.

Click to expand...

Zeee said:

buildingsights said:

buildingsights said:

ARSPR said:

buildingsights said:

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

Zeee said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

Zeee said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

i thought that when you 'optimise' your catalogue, you 'defrag' it, it gets condensed and reorganised to function more efficiently...

Click to expand...

Sure, that was what I thought and how I'd expect it to work both within the *.lrcat part and the *.lrcat-data one. But either it doesn't seem to be the case, (I mean it's a bug/missing feature), or I'm doing something wrong...

Click to expand...

I thought that when you select 'optimise', LR does its thing without intervention from the user. is there something in particular where you think it might be going wrong?

Zeee said:

Zeee said:

(the use of the xmp file is handy, even if you only work in LR... e.g. as a backup or to share your edits of the raw file with friends or colleagues)

Click to expand...

Sure, everything has its usage in the proper conditions. It's just not my case. I'm not a pro but an amateur and my friends only need final jpgs, (even WhatsApp ultra-compressed ones). They'd get quite nervous with raw and xmp files...

Click to expand...

i should try that with some of my friends less into the arcane mysteries of LR and video their reaction at the mere thought of my sending them raw and xmp files!

Click to expand...

.
just another thought... when you have finished your editing, and after exporting the raw to jpg, tiiff, psd... and if you are sure that you don't need the 'history' steps any more .. you could first make a 'Snapshot' (or several) of different stages of your editing, and then go back to the beginning of the 'history' and right-click on it, and select 'Clear History Above This Step' (which could be at any step you choose in the history list). i would imagine that all these steps will be marked as deleted, and they will be gone at the next optimisation of the cataloque...

Click to expand...

That has been recommended but I don’t see the point. Even with the cat and data files combined it’s not that much IMO.

Now with no need for DNG’s even better. The Previews is the thing that chomps up space. I’d be concentrating there for space savings.

Click to expand...

Zeee said:

buildingsights said:

buildingsights said:

ARSPR said:

buildingsights said:

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

Zeee said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

Zeee said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

i thought that when you 'optimise' your catalogue, you 'defrag' it, it gets condensed and reorganised to function more efficiently...

Click to expand...

Sure, that was what I thought and how I'd expect it to work both within the *.lrcat part and the *.lrcat-data one. But either it doesn't seem to be the case, (I mean it's a bug/missing feature), or I'm doing something wrong...

Click to expand...

I thought that when you select 'optimise', LR does its thing without intervention from the user. is there something in particular where you think it might be going wrong?

Zeee said:

Zeee said:

(the use of the xmp file is handy, even if you only work in LR... e.g. as a backup or to share your edits of the raw file with friends or colleagues)

Click to expand...

Sure, everything has its usage in the proper conditions. It's just not my case. I'm not a pro but an amateur and my friends only need final jpgs, (even WhatsApp ultra-compressed ones). They'd get quite nervous with raw and xmp files...

Click to expand...

i should try that with some of my friends less into the arcane mysteries of LR and video their reaction at the mere thought of my sending them raw and xmp files!

Click to expand...

.
just another thought... when you have finished your editing, and after exporting the raw to jpg, tiiff, psd... and if you are sure that you don't need the 'history' steps any more .. you could first make a 'Snapshot' (or several) of different stages of your editing, and then go back to the beginning of the 'history' and right-click on it, and select 'Clear History Above This Step' (which could be at any step you choose in the history list). i would imagine that all these steps will be marked as deleted, and they will be gone at the next optimisation of the cataloque...

Click to expand...

That has been recommended but I don’t see the point. Even with the cat and data files combined it’s not that much IMO.

Click to expand...

Zeee said:

Now with no need for DNG’s even better. The Previews is the thing that chomps up space. I’d be concentrating there for space savings.

Click to expand...

buildingsights said:

Zeee said:

buildingsights said:

buildingsights said:

ARSPR said:

buildingsights said:

ARSPR said:

Zeee said:

There is a thread going on about to xmp or not to. Just in case xmp are sidecars that have nothing to do with the catalogue. Those can be deleted using the OS.

Click to expand...

I don't use xmps as I only work within LrC.

buildingsights said:

DNG file data is added to the catalogue. Deleting those using the OS will cause the LrC to lose track of them and the ! (exclamation warning) will come up.

Click to expand...

See my answer to your former post. Never ever delete "catalogued" files (jpgs, raws, dngs) outside LrC. Do it INSIDE LrC to keep everything correctly synced.

buildingsights said:

Just in case for others. Your files including both RAW and DNG are not the catalogue. They are just normal files. The catalogue is a separate database which I often call a spreadsheet on steroids This makes it the smallest thing occupying storage space. So small it's almost insignificant. To manually delete anything would require coding which I would not recommend. Best just to delete files using LrC and later just restart it and optimize the catalogue.

Click to expand...

*.lrcat is in fact almost insignificant, but AI calculated data are not. In fact my current *.lrcat-data folder is quite new, (as every single one in the world ;-) ), while my catalog started in 2008 and, right now, *.lrcat is 340 MB but *.lrcat-data is 985 MB.

Nevertheless, storing calculated AI data inside *.lrcat-data is much more efficient than DUPLICATING the pictures as DNGs...

And, again, I don't want to delete the pictures, I want to delete the AI Data when, for whatever reason, they're not needed anymore. But seeing the behaviour I've started this thread with, and playing devil's advocate, are you sure when you delete a picture LrC does in fact delete its associated AI data from *.lrcat-data folder? or is it kept as more rubbish inside it?

Click to expand...

i thought that when you 'optimise' your catalogue, you 'defrag' it, it gets condensed and reorganised to function more efficiently...

Click to expand...

Sure, that was what I thought and how I'd expect it to work both within the *.lrcat part and the *.lrcat-data one. But either it doesn't seem to be the case, (I mean it's a bug/missing feature), or I'm doing something wrong...

Click to expand...

I thought that when you select 'optimise', LR does its thing without intervention from the user. is there something in particular where you think it might be going wrong?

buildingsights said:

buildingsights said:

(the use of the xmp file is handy, even if you only work in LR... e.g. as a backup or to share your edits of the raw file with friends or colleagues)

Click to expand...

Sure, everything has its usage in the proper conditions. It's just not my case. I'm not a pro but an amateur and my friends only need final jpgs, (even WhatsApp ultra-compressed ones). They'd get quite nervous with raw and xmp files...

Click to expand...

i should try that with some of my friends less into the arcane mysteries of LR and video their reaction at the mere thought of my sending them raw and xmp files!

Click to expand...

.
just another thought... when you have finished your editing, and after exporting the raw to jpg, tiiff, psd... and if you are sure that you don't need the 'history' steps any more .. you could first make a 'Snapshot' (or several) of different stages of your editing, and then go back to the beginning of the 'history' and right-click on it, and select 'Clear History Above This Step' (which could be at any step you choose in the history list). i would imagine that all these steps will be marked as deleted, and they will be gone at the next optimisation of the cataloque...

Click to expand...

That has been recommended but I don’t see the point. Even with the cat and data files combined it’s not that much IMO.

Click to expand...

sure. if you keep your catalogue optimised it shouldn't be any problem with the sizee...

buildingsights said:

Now with no need for DNG’s even better. The Previews is the thing that chomps up space. I’d be concentrating there for space savings.

Click to expand...

deleting previews wouldn't reduce the size of the .lrcat itself.

Click to expand...

buildingsights said:

previews can be set to be deleted automatically by LR every week, month...

Click to expand...