jcboy3

I got back late from a concert I shot, but I wanted to see the pics so I loaded them into Lightroom, did a preliminary scan/delete, and then went to rename the files. And noticed that the rename was taking a long time, so I checked the status bar and it was busily renaming thousands of files.

I got caught by the notorious Lightroom feature that you cannot delete files from disk when looking at them in a collection, so you have to be in "All Photographs". After deleting files, I did not go back to the collection but selected all and renamed.

Gasp. This wiped out a lot of work renaming files with model and performer name included. This would take forever to fix.

So I reloaded from my last backup, and then corrected what I had done since then, and voila...back in business. I had to back up both the photos folder and Lightroom catalog folder, which I back up at the same time.

So remember, boys and girls, always be safe and backup regularly.

Bill_de Loc: US

We all know that ...

... but can never be reminded too many times.

Thanks!

--

JD750 Loc: SoCal

Jcboy3 glad that it ended well good thing you had the backups.

I don't know what your state was but I can guarantee that if I got back from a concert late I would not be in a state to tangle with Lightroom! :?

PixelStan77 Loc: Vermont/Chicago

:thumbup: :thumbup: :thumbup:

Billyspad Loc: The Philippines

Another good reason to steer clear of Lightroom is what I read here.
So if you make a simple human error it renames all your photos for you huh.

And folks actually PAY for LR?

Pandylou Loc: The Levant

:thumbup: :thumbup: :thumbup:
Expect a visit from the "Adobe Fanbois" cavalry - I can hear them galloping up already :D

jerryc41 Loc: Catskill Mts of NY

I've had a similar thing happen when exporting from LR. I'll export an image and name it 118. After a few minutes, I see that it's still exporting. I had all files in the strip at the bottom highlighted, so it was exporting 118-1, 118-2, etc. It's easy enough to correct, but a stupid mistake top make.

Yes, I love backups.

Billyspad Loc: The Philippines

Bring em on I laugh at em when they sing the praises of shite badly written software. Love it when they say how good subscription package is cos you get updates huh. Ya know if you update shite you get a newer version of shite. Same colour consistency and smell just fresher

dcampbell52 Loc: Clearwater Fl

Yep, it only takes one really big ah oh to get the point across. I had mine years ago so I am an early member of the backup bandwagon. I have 3 complete backups that I rotate to a safe deposit box off site plus one that is on my WD Cloud drive group so I can get to it from the field.

And I do NOT use DVDs or CDs. I have external multi-terabyte hard drives that I can plug into an attached network hard drive enclosure, copy my lightroom backups to them, store the current one in house until time to move it off site. Remember that you want your off site backup to be NO OLDER than you can afford to loose if you were to have to recover from a disaster. (Like the tornado that was 2 blocks away from the house day before yesterday, no damage but close enough to make me revisit my backup schedule). If you can afford to, at worst case, loose 1 weeks work completely, then you need to move you offsite weekly, if you can't afford that then you adjust accordingly. Also, if you really need to, you can use some of the offsite cloud backups to shorten your backup time. But, you pay for the size of your offsite backup cloud so I generally keep it purged to ONLY the last week or so of work until I can get those images into my long term offsite backup at the bank. Also make sure that you choose a safe deposit box location that is somewhat removed from where your studio is. Don't use the bank across the street because if the tornado, hurricane, whatever gets your studio, it possibly will get the bank (and it's vault) too. This doesn't mean the bank vault is bad, it just means that if the bank is destroyed in the same event that your studio is, you will have to wait to recover your backups.

Capture48 Loc: Arizona

I find it laughable that you blame Adobe or any program for that matter for human stupidity. Do you know of any other program that when you do a CTRL+A will decide that the user does not really want me to select all? I'll select only some of the files!

Capture48 Loc: Arizona

No you do not have to be in "All Photographs" to delete, or rename or do anything. Unless of course you import to this one single folder for every image in your catalog. Further it won't rename all or delete all unless you select all. This is simple human error, but very glad you had backups!

jcboy3

Yes, that is true. You can work in the folders panel, and then you can delete files. I often have images from multiple cameras; I keep them separated in my folders but combine them in collections. So I work in the collections panel. And you cannot delete files from the collections panel, you can only remove them from the collection or catalog. So then I go to "All Photographs" to delete files.

And it is the limitation that you can't delete a file from the collections panel that is the issue.

Capture48 Loc: Arizona

You can't delete from a collection because the actual photo does not exist there. The program did not duplicate your photo when you added it to the collection, it simply added a pointer to the photo. Does it make sense that you can't permanently delete a photo from a place where it does not exist? I think so, but you can debate that.

revhen Loc: By the beautiful Hudson

Shite happens. Like the time my computer and its hard drive completely broke down and I had to get a new one. Thousands of pictures and important document files GONE. Except I had invested in Carbonite cloud backup. It took several days to download but I got it all back. Whew!

kd7eir Loc: Tucson, AZ

It makes zero sense that you cannot delete a file via a pointer to that file. It's lazy programming plain and simple. Since the collection knows where to find that file based upon the pointer that it created, it can easily perform any file action on that photo. This is not a feature, it's called crap programming.

BTW - EVERY TIME you click on a filename on a computer, you are clicking on a POINTER FILE. That filename is NOT the file, it's a pointer that says "Go to this sector and read the xxx bytes back." Based upon this REALITY of computer science, Adobe's decision to not allow deleting files from a collection is pure BS.