apHUB is currently only available for registered beta-testers.
If you are interested in participating in the beta-program, please leave a message in the "Why do you want to join?" field on the registration page.
What is apHUB?
apHUB is a suite of Applescripts, that transform Aperture into your central hub for storing your images and sending their master (RAW or JPEG) with a single keystroke to other image editors (currently Capture One, DxO OpticsPro in development) and getting them back with full behind-the-scenes handling of the external settings and mask files. Thus the whole process is non-destructive.
With the combination of apHUB, Aperture and Capture One and/or DxO OpticsPro you have an integrated Photo management and editing suite that is far superior to any currently existing single Photo management application!
Head over to the videos category and watch the other videos!
You may want to know a bit more, what tasks apHUB is doing, when it sends pictures back and forth to Capture One or DxO?
Here's the big picture. I leave out some details, it would be too exhaustive otherwise.
Sending pictures to the external editor
Get the current selection of images in Aperture and loop through it.
For each image it does:
Find the path to the original (RAW, JPEG, TIFF etc.), referenced or managed.
Make a symbolic link from the original into the input folder of the external editor, name after the ID of the original in Aperture's database to keep track of where the image came from (thus the strange filenames in the video).
Check whether the image has already been processed with apHUB. In that case a ZIP file exists in the apHUB/Settings folder inside the Aperture Library.
Get the ZIP and unpack it to the correct place inside the input folder of the external editor.
The external editor sees the images in it's input folder and starts building peviews.
Sending pictures back to Aperture
Send the external editor a command to process/export the selected images.
As soon as the images occur in the output folder of the external editor, the Folder Action Script gets triggered and does all the hard work:
It either imports the processed image into Aperture as a new original or replaces the existing original.
It replaces only if the originals have already been processed with apHUB, original and replacement are of same image typ (TIF, JPEG) and you don't have multiple Output Recipes activated (in Caputure One). Otherwise it reverts to generating new originals.
The original filename is restored appended with text and index, flag, color label and keyword is set, if chosen in apHUB preferences. IPTC tags are restored from the original. Stacking is done if chosen.
It grabs the settings file and the local mask file in case one exits, puts them into a ZIP archive named after the ID of the original and stores the ZIP in the apHUB/Settings folder inside the Aperture Library.
Finally does some deactivating/reactivating tricks to get the apps to recognize any changes.
That all sounds pretty simple? But I can tell you, it took a lot of time to make this work reliably.