Referenced files
I added about 10,000 referenced files, events, etc. to iphoto.
They are not showing up in itunes shared photos.
Doing something wrong?
thanks
Well, no idea why, but this morning the files were available and the streaming worked just fine.
Similar Messages
-
FrameMaker 8 (Unstructured) - How to Find/Change "Referenced File" location globally?
Hello,
First off, I have a FrameMaker 8 (Unstructured) book that links ALL of its graphics, to a separate graphics folder on my network drive.
With that said, I am hoping to do the following:
1. Create a mirror copy of "Book A" and place that copy in another folder, (at the same level) on my network drive.
2. Open up the new book file (e.g. Book B).
3. Run a Find/Change to replace:
..\..\..\Graphics Catalog A\Graphics\a000123.png
..\..\..\Graphics Catalog B\Graphics\b000123.png
The end result is that I could globally map out all the "Referenced Files" to the new folder path structure. This will allow me to save from having to manually re-import each of the 1000 graphics - into my book files.
Finally, I am hoping to do this with the built in capabilities of FrameMaker 8 first. If that is not possible, then I will consider other possibilities.
Thanks in advance for any suggestions.
Regards,
JimThis is how you do it:
Outside of FM, copy the "Book A" folder and paste it where you want.
Also, create the Graphics folder and file structure (i.e.
"... Graphics Catalog B\Graphics ...")
Before you open Book B in FM, temporarily rename the graphics
folder that the FM files in Book A uses, e.g. "Graphics Catalog Z".
Now, when you open the files in Book B, FM won't be able to find
the old graphics since the folder name has changed. For each file,
FM will open the "Missing graphics" dialog, where you need to
browse to the new graphics folder, e.g. "Graphics Catalog B\Graphics".
Select the correct file that FM asks for, and tick the option to
use this folder for all remaining graphics.
If all the image file names are identical, you will only need to
do this once per FM file. If you really need the image file names
to differ like you said:
> ..\..\..\Graphics Catalog A\Graphics\a000123.png
> ..\..\..\Graphics Catalog B\Graphics\b000123.png
then you need to select the correct file name for *each* graphics
that FM cannot find. This is a good reason to keep the file names
identical, even though the folder name has changed.
When all the files have opened, rename the original graphics folder
back to "Graphics Catalog A".
/Thomas Michanek -
How do I stop Aperture consistently crashing when attempting to reconnect a few referenced files?
Has anyone else run into this? It's driving me nuts.
Many months ago I had Aperture move my referenced photos to a larger external hard drive. I just discovered recently that there's a small handful of images that it still thinks are on the old hard drive (even though it successfully moved the original files to the new hard drive, oddly). The full sized previews and all the meta data are still there in Aperture but it regards the photos as offline.
So I select a few (<10) of the affected images, select the "Locate referenced files" option in the File menu, to get the "Referenced files in selection" window. I click on the new hard drive name in the lower panel and Aperture instantly displays the same photo on the new hard drive. I can arrow down through the ten or so images in the top panel and Aperture instantly displays all of them on the external hard drive.
So I press "Reconnect all" and Wham! Aperture crashes. Consistently.
It sometimes works with a single image, but not yet more than once before it crashes.
Aperture has also been driving my nuts with the spinning ball since Mountain Lion and the latest update. (My hardware may be getting a bit out of date for this now, although it was working fine before--it's the fastest late 2009 13" MacBook Pro with 8 GB of RAM.) I've already tried repairing the library (Aperture forces me to do this after a about three of the abovecrashes). I've rebuilt the whole library (twice now). I've deleted the Aperture preferences and relaunched. I've deleted the Aperture application and reinstalled it from the AppStore.
Any ideas on what I can try next? Thanks!
Here's the first lines of the crash report that Apple generates:
Process: Aperture [29772]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.4.1 (3.4.1)
Build Info: Aperture-301039000000000~2
App Item ID: 408981426
App External ID: 11130653
Code Type: X86-64 (Native)
Parent Process: launchd [177]
User ID: 501
Date/Time: 2012-10-25 08:47:06.464 +1300
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report: 122141 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 102826 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: C8AB497A-18DB-3A43-8663-4B28960DFA6E
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Application Specific Information:
objc_msgSend() selector name: dealloc
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff897cf250 objc_msgSend + 16
1 com.apple.Aperture 0x0000000106f2ce46 0x106e03000 + 1220166
2 com.apple.Aperture 0x0000000106f2cf32 0x106e03000 + 1220402
3 com.apple.AppKit 0x00007fff91a15ce6 -[_NSBrowserMatrixColumnViewController reloadData] + 587
4 com.apple.AppKit 0x00007fff91a02e23 -[NSBrowser _matrixBasedReloadColumn:] + 199
5 libdispatch.dylib 0x00007fff8b431f01 _dispatch_call_block_and_release + 15
6 libdispatch.dylib 0x00007fff8b42e0b6 _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fff8b4330c8 _dispatch_main_queue_callback_4CF + 275
8 com.apple.CoreFoundation 0x00007fff899b30fe __CFRunLoopRun + 1614
9 com.apple.CoreFoundation 0x00007fff899b26b2 CFRunLoopRunSpecific + 290
10 com.apple.HIToolbox 0x00007fff8df760a4 RunCurrentEventLoopInMode + 209
11 com.apple.HIToolbox 0x00007fff8df75e42 ReceiveNextEventCommon + 356
12 com.apple.HIToolbox 0x00007fff8df75cd3 BlockUntilNextEventMatchingListInMode + 62
13 com.apple.AppKit 0x00007fff9178b613 _DPSNextEvent + 685
14 com.apple.AppKit 0x00007fff9178aed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
15 com.apple.Aperture 0x000000010727700d 0x106e03000 + 4669453
16 com.apple.AppKit 0x00007fff919d5709 -[NSApplication _realDoModalLoop:peek:] + 485
17 com.apple.AppKit 0x00007fff919d59ce -[NSApplication runModalForWindow:] + 120
18 com.apple.Aperture 0x0000000106f7fcb3 0x106e03000 + 1559731
19 com.apple.Aperture 0x0000000106e4b0b5 0x106e03000 + 295093
20 com.apple.AppKit 0x00007fff9187ba59 -[NSApplication sendAction:to:from:] + 342
21 com.apple.prokit 0x000000010831f10c -[NSProApplication sendAction:to:from:] + 101
22 com.apple.Aperture 0x00000001072780bf 0x106e03000 + 4673727
23 com.apple.AppKit 0x00007fff919b144c -[NSMenuItem _corePerformAction] + 406
24 com.apple.AppKit 0x00007fff919b113a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133
25 com.apple.AppKit 0x00007fff9169e46f -[NSMenu _internalPerformActionForItemAtIndex:] + 36
26 com.apple.AppKit 0x00007fff9169e2f7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
27 com.apple.AppKit 0x00007fff919aa245 NSSLMMenuEventHandler + 342
28 com.apple.HIToolbox 0x00007fff8df4ef0a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206Has anyone else run into this? It's driving me nuts.
Many months ago I had Aperture move my referenced photos to a larger external hard drive. I just discovered recently that there's a small handful of images that it still thinks are on the old hard drive (even though it successfully moved the original files to the new hard drive, oddly). The full sized previews and all the meta data are still there in Aperture but it regards the photos as offline.
So I select a few (<10) of the affected images, select the "Locate referenced files" option in the File menu, to get the "Referenced files in selection" window. I click on the new hard drive name in the lower panel and Aperture instantly displays the same photo on the new hard drive. I can arrow down through the ten or so images in the top panel and Aperture instantly displays all of them on the external hard drive.
So I press "Reconnect all" and Wham! Aperture crashes. Consistently.
It sometimes works with a single image, but not yet more than once before it crashes.
Aperture has also been driving my nuts with the spinning ball since Mountain Lion and the latest update. (My hardware may be getting a bit out of date for this now, although it was working fine before--it's the fastest late 2009 13" MacBook Pro with 8 GB of RAM.) I've already tried repairing the library (Aperture forces me to do this after a about three of the abovecrashes). I've rebuilt the whole library (twice now). I've deleted the Aperture preferences and relaunched. I've deleted the Aperture application and reinstalled it from the AppStore.
Any ideas on what I can try next? Thanks!
Here's the first lines of the crash report that Apple generates:
Process: Aperture [29772]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.4.1 (3.4.1)
Build Info: Aperture-301039000000000~2
App Item ID: 408981426
App External ID: 11130653
Code Type: X86-64 (Native)
Parent Process: launchd [177]
User ID: 501
Date/Time: 2012-10-25 08:47:06.464 +1300
OS Version: Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report: 122141 sec
Crashes Since Last Report: 9
Per-App Interval Since Last Report: 102826 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: C8AB497A-18DB-3A43-8663-4B28960DFA6E
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Application Specific Information:
objc_msgSend() selector name: dealloc
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00007fff897cf250 objc_msgSend + 16
1 com.apple.Aperture 0x0000000106f2ce46 0x106e03000 + 1220166
2 com.apple.Aperture 0x0000000106f2cf32 0x106e03000 + 1220402
3 com.apple.AppKit 0x00007fff91a15ce6 -[_NSBrowserMatrixColumnViewController reloadData] + 587
4 com.apple.AppKit 0x00007fff91a02e23 -[NSBrowser _matrixBasedReloadColumn:] + 199
5 libdispatch.dylib 0x00007fff8b431f01 _dispatch_call_block_and_release + 15
6 libdispatch.dylib 0x00007fff8b42e0b6 _dispatch_client_callout + 8
7 libdispatch.dylib 0x00007fff8b4330c8 _dispatch_main_queue_callback_4CF + 275
8 com.apple.CoreFoundation 0x00007fff899b30fe __CFRunLoopRun + 1614
9 com.apple.CoreFoundation 0x00007fff899b26b2 CFRunLoopRunSpecific + 290
10 com.apple.HIToolbox 0x00007fff8df760a4 RunCurrentEventLoopInMode + 209
11 com.apple.HIToolbox 0x00007fff8df75e42 ReceiveNextEventCommon + 356
12 com.apple.HIToolbox 0x00007fff8df75cd3 BlockUntilNextEventMatchingListInMode + 62
13 com.apple.AppKit 0x00007fff9178b613 _DPSNextEvent + 685
14 com.apple.AppKit 0x00007fff9178aed2 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
15 com.apple.Aperture 0x000000010727700d 0x106e03000 + 4669453
16 com.apple.AppKit 0x00007fff919d5709 -[NSApplication _realDoModalLoop:peek:] + 485
17 com.apple.AppKit 0x00007fff919d59ce -[NSApplication runModalForWindow:] + 120
18 com.apple.Aperture 0x0000000106f7fcb3 0x106e03000 + 1559731
19 com.apple.Aperture 0x0000000106e4b0b5 0x106e03000 + 295093
20 com.apple.AppKit 0x00007fff9187ba59 -[NSApplication sendAction:to:from:] + 342
21 com.apple.prokit 0x000000010831f10c -[NSProApplication sendAction:to:from:] + 101
22 com.apple.Aperture 0x00000001072780bf 0x106e03000 + 4673727
23 com.apple.AppKit 0x00007fff919b144c -[NSMenuItem _corePerformAction] + 406
24 com.apple.AppKit 0x00007fff919b113a -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 133
25 com.apple.AppKit 0x00007fff9169e46f -[NSMenu _internalPerformActionForItemAtIndex:] + 36
26 com.apple.AppKit 0x00007fff9169e2f7 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
27 com.apple.AppKit 0x00007fff919aa245 NSSLMMenuEventHandler + 342
28 com.apple.HIToolbox 0x00007fff8df4ef0a DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1206 -
Aperture referencing files to time machine HD instead of from 'working' HD
Every once in a while I will go into a project see the "broken link" icon on my previews. In Finder I check the location I have all my images stored (and initially referenced) on an external HD. They are there.
I go to File>>Locate Referenced Files and see the referenced images have been changed to a location on my separate Time Machine external HD. I locate them and everything is fine but it's annoying.
I don't not have Time Machine on automatic because I have a laptop and like to choose when it backs up. I've looked through other Time Machine/Aperture problems and couldn't find anything. Does any one know of a setting, advice, or have experienced this at all?
Thanks.Thanks. Sorry, for the delay to answer your questions:
I'm the only one managing the files, and it has happened quite a few times now. The files are in multiple projects ranging from recent imports to projects from a few years ago.
I didn't need to use "File→Relocate Master ..." just the "File→Locate Referenced Files" because my masters are still intact on my working HD. It says that my previous location was on "Volumes/Time Machine/photography/...etc." when I always import masters to "Volumes/My book/photography/...etc"
Does Aperture notice if I move master files because my thought is that Aperture is noticing my TM copying files to another HD and then referencing those instead of my original working HD I import to. Then, the next time I open Aperture it cannot reference the Time Machine files.
Is it because I have TM (USB) backing up my internal HD and my external working HD (FW800)? -
After I've changed the file name/format in Finder iPhoto can't load/relink to the referenced file anymore. For some reasons I don't like to reimport the file.
Hmm the advice has been not to use referenced libraries - you ignored and did it anyway and you find the advise not helpful
Furthermore the advice is that if you choose to use a referenced library that you assure that the path never changes - you also choose to ignore that advice and do it anyway - and you blame the peopson trying to help you
once again - you have one choice - change the file names back and put the files back in the exact same place - and again you are totally ignoring the advice and instead name calling and attacking the person giving you advice
Maybe life would be easier if you followed advice rather than ignoring it and then complaining that things no longer work
change the name back and you will be fine until the next problem you hit that is caused by choosing a referenced library
Have a nice day
LN -
File paths and archiving (and referenced files).
I've come to the stage where I need to start using referenced files (out of disk space on my laptop) and also start archiving projects. One of my plans was to start keeping an off-site backup of all the originals in case something really bad happened. I'm also going to have on-site backup of projects. But for the off-site originals I would like to have some simple way of finding the photos in case something bad happens, my idea was to simply create a PDF from the list view where I could see the photo and the file path to where it's stored (I plan to store them in simple year-month-day hierarchy).
The reason why I'm not going to archive the projects off-site is simply the cost, I did a test yesterday and it looks like just storing the originals would be approx 1/3 in size of the projects.
If someone has a better idea of how to handle this please let me knoeI'll try to explain.
About the cost: Hard disk space is really cheap and I can not see how the cost should be that expensive. This is based on your statement that you still have your images on your laptop and that itself limits the amount of space hence a rather small library.
When it comes to backing up your projects you have several options. First, if you really want to be cheap about hard disk space (I think you should not since your images really are priceless) you can export projects of your referenced images and not consolidate the images into the exported project. Not to consolidate vs. consolidate images on export really makes a difference in the exported project size. On the other hand, not consolidate images on export of a project makes you back up your images separately, which leads to more work.
My advice is then; buy two disks (preferable three disks), and export your projects with the images consolidated into one of them and start using the other one with your referenced images.
I always advice users to have their images in at least three different locations and IMHO the ideal solution for you would be to have your images referenced on one disk and mirrored backups on the other two disks, either one stored in two different locations in case of burglary, fire etc.
Regards
Paul K -
Can't locate Referenced Files in Aperture 3
All my photo master files are in separate directories on a NAS (network attached storage; 4x1Tb) and I import Projects from that into Aperture on my IMac. I migrated my MAC Aperture Libraries to a separate external drive and lost some of the references to the Master. I can reconnect some Projects to the masters on my NAS, but not all. Some projects won't reconnect using Locate Referenced Files. I can find the files and match the photos and Aperture looks like it reconnected, but when I look at the separate images, I get "File not found." I know the original photos are on my NAS because I can see them using a separate PC hooked into it, but can't seem to complete making the link to the master. My intent is to move all masters into my Aperture Library because I can't stand losing photos this way anymore, but I need help making that link. Any ideas what's happening and what to do.
Even though I have the originals on my NAS, all my processed versions (4 and 5* photos) are in my Aperture Library and I hate to lose those.
Update: I seem to be able to connect one photo at a time, but selecting an entire set of Project photos and doing "connect all" doesn't seem to be working. I have thousands of photos and working one at a time is impossible.
How can I get help?
<Email Edited By Host>I migrated my MAC Aperture Libraries to a separate external drive and lost some of the references to the Master.
How is your NAS formatted, where your original masters are stored? And how is the external drive formatted that holds your Aperture library?
Your Aperture library needs to be on a drive formatted Mac OS X extended, Journaled. If the drive should not have that formatting, move the Aperture library to disk with the coorrect format.
If you cannot reconnect originals, that are clearly there, the reason may be, that your Aperture library needs repairing, see: Repairing and Rebuilding Your Aperture Library: Aperture 3 User Manual
I'd try to repair permissions and to repair the library, before trying to reconnect again.
Since you want to consolidate all originals in your Aperture library, I'd try to copy the originals that cannot be recoonected, to the same drive that holds yor aperture libryr and try to reconnect them there, then consolidate them from there. It can be, that the network connection of the NAS is not reliable enough.
Regards
Léonie -
In Aperture 3.4.1, I am not able to connect with referenced files on a network
I am running OS X 10.8.2 and Aperture 3.4.1, and am unable to connect with referenced files on a network. Specifically, the referenced files reside on my iMac and I am attempting to connect to them from my MBP. They appear in red in the dialogue box. While I know this has been a long standing issue in other versions, I was hoping it had been solved by now. Any assistance will be appreciated.
Thanks -
Dudleyhttp://support.apple.com/kb/HT5922
If you want to mirror your desktop, see:
http://support.apple.com/kb/HT5404
Regards. -
How to use "referenced files" in MY case?
I have a MacBook pro, which I bring with me between home and studio.
Until now, I've been storing my shots on an external HD. This means that I cannot see my photos when I'm home.
I've been looking into the "referenced files"-thing.
I would like to be able to see a preview of all my shots also when I only have my MacBook and not the external drive. When I shoot, I would like to store NEW shots on my MacBook at first (to edit, tag etc.) but then put them on my external drive for storage.
I haven't been able to figure out how to do this. Can anyone please explain or link me to a place where I can read about it?
Thanks in advanceI haven't done this yet, but soon I'll need to coordinate a laptop and a desktop machine. So don't take my word for anything!
It sounds as though you have Aperture set up so that the laptop machine's library is on the external drive -- not just the images that make up the heart of the library. Is that right? The alternative would be to tell Aperture its library is on the laptop, but have the library reference master images on the external drive. Previews -- if you have Aperture set to create and/or maintain previews in any or all projects -- are in the library, which is on the computer whether or not you have the drive containing the masters with you.
(Am I going wrong yet??)
But I'm still not clear, when master images are referenced, where Aperture stores versions, adjustments, metadata; in the library or with the referenced images?
Anyway, it seems as though this arrangement should allow you to import new images into a project in the laptop's library while on the road. Then I don't think you even have to export and re-import the project -- when you're hooked back up to the external you just "relocate masters" for the new project onto the external drive.
Somebody please straighten me out if I've got all this wrong. -
How do you convert managed files to referenced files?
I have exported all the files that I mistakenly saved to my aperture library.
since I've exported them by year and month I can easily incorporate them into my referenced files on various external hard drives.
but how do I now actually get the managed files in the aperture library out of the aperture library? (I am trying to make the aperture file smaller so that it can more easily stay on my laptop).
and is there a way to get rid of the managed files without having to reimport all the files and reimport all the metadata …As I understand it:
You had a bunch of original image files and imported them into AP using managed.
At this point the original files are totally separate from AP, since AP has copies of the originals in its library file (a package). If you relocate, AP will not put the files back where they were, especially since you have moved some files around in the database.
If you haven't done much editing to the masters, consider creating a new library and a new import. Otherwise, try relocating a small amount of your projects to see how AP sets up the folders on the disk.
But AP will not automatically write the masters back to where the originals were - the relocate process involves you indicating where the files will go. As I recall, you have to choose a folder structure from several choices and these may not parallel the originals. Plus, as I said above, since you have moved files around the database, you will definitely not get the same layout as the originals. -
Aperture: After changed the file name in Finder Aperture can't load the referenced file anymore
After I've changed the file name/format in Finder Aperture can't load/relink to the referenced file anymore. For some reasons I don't like to reimport the file.
As you told, the command "Locate Referenced File" doesn't work, if the filename doen't match exactly. And the filenames should keep their new names.
"Locate Referenced File" will be able to reconnect one file at a time, if you direct Aperture to the matching file in the Loate Referenced File dialog, but it will not be able to recognise the other matching referenced files and to reconnect them all at once with the "Reconnect All" button.
It will be a lot of work to reconnect the one by one. Usually it is much easier to rename the original master files using Metadata > Batch change in Aperture than to try to do that in the Finder. -
Image size problem after converting from Managed files to Referenced files.
I recently moved to Referenced files for all my images. I use a plug-in (Graphic Converter 8.8.2) to resize all images to a consistent size (1440 pixels wide, landsacpe format) for a web app that I use (Sandvox). With Referenced files, when I drag and drop the externally processed image, it shows up at exactly one-half the correct size (720 pixels). As a test, doing exactly the same opeartion with an Aperture library utilizing managed files, there is no problem...it works as expected.
As a temproray work-around, I found that instead of dragging and dropping, I use the Aperture Export function, everything is correct. This is not really what I want to do because I have a lot of images to process.
This is Aperture 3.5 and Mavericks, but the problem was there with with Aperture 3.4 and OS 10.7.5.Thank you for the suggestion and running the test. I changed the Preview settings to 1440, and then 2560 and finally, Don't Limit. Quit and relaunch Aperture between each setting. No luck.
But you gave me a hint: maybe the problem has to do with the images being first Managed and then moved to Referenced files. So I tried one that has never been a Managed file and everything works correctly! Don't know if this is a bug or a feature.
Mystery solved, but I still have a lot of images to reprocess.
Thank you for the help. -
How do I know if the image is a master or a referenced file?
I imported images into Aperture, and am now not sure whether to delete the originals (that were already on my hard drive in a photos folder).
How can I tell, after having imported them, whether the images in Aperture are referenced or master?
I'm just scared of deleting the original folder (the outside aperture one!)
Thanks!
HannahNot really...
That merely shows you the master image with no adjustments applied - I think the question was how to tell the difference between masters that are referenced vs. managed - the answer to that question is that you can either use one of the functions under the file menu to consolidate the images into the library as managed masters (not available if images in the current selection are already managed) or use manage referenced files to take a look at the location on disk (not available for managed masters).
The other thing that you can do is do a search based on file status (add a search element to the search HUD)
more info here;
[Aperture File Management|http://photo.rwboyer.com/2009/01/aperture-2-file-management>
There are probably some useful info regarding searching near the end of the article.
RB -
Help with referenced files and importing
This might be more complex than can be addressed here, but I'm struggling with the organization of aperture.
Because I'm not sure I want use aperture forever, and because I occasionally like to use other photo editors, I've opted for a referenced file setup. I typically arrange my pictures into year/month sub folders, with additional folders for special subjects, like my kids. I've been doing this for a long time, it works for me, and I don't want to change.
Problem #1 - avoiding duplicates when I import. When I stick the card in my computer I want to copy just the new files to the directory I specify. Image capture only looks for duplicates in the target directory, which is no help if I'm importing files to "November" from a card that has files that were previously imported to "October." The easiest solution would be to delete the images off of the card after importing, but I can't do that - my wife also wants to copy the pix to her computer and she may not copy for several weeks or months at a time.
I tried using aperture's import feature to copy files directly from my camera's memory card. The import worked, but when I tried to locate the files on disk, aperture told me there were no referenced files. Any idea where they are?
Problem #2 - import. Is there any way to make Aperture watch referenced directories and automatically add new files to the the appropriate project? It's a pain to keep manually importing files.
Problem #3 - Organization. Is there any way to set up aperture so that a project = a physical folder on my drive? I get that Aperture is trying to abstract the physical location of my files, but I don't want them abstracted. Also, why is my aperture primary library 6.2 GB when I do all my work with referenced files? Where are my edited files stored? Are these in the primary library? Where are the files from my photostreams (from my phone) stored?
Would any or all of these issues be resolved by moving to a managed file set up?
Finally, if I can't get Aperture working the way I need it, any insight into how I'd use it as an external editor to something like Picasa? I really like the aperture editing tools - that's why I bought it. But the workflow is just killing me.
Any insights would be appreciated. Thanks.It is not as complex as you are making it. Aperture is not per se an editor. It is for storing and organizing, and quickly decoding RAW images. It is a pretty good editor, but it has the feature to allow you to specify an External Editor to which you can send images for more complex editing, and back -- all from within Aperture.
You don't want to have your images referenced so you can also edit them with other programs. That destroys the non destructive design of Aperture. If you want Referenced images, you mostly want them so they can be on a different hard drive from that used by the Library for keeping track and storing the adjustments, and not so other programs can access them.
You need to read further as to how and why Aperture works the way it does.
Ernie -
I just want to migrate all of my work (all photos are referenced) from one drive to another and have my aperture library start working off of my new larger hard drive.
Depending on how your folder hierarchy is organized you might be able to do this with file->relocate masters and one of the options of folder organization that is provided but... if you have complicated hierarchy that Aperture will not reproduce then you can just copy all the entire folder hierarchy to the new drive using finder and then use file->locate masters to reconnect them to Aperture like this...
Aperture 3 – Locate Referenced Files « RB|Design
It's actually a bit easier if the old folder hierarchy/drive is disconnected when you do this for a few reasons.
RB
Maybe you are looking for
-
When I try to activate my imessage it keeps telling me that my username or password is incorrect.
I have changed my password several times, but it keeps telling me the same thing. I have logged into the apstore with it and it does it without botther. Pleas I need help
-
Initialize record type constant in package header
I am creating a package to hold application constants in Oracle 8.1.7.4. I want one of my constants to be a programmer-defined record type. A constant table type of that record type will then hold multiple records. I'm new to using record data types
-
When I plug in for charging battery then screen goes black for a moment?when i unplug it then same issue....please guide me how this matter solve it
-
I have lost my I pod devices and I can't find it anywhere what do I do??
I have lost my iPod 5 32 gb and I can not find it i have looked everywhere and had no luck what shall I do ??
-
Sorry for my bad english, I'm from Italy. I hope you guys can give me some help. Since the latest update my computer is freezing a lot after it stops/screensaver, and I have to shut the mac down everytime. I have an early 2014 macbook air, bought it