Aperture regards masters as previews
Hi,
I recently moved from iPhoto to Aperture. I opened my existing iPhoto library, which holds 25k pictures, in Aperture (so I did not use the File -> Import option, I simply opened the existing iPhote library).
Out of the 25k photos, roughly 500 of them have a badge with showing a yellow warning sign (I filtered on "File Status" is "Missing").
After some investigation through the Finder, it turns out that for these 500 photos, Aperture is missing the master files. So there is no photo in the My iPhoto Library / Masters but there is a photo in My iPhoto Library / Previews. However, these photos are actually masters, not previews, judging from the pixel size (3008 x 2000, which is the same as the other photos I took with my Nikon D70 at that time).
It looks to me that somehow Aperture regards these photos not as masters, but as previews. I can't find a pattern which of the 500 images are affected by this, it seems to have happened to some random pictures in my library.
Is there an easy way to let Aperture recognise these photos as masters again? I guess one option could be to copy each image to e.g. the desktop and import them again. How do I ensure Aperture links these newly imported photos to the photos regarded as previews?
Would the problem be resolved if I _import_ my iPhoto library into Aperture rather than just open it? What are the differences/benefits of importing an iPhoto library compared to opening an library in iPhoto?
Thanks,
Ivo
Hi Frank,
Aperture 3.4.5
iPhoto 9.4.3
Yes, I could try to import the complete library as a new Aperture library but I guess this would create a library file at least equal in size of the existing library, i.e. 75 Gb. Are there any benefits of doing so? Will all the projects, keywords and albums be maintained? Will it make browsing the library faster?
I have tried to re-import one of the problematic photos to see if Aperture would automatically recognise and regard it as a master - no success.
Best regards,
Ivo
Similar Messages
-
Defining what Aperture regards as a 'new' file.
If I import referenced file from a directory, then something changes the mtime of that file, Aperture regards it as a 'new' file and I end up with what appears to be two masters identical in appearence with the same file name.
The behaviour I expected was that a new file was just that -- a file that hadn't been there before.
I've done this by mistake twice -- and now once deliberately.
This is a problem. If metadata has already been written, then each file must be checked to see if it is the one with metadata in order to eliminate the correct duplicate.
(I'm scanning images for an alumnni school llibrary. I have 20 milk crates of albums to do. I typically will scan while watching the tube in the evening, then apply metadata later in the evening. Each binder is a 'project'
I can the following ways to work with this:
1. Don't even think about applying any metadata until a project is complete.
This way, any time I import twice, I can just chuck that whole project and re-import.
2. Carefully track the last file name entred, and make sure that I don't have any thing aready in the library checked for import. This is tedious.
3. Create new folders as needed so that no folder is ever used twice for import.
4. As I add metadata, also give pix a rating. In eliminating duplicates, I just do ones that are not rated.
Is there a better answer?
Is there a way I can tell aperture "don't import duplicates" means don't import a file if there is a file of that name?
If you want to reproduce this error:
Import a folder of files.
Open a terminal window, and navigate to that folder.
Run the command "touch *"
Now all the files will show up if you import from that folder AND have Don't import duplicates checked.I'm not sure just what I'd done the accidental times. I think it was using photosweeper, a duplicate and similar pic finder. (Recommended, BTW)
However I end up with TWO images in the browser that act like separate masters that both refer to the same external referenced file. Not clear what happens if I delete a version and master. I'll try that in my test folder.
As to the other problem. I used referenced files, because I use programs other than Aperture. Which is one of the reasons it's easy to shoot myself in the foot, I'll admit.
As an example:
Import a set of files from a folder.
Chuck the duds.
Use external program to write NAD27 location data to geotag.
Reprocess masters to pull the geotag data.
Now that I'm aware of the problem, I'll just delete versions and re-import, and NOT assign metadata while a project is in flux.
(As an example of a project that is in flux -- I own a tree farm. Over the course of a year, I take several thousand pictures for inventory. With this bug, I'll make sure that each day's shoot comes in as a separate project initially, and then after I've done with it, I'll move those pictures into the long term project. Probably a better work flow anyway)
As to the two cameras issue. I don't have two Nikons, but I ran into that problem when I was teaching photography. Most cameras allow you to change the prefix. I had my students change it from IMG to their initials.
In your camera case, to me it is unlikely that you would have both cameras iimporting into the same folder with the same number. Still, this is a reasonable border case. My requirements for unique file name would be within the same folder. With internal files, Aperture renames them according to date and time I think.
For referenced files imported from a folder a pre-existing name should be reprocessed, with metadata merged. That would be my usual reaction. But there should be choices.
Consider: If I moved the file there, I've ALREADY clobbered the old master. It doesn't exist anymore. Aperture should detect this and do the right thing.
More signficantly, if Aperture wrote INTO the file something like "Aperture imported on {hostname} Aperture ID 1122334455 or whatever string Aperture uses for a key for this image in it's internal database, then:
A: Aperture recognizes that some other program as been messing about.
B: Aperture knows that this file is already in it's database, but MIGHT have been modified. (And therefore should be flagged for the owner to check adjustments.)
Aperture could do some things that are more clever: When it suspects changes in the file, I extracts a new preview. The new preview is compared to the old one. If Identical, then the image is the same. If different but close, and in the same project, the user is alerted, and asked Keep both? Keep newer Keep older Keep newer, and move metadata... Remember choices for rest of this import.
As a more extreme example: My scanner creates TIFFs. A 2000 x 3000 pixel image of a slide is about 45 MB. As a png file (exact same data, but better compression) it's about 30 MB. I'd like to import, sort, change to png. Instead I change to png before import. It's uses more cpu cycles since I'm processing files that will be discarded, but cpu cycles are cheap.
Part 2 of this answer:
Because I keep referenced files and because Aperture doesn't track derivative files, I try to give my photos meaningful names, so that from the name of a file much of it's pedigree is apparent. If Aperture tracked masters by an internal tag, then derivative files would be a LOT easier to track. Aperture could then go with the flow if I used a perl script to rename files.
So, for example, I've done many canoe trips. The first one was on the Fond du Lac river in northern Saskathewan. So they are renamed FDL-001 FDL-002. Now that I'm no longer limited by dos nameing conventions (or writing them in tiny print on the edge of a slide) I'm more likely to name them Fond_du_Lac-75-001 -
Aperture+Slow Generation Of Previews
Hello All,
I'm wondering if anyone can offer any suggestions regarding Very slow preview rendering ? I have a DP G5 with 1.5 G Ram.
I imported 1100 Jegs from my Canon Mark II, I have the preview size set to fit between 1920 * 1929 pixels and a quality of 5, it seems to take about 30 minutes to generate all the previews, - is this normal ?, I relise 1100 odd pics is a large number, but is it usally this slow ??
ThanksPreview can really slow things down in Aperture. You might consider leaving them off and then generating them only for the images that you need previews for slideshows, iLife integration, or drag-and-drop. This is what I do, and it seems many others do the same from what I have read on this forum.
There is good info about Previews here:
http://homepage.mac.com/bagelturf/aparticles/previews/previews.html
Or search these discussions as this has been discussed quite a bit.
-Karen -
Masters and previews all mixed up
Recently the wife has started organizing our large (over 73 gigs) iPhoto library and complained that many of the photos were displaying as small: thumbnail sized. Investigating, I opened the iPhoto Library and found that the contents of the Masters and Previews were quite jumbled. Using Spotlight I quickly discovered that for any given file there were at least 2 versions of each image, a full size (say 1.2MB or so) and a preview (60KB or so) but my Masters directory contains hundreds if not thousands of the little previews and there are lots of the full size images in Previews.
It also seems that, among the confused images, all the full size images have the uppercase "JPG" extension and the previews are lowercase.
I have tried repairing twice to no avail. I haven't rebuilt because I suspect it would compound the problem by making previews of my misplaced previews etc etc. I could easily use the Finder to search/sort by file type and size, save all the originals and start a new library, but I don't want to lose all the metadata, retouching, and so on. I suspect the problem started when migrating to new Macs from our old G5 and iPhoto 6. What's the best way out of this mess?Sounds like when you migrated you imported your old library into iPhtoo on your new system
NEVER import an iPhoto library into iPhoto - it does not wrok and creates a massinve mess
The only real solution is to go back and do it correctly - drag the bad library to the desktop and then Connect the two Macs together (network, firewire target mode, etc) or use an external hard drive formatted Mac OS extended (journaled) and drag the iPhoto library intact as a single entity from the old Mac to the pictures folder of the new Mac - launch iPhoto on the new mac and it will open the library and convert it as needed and you will be ready move forward.
LN -
Aperture 3: low quality preview images
I don’t know if it's just a problem with my (new) Aperture Trial library or if it's a Aperture 3 bug:
The preview images Aperture 3 (trial) creates from raw files (in my case NEFs) are different from the JPEGs exported using the same JPEG settings.
I get the impression that the preview images don’t use all the adjustments applied to the raw files. They don’t have the moire reduction applied. The preview images of high ISO images have color noise, the exported images don’t have that color noise (the moire and noise settings of raw fine tuning are applied to the exported files but not to the image previews).
As the preview images are used for the Finder media browser, iLife, iPhone/iPod touch picture sync and other things the lower quality is not acceptable for me.
The preview images of Aperture 2 are identical to the exported JPEGs from Aperture 2 (using the same settings).
I use Aperture 3 Trial with a new trial library and a few hundred raw images just to test Aperture 3.
I already erased all preview images and rebuild the previews. I deselected using the embedded JPEGs from the raw files and I let Aperture rebuild the miniatures.It seems that Ap2 syncs the previews to the iPhone... you have to clear the previous cached previews before it will load higher quality previews... anyhow, here is what I did... and photos look better on my iphone (not feeling motivated enough to verify if it is the same quality as iphoto sync)...
1.) change Ap2 prefs for "limit preview size" to "don't limit"...
2.) select all the photos in the album(s) you are want to sync, right click (ctrl click), and select delete previews...
3.) sync your iphone again...
if that doesn't work directly, you might need to uncheck sync photos to delete all photos on the iphone, but the ultimate goal is to ensure refresh with the higher quality previews...
Hope that makes sense or gets folks in the right direction... Apple really needs to put a check box in future version of itunes to sync full quality or something... -
Having had the previews created I selected all photos and "delete previews". It did this quickly and no more previews being created. Once aperture is closed and then re-opened aperture immediately sets about creating the previews for the same photos. I don't understand why this should be happening.
This is occuring on my Mackbook Air (Aug 2012) which has 256 GB storage. I am fast running out of space as I am using "Managed Masters". I intend to make the masters referenced by relocating them to an external HDD but before doing this would like to clear up this problem first. I keep my Vault on the external HDD and have Time Machine and Time Capsule. When I have relocated the masters to the external HDD I intend that TM backs the external HDD to the TC. I tink that I will use the second partition on the external HDD for Carbon Copy Cloner to back up the Mackbook Air.
Any help or advice warmly welcomed.Frank
Many thanks for your input.
Following your advice I have selected all the projects individually and checked the status of Mantain Previews. Some were indeed marked up for Mantail Preview so I have unmarked them.
I have also selected Photos and deleted previews and also repeated this for My Projects.
Checking the Get Info for the Preview folder in Aperture Library in Finder this now tells me that I have zero bytes for 564 items.
Close and then reopen Aperture and it regenerates these564 previews in the blink of an eye. I haven't been able to locate these photos yet. I know there are about 120 in facebook and 10 in photostream but dont know where the rest are.
It seems the issue is not with Aperture but with myself and not understanding Aperture sufficiently well
Do you see the problem this way? -
Aperture 3 low resolution previews
Hello all,
I've been using Aperture 3 for a few weeks now and loving it. I read in the forums about how previews are set to low resolution and i've been having problems trying to get them back to a high resolution image file. I've imported the photos in iPhoto 09 and exported them to Aperture 3 (which are high resolution image files) to do further enhancement. After working with them, i noticed that the resolution dropped significantly. As a test,I dragged a photo which i've worked on to the desktop and it gave me a very low resolution. I then tried to export the same file using the drop menu to the desktop but still a very low resolution. Is there a way to get them back to a high resolution image file?
The second thing i did was to export the photos to my mac gallery and so i uploaded them with the original files but i still get the photos that i've worked on with a low resolution. The original files are still in high resolution.
Please advice and thanks everyone.
BrianIt might help to clarify your workflow:
I've imported the photos in iPhoto 09 and exported them to Aperture 3
There is no way to "export photos" from iPhoto to Aperture, so how exactly did you get them there? Export/Import? Drag and Drop... from where to where?
After working with them, i noticed that the resolution dropped significantly.
What do you mean by "resolution"? Do you mean the dpi? The file size?
As a test,I dragged a photo which i've worked on to the desktop and it gave me a very low resolution.
This only produces a Preview, but again, what do you mean by "low resolution."
Regards
TD -
Orange-Red Blotches in Aperture, yet not in Preview....
In Aperture the photo looks like it has Orange/Red blotches in it...
BUT, when opened in preview or iPhoto, it looks ok????
I shot it with a nikon D50 it is a raw file...
Help, any ideas....
take a look here..
http://web.mac.com/careyjames/iWeb/Carey%20James/Photos.html
MacBookPro Mac OS X (10.4.8)"[...] however it's kinda weird that
the photo somehow exported with the highlights. I've never seen that happen."
If you press CMD + SHIFT + 4 you can make a selection of the screen and as soon as you let go of the mouse button, the picture of the selected area is saved to the desktop.
Instead of making a selection you can hit the SPACE bar after CMD + SHIFT + 4 and then move the cursor over and click on the window you want to grab. You will see the window being selected.
Finally, if you want the grab to be available in the clipboard instead of saved on the desktop, you press CTRL together with the CMD + SHIFT + 4- combination.
Regards
paul k
Mac OS X (10.4.8) -
Aperture 3.3 - The Previews mechanism appears to be entirely broken.
TL;DR: In Aperture 3.3 are your Previews in Aperture there when they shouldn't be, and not there when they should?
Try confirming this:
I created a new Library with a couple of small albums for testing. The Previews folder in .aplibrary is empty even when New Projects Automatically Generate Previews is on, Maintain Previews for Project is selected, and when I go to the photos and select "Update Preview" I get a message saying the Preview is already up to date. When holding down the option key and doing a Generate Preview, I still get nothing in the Previews folder, regardless of how many photos I do this with or what resolution/quality I have my previews set to.
On the other hand, if I turn off New Projects Automatically Generate Previews, deselect Maintain Previews for Project, and select photos and then "Delete Previews", I'm still able to drag photos outside of Aperture (and get the plus sign as well as count of photos), and they copy to the Finder as well as other apps in full resolution. Additionally when I go to iTunes, it will sync all of the items in the Project even though I've done all of this to kill off Previews (and there are no previews in the aplibrary/Previews folder).
I should note that I'm not doing anything weird here. For example, I only *looked* in .aplibrary when things weren't working and would never move or mess with anything in there directly.
This is a double problem and pretty serious:
1) Previews functionality is gone
2) Syncing with iOS devices can't be done using just the Previews, meaning it will sync everything, when combined with the Stacks Pick bug, this is a nightmare.Hi,
I think your issue is related to the buggy behaviour I described in this thread:
Aperture 3.3 Bug? Dragging to external editor can modify the original
My suspicion: Aperture 3.3 simply, clandestinely does not create previews, if the original image size is smaller than the pixel size for the previews.
What are the sizes of the images in your project compared to the preview settings?
If images do not have previews, because Aperture did not create them, then I found that Aperture passes the mster instead (or a copy of the master, if you drag to the desktop).
Regards
Léonie -
Can i replace missing masters w/ preview/browser images?
I have an aperture library with some pictures where the master is missing. I see them just fine in the browser. I cannot find them anywhere on my computer and disks (i.e. I have read and explored every method discussed here and at other support websites to locate them). We believe they were originally 'referenced' and then some time later the masters were deleted from the directory where they had been located. Now that i am certain that no master is to be found anywhere on my computer, can the 'previews' be exported or somehow used to replace these masters?
They look good enough and appear to have the quality and resolution to make it worth the effort, but i have not figured out how to do this. Suggestions?
JohnThe previews can;t be exported via the normal procedure, the export pane, but you can simply drag them out of Aperture. If you click on one of the images and start dragging you will see the pointer turn to a green plus indicating you are copying the image.
I would make a folder or folders on the desktop and drag the images from Aperture into it. Create a smart folder in Aperture to select all the images with missing originals, select all those and drag them out.
Then you can import those images back into Aperture. Note that these images will be treated as new imports by Aperture, there will be no connection to their previews or metadata currently in the library.
regards -
Everytime I open Aperture it starts rebuilding previews and thumbnails. Any idea why?
Help please?
Closing and reopening Aperture after it completed its job just started rebuilding previews & thumbnails again and again
If all previews have been generated, and you still see frequent processing of previews, there may be two reasons:
Your Preferences settings do not take, because the preferences file in the user library is corrupted.
You may have imported a corrupted image file or video, for that the generation of previews will never succeed.
The first can be fixed by removing the Aperture preferences apple.com.Aperture.plist from your user library, see the Aperture 3: Troubleshooting Basics on how to do this.
The second requires to search your last import, and to try to generate previews manually for subsets of these images, to find the one, for which the generation of previews will hang.
Regards
Léonie -
D600 raw file could not open in Aperture, but ok in Preview
I import D600 photo to my Aperture library all photo are in RAW format, but some file (almost 1-2 out of 100) could not view in Aperture, which show "Unsupported Image Format", but which could open in Preview, I try to import those file again and I got the same result, could someone help me.
I am using 3.4.3
I think it not my card or file problem, cause if I import the photo to the library using iPhoto it will not have this problem
I have try to import the same photo to my library using Aperture and iPhoto, Aperture will always have one or two picture could not view, but when using iPhoto import the picture it is zero problem and also Apterture could view those pic which using iPhoto import.
Therefore I think the problem should be Aperture itself. -
Iphoto librairy : masters and previews
Hi there !
I'm French so please excuse me if i make mistakes....
I have a question in relation with this link
https://discussions.apple.com/thread/3161569?start=0&tstart=0
I tried to write a question to Terence Devlin but i did not manage...
So I ask my question to everybody !
I did understand that pictures that are in "masters" AND in "previews" comes from a matter of rotation of the picture.
But, WHY, when I watch the picture from "masters", this picture has the same orientation as the one in "previews" ?
Other question : if I turn off the Auto-Rotate feature on my camera, i will have to rotate my pictures myself in iphoto, so it will create another picture in preview. Am I right ?
How can i do to stop having those pictures twice ?
Thanks a lot to everybody !but having twice the same picture is useless, don't you think ?
Not necessarily. It's the nature of having cameras that autorotate photos for you. That's why I rotate photos before importing into iPhoto. If you take an overwhelming amount of portrait oriented photos then you would be better off following the workflow I posted earlier in order to save space. Otherwise I don't think it would make much difference. The MacBook Air is designed as a lightweight traveling device and often is used in conjunction with a desktop Mac at home. With that type of setup I would have my primary library on the desktop Mac and a smaller traveling library on the Air. I would use the paid version of iPhoto Library Manager to transfer necessary photos via albums or events between the libraries as needed. The Air just isn't designed to handle the large libraries due to its limited storage capability. But that's just my philosophy.
If you edit a "normal" landscape photos you will automatically get a copy because iPhoto keeps the original/master file as its digital negative like all DAM (digital asset management) applications. There are high end DAM apps that you can edit and save the edited version over the original file if so desired. Media Pro 1 is one of them. I use it for may primary DAM work and iPhoto for special projects like books (a separate library for each book), cards, calendars, etc. -
Problem with RED color in Aperture, iPhoto but NOT Preview
I'm having a weird display problem in aperture and iPhoto, as well as in the small thumbnail preview in the Get Info window in the Finder: photos with large areas of red appear over saturated and blotchy, while the same image will be displayed fine in Preview, Mail, Safari etc.
I have checked with a number of people using OSX on G4/G5 and Intel machines and running 10.4.9 and they ALL have the same problem.
An example of the problem can be found in this picture: http://oroux.com/trucs/red_bug.png
Left is the image in Preview, middle in Finder's Get Info window and right in iPhoto...
I've checked the profiles in ColorSync Utility and there is no problem on that side.
2.4GHz core2duo MacBookPro Mac OS X (10.4.9)I don't see how it could be a profile problem, since other people (see post above) have the same problem with their pictures. Also, I did some shots over the week-end, including a girl in a bright red dress and the dress shows the same oversaturated red blotches. The image was taken in RAW with my Nikon D80, I didn't do any changes in Aperture, and I reset the colorsync profile of the MacBookPro and DELL 24" screens to their factory defaults.
And when I display the fullscreen image in Aperture, I can see for a split second the CORRECT image, then it does some "color magic" and the details goes down the drain.
Plus, if you look at this image (http://oroux.com/trucs/red/testrouge/10-4-9qt7-1-6/comparaison.png, it's big, 2MB) showing screen captures of a detail of a photo in six different OSX apps, you'll see that not two display it in the same way, which is a real problem. -
What Are The Limits To Aperture? (Masters, Versions, Projects...)
If Apple has a specification for any of these, I couldn't find it.
It's obviously not on the Aperture web site under tech specs.
I couldn't find it in the user manual, but I have been known to stink at searching the manual.
I did some searching on this forum, but I kept coming up with some rather old posts.
Which means, the answer is probably right in front of me and I simply can't see it. So, sorry for asking a question that I'm sure has been asked and answered more than once.
I was wondering if anyone knows what, if any are the limits for ...
How many Masters in a Library?
How many Versions in a Library?
How many projects in a Library?OT: 42
"Alright," said Deep Thought. "The Answer to the Great Question..."
"Yes ...!"
"Of Life, the Universe, and Everything ..." said Deep Thought.
"Yes ...!"
"Is ..." said Deep Thought, and paused. .....
"Yes ...!!!...?"
"Forty-two," said Deep Thought, with infinite majesty and calm.
There is a theory which states that if ever anybody discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable. There is another theory which states that this has already happened.
Maybe you are looking for
-
Is it possible to connect to Drives with the same name simultaneously on Windows?
Hello I have used Adobe Drive to create two connections to two different servers which both have the same setup: Server one: Adobe Drive webservice which is connected to a database called "DatabaseA" Server two: Adobe Drive webservice which is connec
-
After using my new iPhone 5 for a few months I tried to sync it to my computer but it said I had to wipe it first, I don't know if it means everything or just the music. Half of my music transferred to my iTunes library and the other half I can get t
-
dear gurus, I am familiar with creating standard Infocube's in BI7. I have 2 dimensions in this cube and 3 infoobjects that I have inserted in these dimensional. This is a flat file loading. Now how will I know which infoobject will be acting a prima
-
It seems that the SGE2000 switch will lose the connections of systems after some period of time. I will ping a system and it will be slow or will not reply at all. See example below: C:\>ping 10.1.16.16 Pinging 10.1.16.16 with 32 bytes of data: Reply
-
Unable to open files as layers.
I just bought Lightroom 5. I have been unable to export files as layers into Photoshop CS4, no matter what. I just wonder why. Could anybody help me with this? William Rodriguez Miami, Florida.