Migrating Aperture Library to Capture One catalog
Hi all,
I've read all the posts and watched the videos on migrating from Aperture to Capture One, and I'm ready to give it a try this weekend.
I have two questions. My Aperture Library is about 30,000 images, I think, so I'd like to break it into small Libraries. How do I do that? My Library is 100% referenced files, broken into year folders, each of which has month sub-folders, each of which has day folders. So can I do separate Libraries by year or something? Or several years at a time?
Second question: Can I then "re-merge" the separate libraries into one or two big Capture One catalogs called "Aperture images" or some such?
Thank you!
0
-
[quote="MPekala" wrote:
My Aperture Library is about 30,000 images, I think, so I'd like to break it into small Libraries. How do I do that? My Library is 100% referenced files, broken into year folders, each of which has month sub-folders, each of which has day folders. So can I do separate Libraries by year or something? Or several years at a time?
You can separate it however you like. This is just to be on the safe side and avoid a common buggy behaviour by the Aperture Importer whenever it has to deal with bigger Aperture libraries.
In your case I would probably separate it by year. Just select the Year-Folder in Aperture, export it as a new Aperture library and import that into C1. You don't need to create new previews in the new library files, because these will be done by C1 anyway.[quote="MPekala" wrote:
Second question: Can I then "re-merge" the separate libraries into one or two big Capture One catalogs called "Aperture images" or some such?
Misunderstanding. You are already (usually) merging them all into one single C1 catalog (if that is what you prefer). You just do it year by year instead all at once.
Just go ahead, it's not that big of a deal. If something is not as you would like it, throw away the C1 catalog and do it again. By doing it year by year (in your case) you can already check after the first import process if everything lands in C1 as you expected and adjust your process accordingly.
Another recommendation from my side would be to repair the Aperture library before doing all of this (hold down Command+Option when launching Aperture)0 -
[size=150]Excellent. Thank you. Yes, I plan to repair the Library, back it up, etc., before I move import it into Capture One. Thank you!
[/size]0 -
i've just made the move from aperture to C1 Pro 8. to say that there've been a few mishaps along the way is an understatement. let me make it clear. i've invested a good part of a decade into maintaining my photo library with aperture, and i wouldn't be making the move if apple hadn't decided to abandon further development of aperture. what attracted me to C1 was the flexibility of the interface modules, the range of post-processing tools (much superior to aperture's) and the raw processing, which has made some of my old images sing with colour and finely-tuned tonal gradation.
having said all that, i nearly jumped ship yesterday and went back to my beloved aperture. this was because the transfer of libraries has proved so difficult for me. partly my own fault for poor strategy i think, if i'm honest. i had kept my library (about 900Gb), as 'managed' not 'referenced' by aperture, on an external 3Tb (thunderbolt connected) hard drive, with weekly backups to a further external hard drive, not perfect, but adequate for my current needs i think.
my transfer procedure went like this: in aperture, change all my photos from managed to referenced on the ext. hard drive. (as 'aperture masters/year/month/day') then from within C1 i chose 'import aperture library'. this procedure took about a day and a half of continuous processing, and the results were very hit and miss, with the aperture folder structure being mirrored in C1's 'user folder' tree with many many anomalies - photographs from venice wound up in an album of pictures of london architecture and so on. the other thing is that there doesn't seem to be the equivalent of aperture's 'projects' where the master images 'live', so that when i tried to move pictures back to where they should be, it just produced additional iterations or copies of variants, i would then have to go back to the other folder and delete the other iterations. so i was making the assumption that my imported folder structure in C1 would behave in the same way that it had before in aperture. it did not. the nearest equivalent of aperture's 'projects' is the folders where the masters are stored; referenced on the hard drive, or inside C1's catalogue (please correct me if i'm wrong about this). i deleted the aperture folder structure and tried again - another day and a half processing - same thing - inaccurate import. i think the problems sprang from the size of the library. my poor macbook pro was working flat out and at high temperature.
finally i decided on a different strategy. i imported my old library into C1, year folder by year folder, using the import dialogue for each year. i am now going to reconstruct my folders, projects, and albums, manually. this is no bad thing really, it will force me to 'clean house' of unwanted images, review my star evaluations, and maybe make some different albums, my pictures are all there, in chronological order, just not exactly where i expected them to be.
my apologies for the lengthy post. i suppose what i'm trying to say to my fellow (migrants?) is not to expect too much from the 'import aperture library' procedure, be aware that it's 'we're not in kansas anymore, toto' as far as DAM is concerned and be very careful about how you plan the migration, unless you only have very small aperture libraries to deal with.0 -
Same problem here. Have a large referenced Aperture library where the photos are nicely stored in the year/month/day subfolder structure on an external disk. After import to C1 using the offered import option (taking many hours), the former Aperture projects and albums are all there, but the file structure which should show up under "Folders" is completely wrong. What went wrong here? Do I really have to export in Aperture each year separately and then import it sequentially in C1? I have about 20 years of photos... Anybody has a better suggestion to achieve a smooth migration? 0 -
Hi Martin and everyone,
If you can believe it, I'm actually taking tomorrow (Friday) off work to do exactly this: break my Aperture Library into individual years and import them into a Capture One catalog.
If I'm still sane, I'll report back over the weekend!
Best to all!0 -
Hi all,
Well, it seemed to work. First I repaired permissions, repaired the Library, and copied it to a back-up. Then I split the original Aperture Library into five smaller libraries. Let's call them Aperture Library 1, Aperture Library 2, and so on.
I imported the 5 separate libraries into the Capture One catalog and all is well. Each Aperture Library is now a "user collection" in the catalog, so that's handy.
Now a question. Can I delete Aperture Library 1, Aperture Library 2, and the others? Were they just a temporary way-station, or are they somehow still necessary for the navigation of my files?
Thank you!0 -
[quote="Martin24" wrote:
Same problem here. Have a large referenced Aperture library where the photos are nicely stored in the year/month/day subfolder structure on an external disk. After import to C1 using the offered import option (taking many hours), the former Aperture projects and albums are all there, but the file structure which should show up under "Folders" is completely wrong. What went wrong here? Do I really have to export in Aperture each year separately and then import it sequentially in C1? I have about 20 years of photos... Anybody has a better suggestion to achieve a smooth migration?
I don't exactly understand your problem. You should accept, that the DAM of C1 is not as comprehensive and clever like the one in Aperture, so it is currently NOT possible to recreate the exact same structure of Aperture inside the C1 catalog. What the importer does is convert everything to the closest equivalent. For example, the old Aperture rule, that every picture HAS to live in one project only, but can NOT live in multiple projects is not the same in C1. C1's "projects" are more something like Apertures "Albums". The C1 catalog is more like one single Aperture project, which you can view when you click on "All Images". Smart Albums do not work the same way, as you can not openly choose the source of your smart album query like you can in Aperture and so on.
Be happy when all your images are transferred and the structure ROUGHLY represents what you had in Aperture.0 -
I don't exactly understand your problem.
well the problem is that importing a very large aperture library in one go doesn't work - photos turn up in the wrong folders, folders turn up in the wrong sub-folders and so on. once this has happened, because of the nature of how 'projects' and 'albums' work in C1 it isn't possible to move images around by dragging them to their correct folders because the images are not moved just duplicated making more mess.C1's "projects" are more something like Apertures "Albums".
i don't think this is quite right. clicking on a C1 'project' doesn't show any images, and you can't drag individual images from the catalogue or externally referenced folders into projects - you have to make albums inside C1 projects first. C1 user projects are really more like folder groupings in aperture. but, as you say, you have to accept that DAM is completely different in C1. i was very disappointed by the aperture library import feature. it was very time consuming, frustrating, and ultimately i had to abandon it, and go for a much more reliable, and faster, folder by folder manual import.
on a positive note, now that i've got my head round what works and what doesn't in C1's DAM features i can go forward. C1's other features; RAW processing and image manipulation/editing have made the move more than worth making.0 -
i said clicking on a C1 'project' doesn't show any images
sorry, i should have added projects don't show any images until albums inside projects have been populated with images.0 -
Would it be possible to go back to my question?
Well, it seemed to work. First I repaired permissions, repaired the Library, and copied it to a back-up. Then I split the original Aperture Library into five smaller libraries. Let's call them Aperture Library 1, Aperture Library 2, and so on.
I imported the 5 separate libraries into the Capture One catalog and all is well. Each Aperture Library is now a "user collection" in the catalog, so that's handy.
Now a question. Can I delete Aperture Library 1, Aperture Library 2, and the others? Were they just a temporary way-station, or are they somehow still necessary for the navigation of my files?
Thank you!0 -
Actually, I think I have to do it all over again. I've just found hundreds of images that Capture One says are "unavailable or corrupted."
And many of my old JPGs are "read-only" (i.e., adjustments are grayed out) for some reason.
So this didn't really work. I guess I'll try again, but that was disheartening. Does anyone know why the adjustments on SOME -- not all -- of the JPGs are grayed out? I had "edit JPGs" checked in "preferences" before the import.
Also, the new larger catalog is much slower to open and slower to navigate. Maybe I won't try the import again . . .
Too bad.0 -
i didn't have any of those problems with jpegs. however i did import in a different way if you want to try. first, in aperture, i converted all my master images from 'managed' to 'referenced' - i didn't divide the library into smaller libraries, but had aperture organise the referenced files in to year/month/day folders. i imported each year folder manually without using the 'import aperture library' command, but C1's import dialogue. it seems to have worked perfectly for me, although i now have to reconstruct any albums i had in aperture. you might try doing it that way. no guarantees of course. other than that, i would open a support case with phase one. 0 -
Hmmm. Thanks. I use referenced files as well. If you import that way (your way) do the images come across with adjustments or are you just importing the "originals" (or "masters")? Seems to me that if you import that way, the adjustments wouldn't come over. 0 -
[quote="MPekala" wrote:
Hmmm. Thanks. I use referenced files as well. If you import that way (your way) do the images come across with adjustments or are you just importing the "originals" (or "masters")? Seems to me that if you import that way, the adjustments wouldn't come over.
they came over with adjustments, and with metadata. As you noted, C1 is quite slow opening - nowhere near as slick as aperture - but, the post-processing tools are working just fine. the other thing i should say, before the move i converted all my psd. files - photoshop files - to TIFF format. i also took the decision to take all my movies out of aperture, because C1 seems very picky about which movies it will recognise.0 -
[quote="EnderWiggins" wrote:
[quote="Martin24" wrote:
Same problem here. Have a large referenced Aperture library where the photos are nicely stored in the year/month/day subfolder structure on an external disk. After import to C1 using the offered import option (taking many hours), the former Aperture projects and albums are all there, but the file structure which should show up under "Folders" is completely wrong. What went wrong here? Do I really have to export in Aperture each year separately and then import it sequentially in C1? I have about 20 years of photos... Anybody has a better suggestion to achieve a smooth migration?
I don't exactly understand your problem. You should accept, that the DAM of C1 is not as comprehensive and clever like the one in Aperture, so it is currently NOT possible to recreate the exact same structure of Aperture inside the C1 catalog. What the importer does is convert everything to the closest equivalent. For example, the old Aperture rule, that every picture HAS to live in one project only, but can NOT live in multiple projects is not the same in C1. C1's "projects" are more something like Apertures "Albums". The C1 catalog is more like one single Aperture project, which you can view when you click on "All Images". Smart Albums do not work the same way, as you can not openly choose the source of your smart album query like you can in Aperture and so on.
Be happy when all your images are transferred and the structure ROUGHLY represents what you had in Aperture.
Well, I understand that the DAM of C1 is different from the one of Aperture. But I thought that in C1 under "Folders" the actual file structure of the photos on the disk would be shown. This is what happens when one imports photos the normal way. But with the Aperture importer the file structure shown under "Folders" gets garbled; it's somewhat sorted in a numerical way with all day 01 subsubfolders first etc., even though the folders on the disk are untouched of course. Will now have to do it the same way as "kened" suggested; i.e. import every year separately with the normal import dialogue and then recreate in C1 the former projects and albums of Aperture. Will be a lot of work...0 -
My main Aperture Catalog contained about 17000 referenced images, these are now split into two Capture One Catalogs of 9892 and 6480 referenced images. The referenced images were never moved; they are in the same place for all Aperture Libraries and for all the CaptureOnePro Catalogs
I see that CaptureOne Pro does not easily handle catalogs over 4000 images, and I will have to split them again.
In the Catalog with 9892 images, if I select "all images", click on an images and then try to browse images it takes about 63 seconds for Capture one to respond by scrolling the images.
The response time for a mouse click is also about 60 seconds, if it is function used for the first time since the catalog is opened.
In the Catalog with 6480 images, with all images selected, the time to respond is 23 seconds.
A combined catalog of 16372 images will have an extremely long response time, no point in even trying.
This iMac is reasonably powerful, it has a 2.66GHz Intel Core I5 with 4 cores and 8MB L3 cache, and there is 16GB of RAM and 200GB left on the hard drive, so this is not a machine limitation (unless one considers not having an SSD to be a limitation)
Although CaptureOnePro has data structures that can handle many 1000s of images, it seems that the algorithms are not time-efficient enough to handle catalogs over approximately 4000 images (depending on the user's tolerance for waiting)0 -
I have the same issues as Martin and Eric. All my ""01" folders are together without respect to the year, etc.
And response time is pretty bad. Part of it, I think, is that Capture One is still generating previews on some of my imported images. I'm hoping this will improve with time.
But I'm wondering about the long-term feasibility of deleting everything I imported and simply working with Aperture on all those files forever (probably not a good idea) or also putting those old files into Lightroom (which will exist in the future -- with all its downsides).
I really don't know what to do about all this . . .0 -
Sorry if I'm being dense, but I don't understand how importing the images directly from their original folders -- directly into Capture One and not through the Aperture library -- could bring them over with their adjustments. Doesn't Capture One have to talk to Aperture to bring over the adjustments? Aren't those adjustments in the Aperture library? 0 -
[quote="MPekala" wrote:
Sorry if I'm being dense, but I don't understand how importing the images directly from their original folders -- directly into Capture One and not through the Aperture library -- could bring them over with their adjustments. Doesn't Capture One have to talk to Aperture to bring over the adjustments? Aren't those adjustments in the Aperture library?
that's what occurred to me after my last posting. my metadata has been imported into C1, and i think the adjustments too. unless i'm deluding myself (which is quite possible π )perhaps C1 is reading the adjustment data from the XMP files? but i'm really out of my depth here.0 -
[quote="Martin24" wrote:
But with the Aperture importer the file structure shown under "Folders" gets garbled; it's somewhat sorted in a numerical way with all day 01 subsubfolders first etc., even though the folders on the disk are untouched of course. Will now have to do it the same way as "kened" suggested; i.e. import every year separately with the normal import dialogue and then recreate in C1 the former projects and albums of Aperture. Will be a lot of work...
Sorry guys, but you are either doing something completely wrong or you have a big misunderstanding of how C1 represents your images in the folder view.
Of course your should see the very same folder structure that you have INSIDE YOUR APERTURE LIBRARY after launching the Aperture Importer and choosing the Aperture Library as a source.
I highly recommend to check out the C1 Webinar re. Aperture-Migration by Phase One on their YouTube-Channel before you end up with a lot of manual work.
I have been migrating 27.000 images from Aperture into C1 and everything looks the same as in Aperture, except of course the stuff C1 can't replicate, like Smart Albums with selective sources.0 -
[quote="EnderWiggins" wrote:
[quote="Martin24" wrote:
But with the Aperture importer the file structure shown under "Folders" gets garbled; it's somewhat sorted in a numerical way with all day 01 subsubfolders first etc., even though the folders on the disk are untouched of course. Will now have to do it the same way as "kened" suggested; i.e. import every year separately with the normal import dialogue and then recreate in C1 the former projects and albums of Aperture. Will be a lot of work...
Sorry guys, but you are either doing something completely wrong or you have a big misunderstanding of how C1 represents your images in the folder view.
Of course your should see the very same folder structure that you have INSIDE YOUR APERTURE LIBRARY after launching the Aperture Importer and choosing the Aperture Library as a source.
I highly recommend to check out the C1 Webinar re. Aperture-Migration by Phase One on their YouTube-Channel before you end up with a lot of manual work.
I have been migrating 27.000 images from Aperture into C1 and everything looks the same as in Aperture, except of course the stuff C1 can't replicate, like Smart Albums with selective sources.
Of course I watched the Webinar - it is very useful! The import to C1 with the Aperture Importer indeed constructs the same structure as seen in Aperture - but this is in the "User Collections" section. This is in principle perfect.
However, it is my understanding that in the "Folders" section in the Library view, one should see the actual disk folder structure, where the photos are physically located. This one cannot see in Aperture. I consider this a great feature of C1, in that one has one one hand the collections with groups and projects, while on the other hand one can also view the physical folder structure on the disks. However, the Aperture Importer of C1 shows the sub- and sub-subdirectories in some numerically sorted way breaking the actual physical directory structure on the disk.
One could argue that one should thus ignore the "Folders" section of the imported Aperture library and simply work with the structures in the "User Collections". The only disadvantage is, that moving some of the original photos to a new location e.g. on another disk, will be difficult. In C1 one could do this by dragging the respective folders in the "Folders" section to the new location. With the generated strange folder structure, it will be extremely difficult to find e.g. all photos from 2010. Of course it is possible to locate them in the "user collections" with appropriate filters and then e.g. export them, but this is much less elegant as the drag and drop that C1 allows with properly imported folders...0 -
I fully agree with Martin, except for one point. It would be great if you could drag a folder to a new location in Capture One, but I think you cannot. You can move individual images (or select multiple images) to drag and drop, but I don't think we can move folders yet. I have long wished we could! 0 -
[quote="MPekala" wrote:
I fully agree with Martin, except for one point. It would be great if you could drag a folder to a new location in Capture One, but I think you cannot. You can move individual images (or select multiple images) to drag and drop, but I don't think we can move folders yet. I have long wished we could!
Yes, you are right - one can only move images to a new location within the "Folders" domain. I was also mistaken in assuming that C1 mirrors in "Folders" the real disk file directory structure. I tried this out with a simple test case. If the images are in a hierarchical folder/subfolder/subsubfolder... structure, C1 only keeps the the lowest level subfolder names and orders them alphabetically in the "Folders" section. At least that's what it does when you import a set of images which are located in a hierarchical structure and tell C2 to leave them in place in the import. This is a fundamental feature of C1 and not related to the Aperture importer.
This makes the "Folders" section much less useful than I thought. The lesson is that one has to import only single directories or directories with only on level subdirectories which are suitable named. Importing a two-level directory from Aperture with year/month/day year by year will not work. Thus if one wants to keep the year/month/day physical structure of the images on disk, one has only the option of importing them and not leave them in place but have them copied by the importer to a new location. Thereby one can specify in the subfolder dialog the year/month/day structure of the imported images. Then they will also show up like that in the "Folders" section. Alternatively, one can flatten the year/month/day structure using unix commands/scripts and rename the images to keep somehow the year-month-day info in the file name. Too bad.0 -
To be honest, I have trouble understanding why you guys care about the folders so much. I thought that by using a databased catalog like in C1 or in Aperture, you can set up your image organisation any way you like and forget about the one-dimensional organisation from the age of folders.
For 10 years long I have dumped all my images into a managed Aperture database and never had a problem with that. Moving them out into a neat folder structure was a matter of 20 minutes (which I only did because I don't yet trust C1's database, too many bugs). Now I dump them in a folder structure which I have set up exactly ONCE as an import preset. C1 imports them, puts them where they belong, Time Machine does the rest and I could not care less.
Seems to me you will be much more happy with Lightroom instead of C1, which is similarly obsessed with worrying about the folders like you are.0 -
[quote="Martin24" wrote:
If the images are in a hierarchical folder/subfolder/subsubfolder... structure, C1 only keeps the the lowest level subfolder names and orders them alphabetically in the "Folders" section.
Hi, you can avoid this confusing behaviour by clicking on the three doots next to the headline of the library tool and choose "hide/show folder hierarchy" or something similar (my OSX is in German). The folder structure displayed there is exactly the one on your hard drive where the images physically exist.
Regards,
Frank0 -
[quote="Frank.O" wrote:
[quote="Martin24" wrote:
If the images are in a hierarchical folder/subfolder/subsubfolder... structure, C1 only keeps the the lowest level subfolder names and orders them alphabetically in the "Folders" section.
Hi, you can avoid this confusing behaviour by clicking on the three doots next to the headline of the library tool and choose "hide/show folder hierarchy" or something similar (my OSX is in German). The folder structure displayed there is exactly the one on your hard drive where the images physically exist.
Regards,
Frank
Wow! Thanks very much for this tip! This is exactly what I wanted... You save my day!0 -
I did all this 2 month ago with an Aperture Library containing about 70000 pictures and wasn't happy with the performance of the Capture One database either. Plus I've really missed a couple of things that I loved in Aperture like, handling of Raw/Jpeg pairs (very important for me), geotagging/maps view and the integrated book tool.
No question the Raw converter and the edit tools in Capture One are much better than in Aperture.
I realized I need the DAM part of Aperture and the edit part of Capture One in one app.
As this is unlikely to happen, I've decided to create my own hack to marriage both. π
The result is a suit of Apple Scripts, that allow me to send one or more pictures (RAW or JPEG) over to Capture One with a single keyboard shortcut like cmd+alt+C, make all edits in Capture One including local adjustments and send all pictures back to Aperture with another keyboard shortcut like cmd+alt+A. They automatically vanish from Capture One after the transfer.
The nice thing is, that all adjustments done in Capture One are saved inside the Aperture database, so when I sent the edited pictures again to Capture One, all edits are there including any masks. I even can make further adjustments in Aperture on top of pictures that were edited with Capture One, like final cropping etc., and when I later make further edits in Capture One to that picture, the on-top edits in Aperture are automatically applied to the picture I've altered in Capture One.
Another real advantage when using the suit is, that I can store the result of my edits in any format/resolution Capture One can export, even a tiny 0.1 MP thumbnail, but I have the full resolution of my RAW with all my edits, when I send this thumbnail again to Capture One (in fact it sends the Master (RAW or JPEG) plus the edits to Capture One instead, otherwise this would be impossible). I've always hated it, that I had to deal with a 20 MB TIFF, just because I've used a plugin in Aperture to get lens correction or better noise reduction.
I've worked with 2 monitors already for years within Aperture. Now I have Aperture open on one monitor usually in the browser view and Capture One on the second monitor with the edit pallets, large viewer and minimalistic browser strip. The transfer back and forth is so fast, that I don't feel to be slowed down in my workflow in compare to my prior workflow, doing my edits solely in Aperture.
So my solution is to stick with Aperture for DAM and use Capture One for edits.
Btw. I've expanded the suit meanwhile to work with DxO OpticsPro as well. So when I think, DxO would work better than Capture One for a single picture, I send it over to DxO. I can even go DxO -> Capture One -> Aperture with a single picture and do edits with each. π
In case I step over another editor with a nice, new feature, I can easily add it to the list. It just has to offer it's edits in sidecar files.
All I can say is, that I'm very happy with that solution and currently have no more desire to migrate my Aperture database over to any other program.
Peter0 -
[quote="NNN635125278290404489" wrote:
............
I realized I need the DAM part of Aperture and the edit part of Capture One in one app.
As this is unlikely to happen, I've decided to create my own hack to marriage both. π
The result is a suit of Apple Scripts, that allow me to send one or more pictures (RAW or JPEG) over to Capture One with a single keyboard shortcut like cmd+alt+C, make all edits in Capture One including local adjustments and send all pictures back to Aperture with another keyboard shortcut like cmd+alt+A. They automatically vanish from Capture One after the transfer.
.........
Peter
Hi Peter, that's an intriguing solution and one which I might want to adopt. I had started this migration process with rusty Applescript skills, but they improved as I used that tool to clean up some Metadata and version name issues within my Aperture Llibrary.
Would you be willing to share your Applescripts either here, or as a PM?0 -
Not wanting to be the bad-message messenger, but sticking to Aperture is risky on the long run (and perhaps short term too). If it does not run properly on OS X El Capitan, Apple is probably not going to fix it.
But if it does run on the next OS X version, you get an extra year in your Aperture life! π0 -
[quote="Eric Nepean" wrote:
[quote="NNN635125278290404489" wrote:
............
I realized I need the DAM part of Aperture and the edit part of Capture One in one app.
As this is unlikely to happen, I've decided to create my own hack to marriage both. π
The result is a suit of Apple Scripts, that allow me to send one or more pictures (RAW or JPEG) over to Capture One with a single keyboard shortcut like cmd+alt+C, make all edits in Capture One including local adjustments and send all pictures back to Aperture with another keyboard shortcut like cmd+alt+A. They automatically vanish from Capture One after the transfer.
.........
Peter
Hi Peter, that's an intriguing solution and one which I might want to adopt. I had started this migration process with rusty Applescript skills, but they improved as I used that tool to clean up some Metadata and version name issues within my Aperture Llibrary.
Would you be willing to share your Applescripts either here, or as a PM?
Hi Eric,
your welcome. Head over to http://www.aphub.de, first watch the videos. If you like what you see, read the intro and installation manuals and if you want to try it, register as a beta-tester. I recommend to test it on a copy of your library. Γ°ΕΈΛβ°
Peter0
Post is closed for comments.
Comments
33 comments