(Re) Locate 100's of files?
Hi--
I have a workflow whereby I download all pictures from my camera to a folder. I then review the images in this folder and toss the ones I don't want. After I prune the images I move them to another folder.
Recently I noticed that hundreds of the images in my catalog are offline. I see there is a Locate command...but this is not available on more than one selection.
How do I update the paths to all of these files at once? Generally, the locations for all these images are in the same, but different, directory as when they were imported.
I'll apologize beforehand for my next comment:
This was cake with Aperture 😉
thx
PP
I have a workflow whereby I download all pictures from my camera to a folder. I then review the images in this folder and toss the ones I don't want. After I prune the images I move them to another folder.
Recently I noticed that hundreds of the images in my catalog are offline. I see there is a Locate command...but this is not available on more than one selection.
How do I update the paths to all of these files at once? Generally, the locations for all these images are in the same, but different, directory as when they were imported.
I'll apologize beforehand for my next comment:
This was cake with Aperture 😉
thx
PP
0
-
WIth C1 locating single offline images is a nightmare.
You cannot filter or sort for offline images.
If you select an image, you cannot even figure out where the file is expected to be (it is not shown anywhere, not even in the error messages when trying to process an image).
But if you are lucky and easily find them (e.g. because they are in sequence), and you know or can guess where C1 expects them to be (or you look that up in the table ZIMAGE join ZPATHLOCATION in the database directly), then I could imagine the following:
- Move all offline images to the folder where C1 expects them to be. Do this with the Finder (outside C1)
- start or restart C1. The images should be online.
- Within C1, move them back to the desired folder. C1 updates their path info
Cheers
BeO0 -
[quote="ppmax" wrote:
This was cake with Aperture 😉
PP
Yep. But in CO, it is best to do all file operations, after import, from within CO and let it keep track of where the images are stored.
Or import to the catalog (Aperture's managed library) rather than referenced.0 -
Thank you for the replies...I was pulling my hair out before realizing there is no command to relocate files that have moved...then I pulled the rest of my hair out actually relocating the files one by one. Sheesh.
Most Mac applications keep a pointer to the file that is actually independent of the path. Aperture does this with referenced images; e.g. you can import an image into your catalog, then move the image to another location, and the path is automatically updated.
Maybe I should stop using catalogs and start using sessions...
Since I frequently see Bob in discussions about where to go after Aperture (C1, LR, etc)...I thought you might be interested in where I landed:
Back in Aperture. I do all importing, tagging, organizing, etc. using Aperture. For many well exposed pictures the image quality is still OK. When I want to achieve maximum quality I open my Aperture catalog, right click on an image to "Show in Finder" and then import that image to C1 (which is top notch for image quality in my opinion). I then export a tif, and dump that back into Aperture. I also use Iridient in the same way...it has better integration with Aperture. Although Iridient probably offers better tools for sharpening and noise reduction...it typically takes a bit longer to get where you want to go vs. C1.
Oh well, not perfect, but not a train-wreck either.
Anyways, thanks again,
PP0 -
If that's the route you want to take, have a look at apHUB (http://www.aphub.de). You'll need to signup to be on the beta list. apHUB is a set of AppleScripts that do what Bob described and they do it very well.
While I love C1's processing, I still prefer Aperture's DAM. However, I now need to move totally off of Aperture because Aperture is miserably slow at rendering and moving among EOS 5DSR files. It takes 8-9 seconds to render and apparently Aperture's pretty dumb about what it does for caching or something, because on both of my machines (16 and 32 GB of RAM), I can only move among a couple of 5DSR Raw frames before Aperture again has to "load" at 8-9 seconds. This is the first miserable performance I've seen from Aperture. Capture One does great on these.
Also, once you get the hang of C1's DAM, it really isn't all that bad. Yes, it could perform faster and allow more search (filter) criteria. And yes, it could be smart and store relative paths instead of hard links. I also wish C1 had the ability to embed IPTC data in the Raw file like Aperture does (I understand why P1 doesn't do this, but I'd sure like to be the one making the decision rather than Phase One!). But as I've grown more comfortable with C1's DAM, I'm pretty comfortable with it. Note that LR's DAM is also clunky compared with Aperture.0 -
[quote="BeO" wrote:
You cannot filter or sort for offline images.
I filed a feature request. The answer was that this is a good idea. Please join me and create a feaure request too if you also think it is a good idea.[quote="BeO" wrote:
If you select an image, you cannot even figure out where the file is expected to be (it is not shown anywhere, not even in the error messages when trying to process an image).
I have to correct myself. In v9.0.3 if you press "locate", the window caption shows the path and filename which is stored in the database. Maybe it was already there in v8.[quote="BeO" wrote:
WIth C1 locating single offline images is a nightmare.
What I meant is locating a whole bunch of single images is a nightmare.
The "locate" function for folders is buggy.
I have moved my whole Capture One installation (referenced catalog) from a windows notebook (catalog) and UNIX based NAS (to hold the raw files) to a windows desktop machine. I moved the top folder of my raw files from the NAS, and subsequently used the "locate" function for the top folder. (The catalog is now sitting on drive C and the raws on drive D with the identical folder structure on the new machine as on the NAS).
I now can confirm the "locate" function is buggy
Rougly the same images which I had offline last year where again offline this time! (last year I didn't notice it timely to precisely say which of my actions caused this).
I fixed it with SQL statements (using "SQLite Manager" addon for Firefox), replacing old path names with the new ones in the database directly, so the images are no longer offline. Then I had to "add" a lot of subfolders in C1 library as they were missing in the folder hirarchy.
The path and file names are quite long have "special" chars like \\servername . - etc., maybe that's it and maybe I can reproduce it on a smaller scale, if I find the time, and create a bug ticket.
Again, the locate function for top folders is buggy in windows v9.0.3 (and earlier), maybe due to long path names, special (but not too special) characters, or UNIX/Windows differences (or maybe some other reasons...)0
Post is closed for comments.
Comments
5 comments