メインコンテンツへスキップ

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Importing Aperture Libraries on NAS error.

Jonas Calhoun
Hello, I finished all the use cases I wanted to do with CP8 and my Aperture libraries, and decided to purchase it (a few days later 9 comes out, but I got the upgrade free, so no complaints).

Anyway, when I was testing everything, I had copied a bunch of my Aperture libraries to an external drive from my NAS in case something went wrong. Everything worked really well with the external drive, and now it's time to do the conversions on the libraries on the NAS. (this was with CP8, BTW)

However, every time I do (with CP9), I get an 'unable to read catalog file' error from CP9. If I copy the same Aperture library to an external USB, it works great. Is there something different about having the library on my NAS? It's connected using AFP, not SMB if that makes a difference...and I verified good connectivity, and the library is still good (Aperture still reads it). I'm also using Ethernet to connect, although I have the same issue on Wi-Fi. I deleted CP8 from my system, so I can't see if it had the same issue--all of the imports there were using the external drive.

Any ideas? I'd rather not have to copy *all* of my Aperture libraries to an external drive and convert them, then copy back to my NAS--for one thing, I'm worried I'd have to go through the 'locate' tool forever...

Thanks,
Dan
0

コメント

15件のコメント

日付 投票
  • Jonas Calhoun
    Further data points: Size isn't the issue. I just tried a library that only had a hundred or so images in it. Copying to the USB drive and importing, no problem. Leaving it on the NAS and importing does throw the error.

    Thanks,
    Dan
    0
  • Jonas Calhoun
    So now CP9 won't import any Aperture Library. Whether it's on my drive, the NAS, or a USB drive.

    I opened a support ticket a few days ago, but have yet to hear anything. I also re-installed CP8, and the same time--importing any Aperture Library gives a "unable to read catalog" error. No idea what's changed, but something has obviously.

    If anyone has any idea, I'd appreciate it.

    Thanks,
    Dan
    0
  • Andriy.Okhrimets
    How big is your catalog is all your files inside catalog are readable by your user.
    I.e can you open same catalog in Aperture on same machine without any issues?
    0
  • harald_walker
    I also have 8 and 9 installed but am still using 8 for my regular work until 9 has less bugs.
    I've been importing several Aperture libraries from an external disk (thunderbold raid drive) today without problems.
    Am also still using 10.10 and not El Capitan.

    Don't know if an installed version 9 could impact an older version 8. You wouldn't think so but since they seem to share the same application support folders, I wouldn't exclude it either.

    BTW, my migration process is always that I export projects or albums in Aperature as library with anything between 1000 and 8000 images. That's what I am importing in CaptureOne and I haven't had any problems with that approach. I wouldn't trust the full Aperture library that is years old and went through various Aperture updates.
    0
  • Andriy.Okhrimets
    Ok, so is it problem with specific catalog?
    0
  • Jonas Calhoun
    Thanks for getting back to me (I didn't check the forum for a few days).

    So I've gone through a battery of tests. Right now, I'm working with a small Aperture library (about a hundred images, 1.47 GB total size). Aperture reads it fine, whether it's on my NAS, a USB drive, or on my local system. But when I try to import it in CP9, I get the "unable to read catalog" error. The same error happens with any of my Aperture libraries, whether this small one, or a large one with 10k+ images.

    I opened a support ticket, but it was closed with "we don't support catalogs on remote drives", not understanding that my catalog is on my local drive, it's the imported ones that aren't (although now it looks like that's not working either). I've since re-opened the ticket, but I haven't heard anything back.

    I've also tried to export a project as a new library and import that just as a test...same issue.

    Versions:
    OS: Mac OS X 10.11.2
    CP9: 9.0.0.110 (f32d002)
    Aperture: 3.6

    Thanks,
    Dan
    0
  • Jonas Calhoun
    I'd like to try removing all traces of CP8 and CP9 just in case--just found the KB article on how to do it...so I'm going to try that right now.

    Thanks,
    Dan
    0
  • Jonas Calhoun
    Following the instructions at https://www.phaseone.com/en/Search/Arti ... nguageid=1 Didn't seem to make a difference.

    Thanks,
    Dan
    0
  • Andriy.Okhrimets
    It is worse to copy Aperture libray on same local disc before importing it in C1.
    0
  • twelvefingerjoe
    I've been fiddling around with C1 9 the last few days, and did all this copying back and forth on my NAS.
    Just guessing:
    is there an aperture process still running?
    Maybe the issue is a lack of user permissions on your server. did you log in with admin rights?

    re remove c1: I use appcleaner, after that easyfind with searchterms "captureone" and "phaseone" to delete the rest, then log out and back in again, empty the trash. this will kill active .plists or deamons/processes.

    Right now, I found out that it's best practice to relocate your masters in aperture first, the location could
    be whatever mounted volume or local, but keep your aperture library locally. No double files, both programs share
    the same folder. import from NAS then worked for me. learned a lot here:
    0
  • Jonas Calhoun
    Again, thanks for the responses. No aperture process that I could see running--I did a fresh reboot just to make sure. I do have admin rights (It did work in CP8 when I was trialing it, it's after I bought a license key that it's not working). I use managed aperture libraries, so nothing to relocate. I'll try app cleaner just in case.

    What exactly does this mean?
    It is worse to copy Aperture libray on same local disc before importing it in C1.


    Thanks again,
    Dan
    0
  • Jonas Calhoun
    So looking at that link, that's just exporting the images and importing them to CP9. That works. What I was hoping to use was the built in tools of CP9 (File->Import Catalog->Aperture Library). With the amount of images I have, it'll be a genuine pain to export and import all of them.

    Thanks,
    Dan
    0
  • twelvefingerjoe
    Not sure if we're using the same terms here:
    managed: images live inside the catalogue folder
    referenced: images somewhere else, this might be on the same drive, external drive or file server, but outside the catalogue folder
    as said, I had some trouble with accessing/copying aperture libraries on/from a NAS server, precisely the ones in Photos.aplibrary/Database folder. I haven't had time to check the issue, but I assume, user rights for those files are set to system, app only or wheel.
    when you keep the aperture catalogue on your system's drive and the images referenced somewhere else (e.g. on your NAS as well as on your system's drive), you might be able to use File->Import Catalog->Aperture Library, at least that did the trick for me.
    0
  • Jonas Calhoun
    I gave up. I'm now going through my Aperture libraries and exporting each project and importing into CO9. Tedious, but I'll get through it. There's only a few hundred photos that I want to revisit, so mostly this is just for cataloging purposes. It'll take a while, but I'll do it in my spare time.

    Thanks,
    Dan
    0
  • BeO
    Top Commenter
    [quote="Jonas Calhoun" wrote:
    I'm worried I'd have to go through the 'locate' tool forever...


    Just a quick side note: If you move referenced images outside C1 (in the Finder) than you have to "locate" images. But you can move the images from within C1 (select images then drag to the target folder in the library tool), references will be updated automatically.
    0

投稿コメントは受け付けていません。