Terence Devlin wrote:
I would be very nervous having my entire library of years of photos sitting in one big db file.
It's not a file. It's special kind of folder called a Package. It presents in the Finder as single object but it's not. Want a look inside? Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed. There are all your files, arranged in folders. It's a simple protection against inexpereinced users damaging the library inadvertently.
I know that, but I assumed that if that folder becomes corrupted, then the whole db is problematic compared to just losing a file or two when stored in a more 'conventional' structure. Thanks for reassuring me that is not the case.
There's no more to corrupt than any folder tree.
See above. Very reassuring.
Are you really comparing a software system that costs in the region of $1,000 with a $15 app? Seriously?
No I'm not. Just giving a reason for liking a particular workflow. No dig at iPhoto intended or given.
No you don't actually. What you have is a collection of files in folders. But those files are not your photos. They're just containers for your Photos. It mkes as much sense organising your photos by the files that contain them as organising a shoe store by the colour of the boxes. The point is the shoes not the boxes.
I'll use the term files in future!
With iPhoto, you're working with the Photos, not the files - it's that dumb storage thing again. (Same with LR, incidentally). With iPhoto all edits are non destructive, and, using the external editor set up, iPhoto and Photoshop can "see" the edited versions too.
Using the external editor set up with Photoshop, where does PS store the files/photos when you do a 'save as'? Back into the iPhoto library? Are you saying that PS and iPhoto can see each others edits like LR and PS? Hmmm.
One single object to back up gets everything. Originals, edits, metadata, orgnisation etc etc etc How is having multiple objects to back up easier?
Because, if I make one change to a photo, Time Machine will back up that small xmp file, but I assumed (rightly or wrongly) that it would backup the entire iPhoto library file unless it is clever enough to know changes within the package. (Same sort of problem with VMs like Parallels, one small change makes TM backup the whole huge VM file.)
Neither would you have two copies with a Managed Library either. So, your point is?
Sorry, I obviously misunderstood. I was under the impression that with a Managed library, a copy of the files was made to iPhoto library and the original files wre left untouched in their original locations.
As to deletions: If you run a referenced library you are responsible for file management. So, manage the files, it's what you have a jones for. That's why I advocate a Manged Library.
Still, the fact is as I understand it, that you cannot delete a file within iPhoto. LR (sorry to make the comparison) and iTunes, for example, asks if you want to delete the photo from the hard disk as well as the library.
Only trying to understand some more, that's all. No criticism of iPhoto intended!!