Aperture library sync over two machines?

Is there a way to sync aperture libraries over two machines on a LAN?
I am going to try aperture but I am not sure which machine to install it on.
I have a mac pro and a mac mini which I run side by side. I use my mac mini for email, and iphoto, iPad syncing and music and my mac pro as my main work machine for music production.
Ideally I would like to install it on the mac pro where I get the extra power and screen real estate but then I do not want to miss out on not having photos on the iPad. As the iPad syncs with my mac mini, I am torn between the two.
Does anyone have any suggestions on this matter?
It woudl be much appreciated.
Regards,
Felix

And that works fine unless you need both machines to have the library at the same time.
And it wasn't my point it was the OP's
From the first post:
I have a mac pro and a mac mini which I run side by side. I use my mac mini for email, and iphoto, iPad syncing and music and my mac pro as my main work machine for music production.
So for the orignal specs both machines required a copy of the library. 
Let's say in the middle of working on the Aperture library on the MacPro he needs to email an image to someone. Aperture will have to be shutdown, the disk unmounted and carried over to/cabled into the Mini. Just to send an email. Seems a lot easier to just have a copy of the library on the mini. The library on the Mini could even be a stripped down copy, no masters just the previews this way it makes it impossible to make changes on the Mini to images if that is a concern.
regards

