"if it's worth doing, it's worth doing well" ?
mine said that too!
Glynor, at the beginning of your post, above, I was recoiling, thinking, this is waaay too complex, I'm finding it hard to keep up"....
but by the end, you'd joined all the pieces perfectly for me, and you want to know where this idea would absolutely rock?
Images, photos. that's where!!
MC could save any image edits as a new file, linked to the original. It could (hopefully) keep track of multiple versions of an image. Each time it's edited, a new file is created. MC could keep the tags for each of these files synchronised, including the EXIF data.
You know, if acdSee or photoshop elements updates/creates an EXIF tag, they also create a tag that contains the software name, and when I see that, I think how good it would be to see MC in there. Maybe it's possible the advertising would pay the developement costs!!
It would certainly step MC up to a new level.
That is the first idea to really 'light my fire' in a long time.
Matt, I hope you'll stay active in this thread as I'd love to hear your comments regarding glynor's suggestion.
The terms "10 gig" and "cache" sound contradictory at first, then all the lights come on, I smile, and I see how cool it could be to have a 10 gig cache.
absolutely no offense meant, but I like glynor's idea better.
What do you think?
I'm of the opinion that a photograph's EXIF data is as essential to that photo as an mp3's standard id3 tags are to it. They're not 'just' metadata, they're a part of the picture, and so should be saved as such. I could use MC to manage my photos, and then send photos to my mum, who uses elements, and my brother, who uses acdsee, and they would be able to see the captions I'd added to them. How cool would that be!!