Revel: Nuking iPhoto duplicates

  • 3
  • Problem
  • Updated 6 years ago
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: Revel - Transition | End of Service

My photos have been pretty disorganized after trying to escape iPhoto (and its crazy way of placing pictures in multiple directories). Adding pictures to Revel, I'm bringing together several collections, and I expect there to be duplicates. Importing my iPhoto DB has brought in *lots* of new duplicates.

By lots I mean sometimes 5 copies of the same picture. When I open the Revel DB package and go to that date's directory, I find IMG4332.jpg, IMG4332-2.jpg, IMG4332-3.jpg and so forth. With moving files between computers and so forth, I can understand how a checksum might see these as different files. But the image name should be a tip off. Revel should be able to ask me if these files are duplicates.

Deleting these duplicates is painful. Within the app, just forget it. You can't select files from the carousel. You have to go in each picture screen to delete it, which is incredibly slow. Duplicates are much easier to identify in the package directories. When I delete duplicates there, the files are still shown in the carousel when I relaunch Revel. How do I delete duplicates so that they stay gone without crawling through the carousels?
Photo of fishpatrol


  • 10 Posts
  • 1 Reply Like

Posted 7 years ago

  • 3
Photo of Steve Ratcliffe

Steve Ratcliffe

  • 27 Posts
  • 2 Reply Likes
Hi Fishpatrol,

I had exactly this issue and like you I was disappointed that Revel's checksum detecting routine couldn't spot the duplicates when I consolidated several libraries.

However it isn't as hard as you think to delete individual files as long as you are using the latest version of Revel on your mac (v1.2).

I tend to do this one event or date at a time by pressing the grid icon (or by dragging a strip to the right from the first photo) to show all the photos from a date or event in "Grid View". You can then click the Action icon in the top right corner to enter "Multi Select mode". Just click on a photo to "tick" it and then hit the delete button in the bottom right corner. All ticked photos will be deleted in one go.

Best of luck.
Photo of Steve Ratcliffe

Steve Ratcliffe

  • 27 Posts
  • 2 Reply Likes
In answer to your other question of how to lose these deleted photos from your local store of photos, I wasn't aware that if you use "Keep originals" they are not deleted from your mac when you delete them from Carousel but one sure fire way of getting rid of them is to delete the local store. You can do this by deleting the Revel file from your Pictures directory. You may also need to clear the cache files and there are other posts in this forum which can help with that.

Of course this means that you will have to download them from the cloud again which isn't ideal as "Keep Originals" is suggested to ensure you have a backup.
Photo of Jason R

Jason R, Employee

  • 241 Posts
  • 9 Reply Likes

Steve gives the best pointers for deleting a range of multiple photos.

Could the duplicates you are seeing be from edits made in iPhoto? It's not exactly clear to me if you are opening the iPhoto package in finder and dragging folders to Revel from there or dragging photos from the open application user interface of iPhoto.

Also when you delete a photo from within the Revel user interface (rather than our package data) we do mark the file as deleted so you can't mistakenly re-import it.

Another tidbit of info. Revel does not rely on file name to determine if an image is a duplicate. In fact you may import different files with identical names from different folders. We do parse the image to assure the contents are not already in existence in the Carousel. There are some outside cases where the files system data will cast enough doubt that we will bring in a file that could be considered a duplicate visually by the user.

Photo of fishpatrol


  • 10 Posts
  • 1 Reply Like
Thanks for the replies, everyone. Jason, I was adding iPhoto images by hitting the plus sign and using the "Import Photos" dialogue box to select the iPhoto package file in the Finder. That's when the duplicates piled up.

I'm glad that Revel doesn't only rely on file name to identify duplicates. But as a non-pro photographer, I've only used a handful of cameras in the past ten years. Maybe they've all been different brands, but none have used the exact same naming conventions. So I think I'm less likely to have several IMG4332.jpg files that are non-duplicates.

Identifying these duplicates would be a lot easier if Revel could display the file name. I wouldn't want to see it usually, but it would be nice to see in Grid View. (Thanks for pointing that out, Steve.) I can see I'll have to delete all duplicates within the app to ace them in the cloud, too. That makes sense too, but I think it points out that the desktop app needs to have more robust management tools.

It looks like one of the "days" in Revel has 519 pictures that are thumbnails from iPhoto. How do I know what those photos are? I can't see their dimensions, can I? They include pictures that were taken months apart. What a mess.
Photo of elholtu


  • 1 Post
  • 0 Reply Likes
I want to be sure I understand. When I first imported files into Revel this year (using Revel in my browser), it notified me when it found dupes and would not import them. However, I recently imported a folder of pictures using the Revel application on my iMac knowing there would be some dupes and assuming Revel would again spot them. It doesn't seem to have noticed the dupes this time. Will Revel just keep importing more and more copies of the same photos if I do not carefully make sure that I only select for import to Revel only photos that have not been imported earlier?
Photo of Peter Baust

Peter Baust, Official Rep

  • 388 Posts
  • 43 Reply Likes
Revel currently only detects exact duplicates. The files coming from iPhoto were likely downsized versions of the originals, which are not considered duplicates, though of course, they look the same until you zoom.

We are considering adding detection for the downsized case as well, though it may require manual intervention to avoid false positives.

This conversation is no longer open for comments or replies.