Where does iPhoto store imported photos?

iPhoto has been uninstalled from my Mac. Besides iTunes, it is the most frustrating app on my Mac.

Yes, these apps can take a little figuring out.

Have you watched the tutorials? There is a learning curve for new software. The tutorials will save a lot of frustration

LN

I use Iphoto in the following way.

I always drag photos from my SD cards using Finder into "proper" folders under Pictures in the file structure. My iphoto never sees my SD card!

I then go into iphoto and "import into library". Iphoto then uses the folder names as "events" - so far so good.

If the folder has been imported before, because I have only added photos to the existing folder, iphoto decides annoyingly to create another event of the same name. I then highlight the two events, right click and hit Merge Events. BAck to one event = one real folder.

If I use iphoto to make small corrective edits, I always immediately Export the "Current" version back to the proper folder in the file system with a suffix. That way I don't have to worry about where the heck iphoto has stored the edited version.

If I use Photoshop I always do it outside iphoto and import the subsequent version as above.

If I get tired of the wasted space in the iphoto library I find it and delete it, then import the whole folder structure fresh into iphoto. Cooks the CPU but no harm done.

As you may guess I am ex Windows (aren't we all) and I absolutely hate the way iphoto, Aperture and Photoshop try to catalogue my versions in an obscure place that Finder has a job to find!

OK I am not a believer, sorry, but iphoto has some nice viewing capability it's just not going to take over my filing system.

By the way I unticked that Importing [] Copy to the iphoto library option in Advanced prefs.

Well you really would be much happier using another app. All that you are doing is making extra work for yourself.

Why on earth would you bother doing that? Why not use some other app that works they way you want to work.

Honestly, that workflow makes as much sense as driving from New York to Chicago via Miami, simply because you happen to have a map of Miami.

Again, if you cannot manage to distinguish between a file and the data it contains, then don't use a database.

The whole problem is storing large amounts of binary data in a database is not efficient. It started as a great idea but it’s still better to store a pointer to the actual file. Thus using a database for its actual intent of how you should store data.

A file system is for storing files that contain data, a data base is for storing data not a file. Die hard Apple users what to blur the lines on data vers files by calling it containers.

"Here comes all the defensive replies on that comment."

Yes they are correct in the aspect of describing the difference, but it’s a matter how to efficiently store your collection. If you do any Database administration or development you will understand that it’s not the ideal way to deal with that kind of data if you have a large volume of photos..

Peter I understand why you are doing the style workflow, but it is a lot of work for sure. I would use another package.

Never looked inside the Library package then?

I was merely offering an alternative method to address the original question in a lateral way by controlling manually where imported photos are stored, which does not take any more time or effort despite the lengthy description. I daresay if you described how you you use iphoto in standard configuration it would take the same number of lines of text, but my method does retain complete control in MY hands not iphoto. My work is in my Mac in my folder structure.

The reason I use iphoto is that unlike windows there is no other native viewing method which does not involve contortions for non mac users (the wife), and please don't say using Preview or hitting the space bar in Finder is an alternative because they all have serious flaws in the way they navigate through a collection of 10,000 pictures. IPhoto does a good job of presentation, so I will continue using it, thanks.

iPhoto is not a "native" (whatever that is) viewing method. It's a Databse driven photo manager.

You have Photoshop? Never heard of Bridge? There are hundreds of Image Viewers for the Mac. Hundreds. Check them out sometime. Save yourself a lot of time.

Regards

TD

There are indeed a few in App Store, about 20, and those which have any reviews seem to indicate they are Finder based which proves my point that Finder/preview is poor compared to Explorer.

I have Photoshop and Premiere Elements, (I'm not made of money!) so Bridge is not available. Elements Organiser has an even more fragile catalog.

A database is just a storage mechanism coupled to a catalog or index. Good systems allow you to select your preferred physical storage location. I use iphoto's index but with the standard filesystem of the Mac.

Whatever. It's not an image viewer but you'll twist yourself into all sort of odd positions to try and use it like one. Makes a much sense as writing a novel in Photoshop - somehow possible, but rather pointless when you consider the tools out there designed for the job.

iPhoto does allow you to choose where you store your files - you have unchecked the option to copy the files into the Library package, haven't you? I don't recommend it for many reasons, but there you go. It's the rest of the carry on that makes no sense:

If the folder has been imported before, because I have only added photos to the existing folder, iphoto decides annoyingly to create another event of the same name. I then highlight the two events, right click and hit Merge Events. BAck to one event = one real folder.

If I use Photoshop I always do it outside iphoto and import the subsequent version as above.

If I get tired of the wasted space in the iphoto library I find it and delete it, then import the whole folder structure fresh into iphoto. Cooks the CPU but no harm done.

Let me give you one small tip: If you export as current then you're losing metadata.

Regards

TD

If the folder has been imported before, because I have only added photos to the existing folder, iphoto decides annoyingly to create another event of the same name. I then highlight the two events, right click and hit Merge Events. BAck to one event = one real folder.

If I use Photoshop I always do it outside iphoto and import the subsequent version as above.

If I get tired of the wasted space in the iphoto library I find it and delete it, then import the whole folder structure fresh into iphoto. Cooks the CPU but no harm done.

To explain, The first point is that iphoto is behaving badly (IMHO) creating another event of the same name but with a date qualifier so it makes sense for ME to merge them. If you want iphoto to control your life events as it chooses then ignore the method.

Second point is that my serious edits would be done in RAW and resultant jpgs can be imported after editing. Again this allows me to keep my separate RAW 'negative' files separately. The 'Edit in external editor' option is very slow and has hung my mac several times with the wheel of death.

Final point is, as you will see from many previous posts, when these databases screw up their index they tend to trash your photos. Having an index that can be recreated from the master filesystem rather than a filesystem that is created from the index, the index is disposable and cannot screw up your photo collection.

Yes of course editing any jpeg will lose some metadata every time it is saved. It's a flaw in the jpeg compression The 'current version' held in iphoto has already lost its metadata (it is saved as a jpg in iphoto library) and exporting it does not make it any worse. Also if exported with a suffix a,b,c all versions are available in the mac fielsystem. Exif data is preserved.

The first point is that iphoto is behaving badly (IMHO) creating another event of the same name but with a date qualifier so it makes sense for ME to merge them. If you want iphoto to control your life events as it chooses then ignore the method.

iPhoto creates a new Event for each import. You perhaps might like to investigate the other options for organising in iPhoto. Events are organisation for those who can't really be bothered. They are automatic - based entirely on Date and Time the camera records the photos as taken.

If you're going to use iPhoto - and you shouldn't, really - then you should investigate the other more powerful options it presents: Albums, Smart Albums keywording and so on.

Second point is that my serious edits would be done in RAW and resultant jpgs can be imported after editing. Again this allows me to keep my separate RAW 'negative' files separately. The 'Edit in external editor' option is very slow and has hung my mac several times with the wheel of death.

iPhoto preserves the Original file untouched in every operation. You can always revert to the original file.

Final point is, as you will see from many previous posts, when these databases screw up their index they tend to trash your photos.

Well, if you actually read the posts and not the alarming titles you'll see that no, when the database goes west they don't trash your Photos. The catalogue is damaged but the files are perfectly fine. You do realise they are just stored in folders in the Finder, right?

Plus, like any data on any computer, the simple and surefire protection against this is an up-to-date back up. Your actual photos are at much greater risk from a HD failure than an iPhoto database one.

Yes of course editing any jpeg will lose some metadata every time it is saved. It's a flaw in the jpeg compression The 'current version' held in iphoto has already lost its metadata (it is saved as a jpg in iphoto library) and exporting it does not make it any worse. Also if exported with a suffix a,b,c all versions are available in the mac fielsystem. Exif data is preserved.

No, when editing a Jpeg no metadata is lost. Data will be due to the compressions system, but no, exporting as current does not preserve all the Exif metadata.

iPhoto is about lossless editing of Photos.

I regularly sit down at Windows machines and I find then confusing and difficult to use. But I don't assume that the problem is with Windows. If I'm going to use this machine for a task then I need to learn how the designers intended that task to be accomplished. I invariably find that when I do, then their workflow makes a lot of sense. I don't assume that the designers are wrong. I assume that they are quite bright people. If the app suggested to me for a job doesn't suit, I go look for one that does the job that I want done.

You choose to work the way you want. You're a grown up. But your system is pointlessly complex, lossy and based on a misunderstanding of what iPhoto is, how it works and what it's for. If you took a few moments to explore the app you might find that it can actually do what you are trying to achieve and do it more easily than you're doing right now.

Regards

TD

I disagree with all the technical statements in your reply and there is no point in arguing further.

Yes of course editing any jpeg will lose some metadata every time it is saved.

You still think that statement is true? Or this

iPhoto preserves the Original file untouched in every operation. You can always revert to the original file.

is untrue?