Similar Messages

  • My Aperture Library is over 53gb!!!

    OK, I think this is odd. I have about 75,000 pics and store them on an external drive. My Aperture Library is on the same drive, but no pics are stored in the Library, just in the original location. Why would my Aperture Library be over 53GB in size??? Can this be reduced somehow??

    thats pretty accurate...one of my libraries is almost that exact size, (both image and library-wise). Keep in mind that the referenced masters are just the raw files (or whatever format you shoot in), but your aperture library is storing all information for metadata, thumbnails, additional versions, etc...so you're talking about information for 75k images.
    no need to reduce it as it is accurate. there is a thread about how rebuilding thumbnails has effectively made some libraries smaller by a pretty substantial amount (this is due to a fix in the 3.02 update as the prior version was causing thumbnails to take up more space than necessary). I would do this at your own risk however...i tried it on another library that was 6GB, and after the rebuild the library grew to 9.35GB, so best case scenario is you could wind up with a somewhat smaller library size, but worst case is you wind up with a much bigger library.

  • Why won't my itunes library sync over to my new ipad?

    I've recently purchase an ipad and am trying to sync it to my macmini.  It's copied over the iphoto library, but won't copy the itunes library over.  I've spoken to Apple twice today, the first guy told me that if I updated to the latest version of itunes then the sync would work (I updated, but it still didn't work).  The second person suggested doing a hard reboot, exiting, restarting, etc and then retrying but that didn't help either.  Any suggestions?

    Hi Nico,
    When you hook up the device to your Mini, and click on it, you should see the Device Profile with several tabs. Click on the Music tab and make sure it is set up to Sync your music.
    Cheers,
    GB

  • Best way to move the aperture library to a new machine?

    Hi Folks,
    This must be an FAQ I just can't find it.
    I've just got a new machine and want to move Aperture to it. I have backed up the vault to an external drive. I 'think' you would restore the library from that. Any advice from those who've done this already, would be much appreciated.
    Mac Pro   Mac OS X (10.4.9)   Quad-Core Intel Xeon 4GB memory

    What it won't do is copy across your preferences, presets and keyword lists...
    Preferences - copy 'your home folder'/Library/Preferences/com.apple.Aperture.plist to the same place on the new computer.
    Presets and keywords lists etc. - copy the entire 'your home folder'/Library/Application Support/Aperture folder across.
    If you used Migration Assistant these have probably been copied across already.
    Ian

  • RMI started but not communicated over two machines ......

    I installed jdk1.6 beta version on linux fedora core 4.
    and started RMI registry on linux.
    when we try to connect that application with the WinXP machine as using it as client and linux server, it gives us exception like
    root exception:
    i mean when we run project on two XP machines it works fine.
    but when we use linux machine as server , and XP as client
    it gives connection refused.
    and not worked ( not connected ) what will be the problem ???
    ================
    winXP -> winXP = working
    WinXP -> linux = not working
    linux -> linux = not working
    ===================
    and we have to do project in linux machine both server-client
    Hope
    for early REPLY from my dear friends.....
    experts

    There is no misconfiguration problem,
    becoz as we installed fedora core 4 ( select all packages)
    and still its fresh installation and we should not modified any setting over in fedora
    thanks... for your cooperation....
    be in touch.. i will send exact exception 2 u.
    thanks

  • Can one Aperture library draw from two iCloud streams?

    I have successfully configured Aperture to pull from the user's iCloud photostream.  I'd also like it to pull photos from the photo streams of my children.  I can add their iCloud accounts in System Preferences, but it only presents me with the options to use their address book, calendar, and mail.  Not the photostream.
    Anyone know how to do this, or work around it?  I'd love for the photos to stream in as they do for the primary account.
    Thanks

    only from one Apple-ID possible.

  • TM backs up Aperture library over and over again!

    Ladies and Gents; I look forward to your insight how this happens. Every time I work in Aperture, Time Machine backs up the whole library file to my Time Capsule(1TB), eating space like hungry dog.
    My aperture library is refrenced, so the actual pictures are stored in folders on the hard drive and Aperture only keeps the references. As I have some 15000 pictures amounting to some 40GB, the referenced library is 18.9GB in size.
    Even when I just delete some pictures (in Aperture) or do minor adjustments (create a version of a picture in Aperture) TM backs up 18+GB every time.
    For now, I have excluded the Aperture library from backups but would like to understand why this bug happens and how to avoid it. I have read somewhere that the latest 10.5.3 updated fixed this - but aperently not for me.
    My software is always updated and the iMac packed with power. Thanx for your time.

    I just did some reading on the forums and it appears that the issue happens when Aperture is running while TM runs backup. Subsequently, next time TM runs a backup while Aperture is not running it will back up the whole Aperture library all over again.
    At the same time some people suggested that 10.5.3 has solved this. Not for me, any ideas?

  • Unable to restore aperture library using time machine

    Aperture's UI was being barely responsive earlier today, and when I deleted a photo, it ended up actually deleting an entire album.
    So I close Aperture and go to my last Time Machine backup to restore my Aperture library. The restore is going perfectly normally, but it gets about halfway through and stops. It throws up a "You do not have permission to do that" notice.
    I've tried doing this numerous ways, including an actual "Restore" via Time Machine and also simply pulling the Aperture library off the Time Machine HDD via Finder. Same result no matter what I do.
    Help please! I'm looking at an icon of my Aperture library that has all my photos in it, but I cannot copy it!

    Thanks, MacDLS. I had checked the permissions under Get Info, but I don't remember an "ignore ownership" option. I'll look for it.
    The problem may be a corrupted HDD. After posting my question, I ran Disk Utility, and it was unable to complete a "Repair Disk" on the backup HDD. So I'm assuming there are some corrupted sectors.

  • Time Machine Suddenly Failing Caused By Aperture Library

    Starting about 3 days ago - my ever-faithful Time Machine backups started failing. The error was concerning running out of disk space. Ilet it try several more times and it failed every time. I started doing some research at this great resource http://pondini.org/TM/Troubleshooting.html and tried several things from the suggestions:
    1. Disk Utility repair
    2. Spotlight Re-index
    3. Manually deleting the "inprogress"
    4. Manually deleting a few older backups.
    None of them worked. Looking at the logs I could see it was choking on the Aperture library. I fired up Aperture and let it do it's thing - hoping it would repair whatever issue it had. Tried backing up again. Still  the same error.
    Next up - I excluded the Aperture Library from the Time Machine backups - and BOOM.... successful backup.
    My only problem now though is I REALLY want that Aperture library backed up  to Time Machine,
    Does anyone have any suggestions for fixing this issue?
    - thx

    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    If all you see are messages that contain the word "Starting," you didn't clear the search box.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • WebLogic domain spread across two machines

    Hi All,
    I have a weblogic domain that spreads across two machines. First machine hosts the Admin server, (BAM , SOA) managed servers and the second machine hosts the (APPs and FIN) managed servers. As you can see the managed servers hosts different applications and not related with clustering. I want to know in such a setup do we need to have separate weblogic installation on both first and second machines or just have WebLogic installation on the first machine and have the second machine reference the first's WL installation.
    What's the best practice.
    Regards

    I mean for a domain spread over two machines, I need to have weblogic installation on both machines and not just the one running admin server. I read somewhere WebLogic installations have 1 to N relation with domains. Seems like for a domain spread across two machines, two WL installations and two licences. Am I right?

  • Disconnect Large Aperture Library from FCP X

    Hi,
    I have a large Aperture library of over 200 gigs that takes over 10 minutes to load when I start FCP X.  I'd like to disconnect Aperture altogether from FCP X and then just save the few jpgs I need, when I need them to a folder that I can then pull the photos from.  How can I do that?
    Thanks,
    Don

    I experienced the exact same problem. I have a iPhoto Library in another volume (or partition) with very small free space, while main/system partition (Macintosh HD) has big enough free space.
    Turned out, the one that should have big free space is the volume/partition that contains original iPhoto Library (to import from), not the system partition. So, I freed up some space, reopen Photos app (while holding Alt key), and select the iPhoto Library to import. It works!

  • Workflow Questions - Same Aperture Library on two machines - Sync ?

    Ok, So now that 1.1 is out I copied my Aperture library to my new MacBookPro, updated to v1.1, loaded the program ... and Bam, my library is there and working perfectly (after the Migrate process).
    So now, I have my libarary on my Desktop Dual Power PC machine at home and also on my MBP in the field ... I'm in heaven!
    My question is this. If I make a bunch of updates to the library (adding new images, new projects, new albums, rating new and existing images, assigning keywords, etc) on my MBP while sitting at Starbucks or laying on the beach is there any way to go home and sync these changes with the library on desktop machine?
    I realize that if I do all my work on the MBP in a new Project and then export that project I can then import it into the machine at home ... but that only solves 1/2 my problem ... how do I deal with projects and albums that already exist on both machines?
    Copying the entire Aperture Library back and forth is an option but at 40GB and growing that does not seem like a lot of fun.
    Any ideas? Even a 3rd party app would be cool if it worked. Would something like ChronoSync see inside the Aperture Library container and deal with changed items?
    Thanks,
    A happy v1.1 MBP user
    Power PC G5, Dual 2 Gz, 3.5 GB RAM   Mac OS X (10.4.3)   MacBookPro, 2.16GHz, 2 GB RAM

    <...>
    My question is this. If I make a bunch of updates to
    the library (adding new images, new projects, new
    albums, rating new and existing images, assigning
    keywords, etc) on my MBP while sitting at Starbucks
    or laying on the beach is there any way to go home
    and sync these changes with the library on desktop
    machine?
    I realize that if I do all my work on the MBP in a
    new Project and then export that project I can then
    import it into the machine at home ... but that only
    solves 1/2 my problem ... how do I deal with projects
    and albums that already exist on both machines?
    Copying the entire Aperture Library back and forth is
    an option but at 40GB and growing that does not seem
    like a lot of fun.
    Any ideas? Even a 3rd party app would be cool if it
    worked. Would something like ChronoSync see inside
    the Aperture Library container and deal with changed
    items?
    <...>
    Aha! That (file sync) is exactly the first thought I had when I read your post (though I personally was thinking RSyncX, Chrono Sync may be easier to use).
    To many programs the Aperture library looks just like a directory, which it really is - Finder and a few other things treat is specially but usually the origins of file synchronization tools are more UNIX utilities that just see the Aperture library and projects therein as a series of directories.
    In particular, what you'd be looking for this tool to update are:
    * Import directories in exisitng projects with new images and updated sidecar/XML files.
    * Added folders and albums
    * (most important) new copy of the Aperture database.
    All of these things are just files so it should be very easy for the sync utilitiy to find they are newer on the laptop and copy them over.
    Now what will not work well with this approach would be to edit files on the laptop and the desktop at the same time, and then attempt to syncronize them - but if you are only using one at a time you should not have issues.
    I would make a small sample library in both places to test this approach against but I see no reason why it should not work.
    The only other approach really would be shuttling projects back and forth between systems, which you may have to do someday if your desktop library exceeds the capacity of the laptop.

  • Aperture in two machines sharing the same library... possible?

    I want to have one library which I could share between two machines (Ive got an iMac and a MBP). But I'd like to keep the library in iMac and access it on MBP over the network. I don't need use it simultaneously, but I don't want to use an external drive for it either... Any ideas? Thanks

    Ian, and others,
    I am maintaining multiple boot volumes on my Mac Pro, with the primary ones being one for Tiger and one for Leopard. At the moment I am separately maintaining Photoshop CS3 and Final Cut Studio on each of those. I have recently installed Aperture on that Leopard boot. I now plan to establish another Leopard boot (using a WD 750 GB drive), primarily for the pro apps such as PS CS3, Aperture and Final Cut Studio 2 (an upgrade) while maintaining FCS 1 on the other boot drive. With FCP, the projects and voluminous files are of course maintained on drives other than the boot volumes, and thus FCP, for example, can use those files whether I am in the Tiger boot, or the Leopard boot.
    I have been wanting to fire up Aperture while in the Tiger boot, to test some odd printing behavior, but don't want to create another Aperture Library (which is not yet populated to any real extent) just to do the test. Also, I would like to administer the Aperture Library from the planned new Leopard boot, but not create separate libraries if I should wish to use Aperture while in other boot volumes.
    It seems clear (but I could be wrong) that this can be done, but is it advisable? Practical? Obviously, with the separate boots, I would never be using Aperture from but one "computer".
    Ernie

  • Best way to share aperture library over network on two computers?

    I've read several posts about doing this and most recommend using an external HD and just hot swapping. However, is their not a better alternative? Can I not share my library over the network, or just remote connect to the other computer?
    Thanks for the help!

    Hi Terence and Leonie,
    You can run several Aperture on the same computer as long as all Aperture are using distinct libraries.
    What Aperture does is to create a simple lock file in <your Aperture library>.aplibrary/Database/apdb The lock file contains the PID of the process. So not two Aperture could open the same library (although I don't know how good they have manage the concurrent creation, locking, verification of this lock, this is a typical and difficult software engineering problem)
    Anyway, I have not said that Aperture supports concurrent editing. That a file is a database or a simple text file, you have basically the same issues on network or in concurrent environment. So if the folder structure holds simple, flat text file or xml object or databases, it is still a bunch of files (this is a UNIX system by the way ).
    Aperture contains more than one SQLlite file, there are some at the root folder, some under Database/apdb etc. there are also XML files that could be used as database.
    Anyhow, editing a file (SQLlite, XML, txt, doc, etc.) either on a share or locally is plain similar. The drive can fail too, although much less likely than the network.
    Network file edition can have a few shortcomings, but nothing that when known can be blocking.
    Locking files over the network can however be tricky and depends largely on the network protocol used (NFS, SMB/CIFS or AFP just to name a few). In addition, if you import files from /Users/foo/Photos in Aperture (without copying them within Aperture), they might not be visible from another computer or only the previews, as the path /Users/foo/Photos is not "visible" from the other computer.
    What really is a problem when you put a file not locally is the file system type and its features. HFS+ supports extended attributes (metadata), many other file systems support these but the API (how the software, such as Aperture, access this feature) might not be similar, in addition the amount of metadata or their structure might differ from file system to another. And this is where you might lose information.
    A tool like Dropbox is pretty good at maintaining the metadata across different computers, and it has been adapted to do so for OS X specifically (and also for Linux and Windows).
    The second problem is if you would have a Mac and share via SMB (the Windows share network protocol, aka CIFS on recent Windows versions) the library, SMB might not support the reading and writing of HFS+ metadata, thus data loss might occur.
    Apple is just warning us of all these shortcomings, and advise to use local storage formatted as HFS+. Because even a local external disk formatted as NTFS or other file system could be a problem.
    However, power users who understand the risks and limitations of a network share (in general) can create a disk image on a share (even if it is SMB). As for OS X, once the disk image is mounted, it is just like any other local hard disk, it is just "slower" especially latency wise. OS X supports perfectly disk image mounted on a share, it takes care of properly synchronising it.
    Of course, due to the nature of the link between the application data and where they are stored, in case of application or OS crash, the amount of data loss could be greater than when the data are held locally.
    I hope this clarify better my post.
    Note: another shortcoming of having it on the network is: Aperture lock the library by creating a file with a process ID. If the same library is opened from another computer on the network, this other Aperture instance might see the lock file and could perhaps not find the corresponding running process. This Aperture instance might then decide to ignore the lock and proceed with opening the library. This might have some consequences.
    But I haven't developed Aperture so I don't know how it would behave

  • Syncing Aperture library between two computers using MobileMe and DropBox

    I'd like to have my Aperture library automatically sync'd between my MacBookPro and iMac.
    I have MobileMe and I'd ideally like to use it to sync, however I believe Aperture sees the library as a large single file, and so is not really practical to do this.
    I believe DropBox does handle this better, but I only have the 2GB free version, and don't want to upgrade while I'm paying for MobileMe (which I use mainly for iPhone syncing).
    So, I was wondering would keeping the RAW and JPEG images in my iDisk (outside the library) and using a library in my DropBox folder using referenced master files to the images seem like a workable solution?
    I appreciate I need to only use one system at a time and make sure it's all sync'd before using the other computer or risk corruption.

    Just curious - why do you think it would be slow?
    With iDisk sync turned on the master images would be on the local hard drive, as would the library in the DropBox folder. Might have to use a symbolic link or mount to make the local hard disk iDisk folder appear in the exact same location on both machines, though maybe not even that?

Maybe you are looking for