Latency in Aperture

I am running Aperture 1.1 on a G5 dual 2.GHZ tower, w/ 2 GB of RAM, and the original ATI Radeon 9600 XT w/128MB DDR SDRAM.
My issue and I've grown uneasy about using Aperture further because of this problem is the "spinning wheel of death" which seems to accompany almost any use of Aperture, including the simple act of ranking the images. Anytime anything, aside from merely moving through the RAW images in an album is done, I can expect and do encounter time delays of from 8 to 22 seconds each. When I attempt to envision what it will cost me in time/discouragement to even rank the most recent 4-5,000 images I've added to my Aperture files, I am overwhelmed.
I am trying, everywhere I can image on the web and locally, to locate an ATI X800 graphics card to see if that corrects this issue of latency. I also this morning, had 2 added GB's of RAM installed on the G5 and it accomplished absolutely nothing. I've been watching the performance of Aperture on the G5 using the Mac Activity Monitor and it shoots up the 100 to 104% range in CPU processing whenever any adjustments are input into Aperture.
Does anyone have any thing to suggest or recommend. I am told that I should be able to pick up the X800 card on Monday and see if that removes this issue for me.
My other alternative frankly, is to stop using Aperture and go back to my old method of using just PS CS2 and Bridge (or try their beta test version of their new processing application). I simply can't afford to purchase another, new G5 procesor.
I would appeciate any advice or counseling in regard to this issue? I'd be even happier if I knew this was effecting others as it is me and that I'm not alone in the stew pot. Apple isn't very forthcoming about the solution to my problem, other that to suggest that I try the new processor and graphics card.
Thanks for listening,
Bob

I am having the exact same issues, with a G5 dual 2.5 and 4 gigs of RAM.
After importing about 500 JPGs from a Nikon D70 (3002 x 2000), I just get the spinning wheel cursor when just trying to rate the images. How can Apple justify this type of performance when just trying to apply ratings to a 1.5mb JPG image, when the same machine can perform flawless editing using Final Cut Pro, 30 frames per second multiple video streams in REAL TIME, and with complex compositing, etc.? There are some serious flaws in the Aperture code that should easily be solvable.
There is a small developer named Hexcat that creates a rocket fast viewer called Viewit. It's a one-man operation, and his $20 application can open and rate tens of thousands of JPGs on a older G4 PowerBook with no delays at all. Of course, it's not even close to Aperture in overall features, but it shows that such basic functionality can and should be accomplished without ridiculous hardware requirements.
Apple, don't lose focus of core functionality requirements (speedy opening and rating of images that aren't even RAW being one of these primary functions) over anything else. To put it in real-life terms, those 500 images take an average delay of 10 seconds to apply the rating and move to the next image. That equals nearly an hour and a half just to sort and rate them!
Hopefully 1.1 will have significant improvements in more areas than just the lift and stamp tools...

Similar Messages

In "About this Mac" why are my aperture photos listed in "Other" vs "Photos"

After consolidating iPhoto pictures into Aperture Library - and having to rebuild library all photos are shown under "Other" in storage under About this Mac. How do I get photos back into the Photo section. I am sure this is why Aperture is running very slow. Aperture library is on a 500 GB external USB hard drive. Does anyone know how to get photos into the right spot in the storage.

sharon108 wrote:
After consolidating iPhoto pictures into Aperture Library - and having to rebuild library all photos are shown under "Other" in storage under About this Mac. How do I get photos back into the Photo section. I am sure this is why Aperture is running very slow. Aperture library is on a 500 GB external USB hard drive. Does anyone know how to get photos into the right spot in the storage.
Nothing in my experience would make me draw the same conclusion (that the reporting of your Aperture Library as "Other" is why Aperture is running slowly). You report that your Library is on an external drive connected via USB. Is this USB 2 or USB 3?
The consensus is to put your Library on your fastest (lowest latency and highest throughput) drive. This is almost always your system drive. If your Library does not fit on your system drive, you are advised to move some or all of your Images' Master from the Library to a second drive using "File→Relocate Masters". If you want help with these set-ups, post back.

Aperture - library management and external HDD question

Hi all.
I have just graduated from a point and shoot to a Panasonic GH2 (love it), and have now begun using Aperture 3 rather than iPhoto on my early 2008 MB Pro to manage my photos going forwards. Of course, I’ve now discovered that Aperture is quite the resource hog and so it’s upgrade time (darn, “have” to buy a new ‘puter!). I have a 2011 MB Pro (2.3Ghz i7 with 512GB SSD) on order and 8GB of DDR 3 arriving from Crucial. Since I have this brand-new-computer opportunity I want to make sure I’m organising things properly before I start transferring things across, and so have a few Aperture-related questions. (In case it’s relevant, I’m shooting in RAW+JPEG. So far I’ve been using RAW as master, but have since learnt it might be a good idea to import JPG as master and switch to RAW only when I need to make corrections, so I’ll probably do that going forwards.)
I understand that moving to referenced masters on an external drive might be a good idea and save me precious SSD-space. To that end, questions are:
1. Can anyone recommend a companion external HDD for Aperture and the 2011 MBPro? I guess either FW800 or Thunderbolt are the way to go. The Lacie Little Big Disk Thunderbolt might be an option but is this overkill for Aperture masters or would FW800 be sufficient. I’ve also seen the G-Tech G-RAID mini, Lacie Rugged – thoughts welcome.
Key requirements are a) as compact as possible, and b) bus powered.
2. What kind of performance can I expect if I go down this route? Is there going to be significant loading/processing delay whenever I switch to a new image?
3. How will Aperture cope with (eg) syncing photos to iPad / iPhone if the drive containing the masters isn’t connected? Put another way, are JPG renders saved in the Aperture library (i.e. on my MBP SSD) or with the masters?
Thanks in advance to anyone who responds!
Aljrob

Aljrob_UK wrote:
...I have a 2011 MB Pro (2.3Ghz i7 with 512GB SSD) on order and 8GB of DDR 3 arriving
...I understand that moving to referenced masters on an external drive might be a good idea and save me precious SSD-space.
1. Can anyone recommend a companion external HDD for Aperture and the 2011 MBPro? I guess either FW800 or Thunderbolt are the way to go.
...Key requirements are a) as compact as possible, and b) bus powered.
OWC (an excellent vendor) has the Elite Pro Mini hard drive that meets your specs:
http://eshop.macsales.com/shop/firewire/EliteALmini/eSATA_FW800_FW400_USB
Thiunderbolt drives are not mainstream yet but eSATA and FW800 both work well. The multiple connection methods of OWC drives allow very desirable flexibility when purposing/repurposing drives.
Note too that the MBP optical drive can be replaced with up to a 1-TB hard drive DIY or OWC will do it for you. That is what I am doing with my 17" 2011 MBP.
2. Is there going to be significant loading/processing delay whenever I switch to a new image?
SSD latency is orders of magnitude less than hard drives. Switching to a new image even fast hard drives with fast connectivity add significant latency delay. To avoid that what I do is leave (Referenced) Masters on the SSD until all editing is complete (which may be a few weeks). Only then do I use Aperture to change the Referenced Masters location from the SSD to a large external drive.
What kind of performance can I expect if I go down this route?
With Masters on the SSD and 8 GB RAM imports/exports are very fast and all Aperture editing is essentially instant. You will be pleased!
Suggested workflow steps for Referenced Masters:
• Use a FW card reader or MBP slot to copy to a file folder on the SSD (never directly into Aperture or any other images management app). With fast camera cards copy times are quick, but cheap slow cards can slow this step down a lot.
• Eject and physically disconnect the card reader.
• Back up that file folder on external drive(s).
• Only after backup is complete, reformat the camera card in-camera.
• Import images into Aperture from the file folder on the SSD.
HTH
-Allen Wicks

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

AGP Aperture.. What is it and where should it be set?

While messing with my new MSI video card today I came upon a good question.. what should my AGP Aperture be set at for best performance? Is it based on amount of system memory? Video card memory?
To refresh your memory I have:
AMD XP 1600 Processor
512 DDR RAM (2x256)
MSI Geforce4 ti4200 64MB 8X
Asus A7A266 Motherboard
30 GB Hard drive
Thanks!

(long post warning)
You've all got a pretty good understanding.
VGA memory on your card is used as required by the application FIRST (for textures, buffers, code, etc.). Key point - VGA memory is FAST - remember, in the case of a G4Ti4600AGP it's clocked at ~650MHz(DDR). (and in the case of the GeForce 5600FX, that's now 1GHz DDR II)...
AGP Aperature memory is used NEXT (for textures) if your VGA memory is full and the application requires more. The amount of memory available is as you set in the AGP Aperature setting in the BIOS.
The key point about AGP Aperature memory is that it is the portion of your _SYSTEM MEMORY_ that _can_ be allocated to be used as AGP memory IF required.
What's special about it, is that any access made to it (by the Video card) is done directly through the AGP bus without need for translation (i.e. without CPU intervention) - this makes using the aperature memory faster than using normal system memory. (but still much slower than the local VGA memory as seen above - eg. a P4 can use 400MHz DDR RAM - much slower than the VGA memory not even accounting for latency, AGP bus speed, etc.).
Finally, if after this your AGP Aperature memory becomes full, then the application must resort to using regular system memory - requiring CPU/Memory Controller intervention - and share with other components (PCI bus) also requiring access to the system memory. MUCH slower.
Setting a large AGP Aperature won't hurt you as it's only going to be used if your VGA memory is full - however, once used, it's taking away from your system memory. So, if you set your Aperature to 128MB and you only have a total of 128MB system memory installed....
If your VGA card has alot of memory (64MB or 128MB by today's requirements), then it's likely you won't need a large AGP Aperature as the VGA memory will handle the load. Still, suggested requirements is to set your AGP Aperature at either 64MB or 128MB (and if you've got the system memory to spare, than all the more power to you). If OTOH, you've got a small amount of system memory, you may want to remain conservative here - but it will still also depend upon the amount of VGA memory you've got.
Eg: in 3DMark 2000, there was the 64MB texture test - anyone running a 16MB VGA card with an AGP Aperature of 32MB could not run this test - even setting the Aperature to 64MB didn't necessarily mean you could run the test due to overhead - from the link I posted above:
Quote
AGP aperture must be more than twice the size of the desired AGP memory space. So, if you want 15MB of AGP memory for texture storage purposes, then the AGP aperture has to be at least 42MB in size.
The good news is that games today don't yet require this massive amount of memory, thanks in part to texture compression techniques, etc. - but who knows what the future holds (hence we're seeing cards with 128MB and now 256MB on board). A few more years down the line, and the technology will probably change altogether (I've already heard of the AGP bus being replaced).
(whew...I hope everyone understands better. This is at least my understanding of AGP Aperature - it might not be 100% accurate)

Ideal hardware setup for Aperture

Is there an ideal hardware setup for working with 18megapixel raw files in aperture? Of the three...graphics card, cpu and ram...which are the most important to processing the raw image.
I am running 10.6.3 on a macbookpro 2.2GHz core 2 duo, 4G ram and an Nvidia card with 128Mb of vram.
Overall it feels somewhat slow, about 10 seconds to load the full raw image on screen. Is that just to be expected? Any form of image adjustment usually switches to low res while adjustment is being made.
Thanks in advance.

A fast hard drive seems to be the most important thing now. The more I use Aperture, the more I appreciate the need for fast, fast hard drives! Open the activity monitor and monitor your disk activity. Monitor the IO - if you are constantly in the hundreds for the disk IO counters, you are IO bound (and more than likely it's your library database and preview thumbnails database).
For a laptop, the Seagate 500GB with the 4 GB of flash built in that it manages might be a good way to go. I just got one and haven't had a time to put it in my Mac Book Pro for testing. If it manages to put most of your library database in the 4 GB flash cache, you won't see near the performance issues as with a regular hard drive.
You could get a smaller SSD for your primary drive and to put the library on, then get one of the kits to remove the optical drive and put the hard drive in that bay. Reference your masters on the hard drive and that way you won't go broke buying a huge SSD. Gasp! I know, me recommending referenced files - I'm grudgingly coming around. Well, that and Aperture 3 has some pretty nice features for referenced files that are making me more willing to consider that kind of a setup, esp. when I look at the disk activity and constant fragmentation of the library and thumbnail database files. I'm seriously considering getting an SSD just for my library database and thumbnail databases and referencing the masters on my internal RAID.
Also others have recommended iDefrag and I can heartily recommend it as well if you stick with traditional hard drives. If nothing else, download the free version and run it - I'll bet that the two aperture databases for your library will easily be the most fragmented files on your hard drive, followed by the thumbnails themselves. SSD obviously doesn't have the latency issues of rotating disk so defrag isn't needed - indeed it would just shorten the life of your SSD with a bunch of unnecessary writes. If you do consider SSD, the only one I can recommend for the Mac is from Other World Computing/MacSales as it does internal garbage collection. Until Mac OS X supports TRIM, normal SSDs that don't do internal garbage collection will run fine for a while, then hit a performance wall that will make you want to go back to your hard drive
Anyway don't feel bad - until I started tweaking my hard drive setup, there wasn't a real speed difference between my MacBook Pro and my Mac Pro - want to talk about a real downer!

Can Aperture actively work w/ images on an external HD?

I assumed that Aperture could work in a distributed mode; ie, acitvely display, compare, & adjust files stored on external HDs, but it appears not- all files must be physically loaded on the computer's internal hard drive. Is this true? If so, seems like quite a shortfall.
I have a 60GB HD on my G4 Powerbook, but figured my two 250GB externals could tie in. Appears that I have to import & export projects, individual images, etc. to preclude stuffing my internal HD with every photo I want to readily access
If this is a dumb or over-asked question, I apologize in advance. Thanks,
Bob
G4 Powerbook Mac OS X (10.4.6) User since Apple IIe

Your intenal drive is SATA 7200rpm. That's a low latency, high burst rate capable solution .... and my gut call is faster than an external FW800 with 7200rpm drive (BTW, not all FW800 enclosures and chipsets give the same throughput).
I have to assume the guy at Apple was not referring to speed but the lack of hdd space available internal to a laptop. An AP library for a pro- / prosumer is going to be big. Mine was 145Gb last time I looked. Internal drives in a laptop can't compete on space and AP cannot span a library across multiple drives.
Compromise for speed and space..... Consider holding your library on the external drive, and exporting your current project to the laptop internal. Reset your preferences to point at an internal path/folder, kick off AP again and import the project. Putting your project back into the PRIME library is pretty much the reverse. (AP designers put this capability in place to support laptop users in the field while their library was back at the ranch.)
Hope this helps.

Aperture Updating Library... 126,637 of 6,959,575

Hello all,
I upgraded to Aperture 3.2.3 and got an unexpected "Recovering Library" when it first started. Well, it seemed to have worked, and I did some importing in Aperture. It also started doing facial recognition in the background. I let all the background stuff finish, and then yesterday I quit Aperture.
At that time, it popped up a panel/sheet saying Updating library... 1 of 6,959,575 (commas added by me). It had done Updating Library in the past so I didn't think much of it.
However, now, a day and a half later, it is only up to 126,767 of those nearly 7 million. It seems to be going at a rate of one per second. At this rate, it will take around 80 days to finish. Given that my computer is a MacBook connected to an external DroboPro, that means I'm stuck with a non-portable computer that I have to hope has absolutely no crashes nor power failures nor any other hiccoughs for three months. Clearly, this is unacceptable.
Does anyone have any ideas what's going on here and what I could do, please?
Thanks,
Doug

If you have not read and undertstood this, you should: http://photo.rwboyer.com/wp-content/uploads/2010/08/Aperture3Organization.pdf
This will tell you how to open the Library Package and determine how large your Masters, Thumbs, and Previews are.
Some other thoughts:
How full is your system drive on your MacBookPro? If it does not have between 25 and 30% free space, then that is the first thing you have to fix. Similarly, I assume that you have run Disk First Aid or Diskwarrior against your system drive, just be be sure that it is not, for any reason, hosed. From your comments about Lion, I would guess that:
-- Your OSX installation has real problems; problems that probably rate a visit to the Genius Bar; there should be one near you in New York.
-- Your Aperture rebuild may be having problems with latency - possibly because the catalog of your system disk is damaged or your Lion install is damaged. Couple that with the slow speed of the Drobo and things may be timing out. I will admit that this is a complete shot in the dark.
Assuming that your 2 TB Library is Managed, that is that the 2 TB includes your masters, and that you do not have 2 TB of free space in your MacBookPro, then:
-- First relocate your Masters out of the Managed Library and put them somewhere on the Drobo. There re many, many threads on this Forum discussing strategies for doing this.
-- Move the Library (now without Masters) onto your fastest, emptiest internal drive.
-- Resync everything. A quick pass with iDefrag wouldn't hurt after this much file movement.
Why lecture about backups?
-- Well, first of all you said that you had no backups.
-- Secondly, we are trying to diagnose a problem at a distance, on hardware that we cannot see. We can't really tell if your problem is with your Mac, Lion, the Drobo, or Aperture. Under those circumstances we could easily give really bad advice. The cyber version of the Hippocratic Oath (First, do no harm.) is to assure that backups are available.
Good luck and best wishes.
DiploStrat

Why aperture running very slow?

I just installed additional ram and the other day aperture was running extremely slow. The only other application was iphoto.
How much CPU power does aperture require?
thanks.

sharon108 wrote:
After consolidating iPhoto pictures into Aperture Library - and having to rebuild library all photos are shown under "Other" in storage under About this Mac. How do I get photos back into the Photo section. I am sure this is why Aperture is running very slow. Aperture library is on a 500 GB external USB hard drive. Does anyone know how to get photos into the right spot in the storage.
Nothing in my experience would make me draw the same conclusion (that the reporting of your Aperture Library as "Other" is why Aperture is running slowly). You report that your Library is on an external drive connected via USB. Is this USB 2 or USB 3?
The consensus is to put your Library on your fastest (lowest latency and highest throughput) drive. This is almost always your system drive. If your Library does not fit on your system drive, you are advised to move some or all of your Images' Master from the Library to a second drive using "File→Relocate Masters". If you want help with these set-ups, post back.

13 vs 15" Retina. Quad or Dual Core for Aperture and IMovie?

Does iMovie or Aperture take advantage of quad core? I'm debating if I should return the 13" Retina I just purchased for the 15". Thanks

A quad core will definitely allow you to stack more layers of instruments and decrease your buffer size (resulting in lower latency). I have a 3.06gHz core 2 duo 17" with 8GB RAM and a mate of mine has a 13" i5 with 4GB RAM and we compared how many synths we could cram into 1 patch before we got system overloads. My mate's i5 easily handled at least 60% more than my machine....I was blown away by how much difference the extra CPU speed makes.
If I were in your shoes, I'd definitely go for the quad core if you want MS to handle (just about) anything you can throw at it. This will also give you a few more years of use as plugins evolve and consume more and more processing power. That's one of the main reasons why I splurged at the end of 2009 and upgraded every "power" feature I could when I bought my current MacBook Pro.....I've easily gotten more life and use out my system than most users who bought the standard config at the time. I've also just upgraded to a 512GB SSD to get some more juice out of my machine to keep me happy for at least another year before I get a new MacBook Pro.

TS2518 Help, I had aperture open and working on a image and did not have a battery in and bumped the power off. As a result it will not open my master, it is locked. when I try to open that Library it says There was an error opening the database for the

Help, I had aperture open and working on a image and did not have a battery in and bumped the power off. As a result it will not open my master, it is locked. when I try to open that Library it says There was an error opening the database for the library. I have tried every thing. I updated the other libr but now it will not open the main to update. What do I do?

Try starting Aperture with the command and option keys held down. You'll get 3 options.
Try each, starting at the top, in order, checking after each to see if it fixes the issue.

A single photo in Aperture smart album shows multiple times on Apple TV2.

Sometimes a random photo in my Aperture smart albums displays on my ATV2 multiple times..can I fix this? For example, currently a single picture shows up on the Apple TV in the photos taken "in the past week" smart album 124 times, and the same picture shows up in the "in the past month" smart album 15 times.
When I double check the picture in the original smart album on the computer, it appears correctly, i.e. only one time.
Suggestions?

I'm having the same problem. I deleted all the photos in the photostream then tried to drag a couple new ones in to see if they'd synch. Nothing is happening. I recently installed aperture (have about 125 gb in the library). If anyone has an idea what to do, i'm open to try something.

Iphoto calendar is a mess, can we get a pro calendar in aperture?

I am making a calendar using the aperture library in iphoto and having lots of troubles.
When i have added the photos to their positions, i find that i need to edit some photos to fit their neighbours, and then having to close iphoto, open aperture and edit them, yet those changes fail to show up in the applied photos, so have to edit outside the project and replace the photos...
Also while working on this project my library is locked so i cannot open aperture without closing iphoto, even if i want to work on entirely different things, interrupting a normal day workflow.
When i reopen iphoto it has forgotten my position and just shows the full calendar again, forcing me to search again for the place the photo i have edited in aperture or to replace with another i have found that fits better.
The calendar templates are quite limited, on a few pages i wanted to place more photos or have other orientations which is possible when making a book, and the size of calendar is relatively small, could be good with a possibility of making professional calendars one step bigger.
Is there any way to tell apple that there are many who would need a proper calendar inside aperture, to be able to make professional products or who have migrated from iphoto being used to making calendars and cards and wanting to continue that in what should be a better program?
Even having the exact same calendar available in aperture would be huge benefit, and ensure many more being made!
Aurin R
Denmark

Is there any way to tell apple that there are many who would need a proper calendar inside aperture, to be able to make professional products or who have migrated from iphoto being used to making calendars and cards and wanting to continue that in what should be a better program?
That is what the command "Provide Aperture Feedback" in the Aperture Application menu is for: http://www.apple.com/feedback/aperture.html
How are you switching between Aperture and iPhoto? When I use the commands "File > Open Library in Aperture" and "File > open library in iPhoto" to switch back and forth between the application, the iPhoto will open with the calendar selected, when I switch back from Aperture, albeit not on the calendar page, that I last viewed.

Aperture No Longer Working With Screen Saver?

For years I've been using my Aperture library (specifically, the "Flagged Photos") with the Screen Saver in OS X. Since I upgraded to Lion last night, I have discovered that my Aperture library no longer shows up as an option in Screen Saver -- only iPhoto does.
As I am remiss to ditch years of work and return to iPhoto -- I was hoping someone might have discovered a solution for this problem (perhaps something to do with the iLife browser in Lion?).
Any help would be greatly appreciated.

Kluv32 wrote:
Then, I checked the new sharing preferences and closed out Aperture. I opened up the System Preferences for Screen Saver, and after waiting about 1-2 minutes, Aperture popped up in there as an option.
Can you please explain what you mean about "checked the new sharing preferences?" I see no way of setting any "sharing" preferences in Preferences or anywhere else in Aperture. Do you mean you just looked at the sharing preferences?
Since I've upgraded to the latest version, when I go to the System Preferences, Aperture is very slow in showing up on the ScreenSaver settings under System Preferences and the virtual Library folders no longer show up (they show up under the Desktop window though). However, after closing Aperture, the screensaver would display "looking for pictures" and would not display the photos.
The latest upgrade definitely broke something, although it greatly improved Aperture's response time, as it was getting pretty sluggish before the upgrade.

How do I get custom book themes to appear in Aperture?

I want to create two custom book themes in Aperture - A4 Landscape and A4 Portrait - so that I can print them on A4 photo paper. However, after creating the custom themes, they do not appear in the custom theme list which is preventing me from creating an A4 sized book. I closed and restarted Aperture and I have also closed and restarted my MacBook.
My Aperture version is 3.5.1 and I am running Mac OS X 10.9.1.
Folders for the two custom themes I have created do appear in Users/MacPro/Library/Application Support/Aperture/Book Themes.
Regards
Schof

Folders for the two custom themes I have created do appear in Users/MacPro/Library/Application Support/Aperture/Book Themes.
Schof,
I will try your suggestion of creating a new Aperture library and let you know what happens.
If a new library does not fix it, there is probably a permissions problem with your user library, or a problem with the "Books Theme" folder.
I'd try to trash the "Books Theme" folder:
Quit Aperture.
Delete your "Users/MacPro/Library/Application Support/Aperture/Book Themes".
Log off and on again.
Create a new Custom Book.
Can you now see it in the "Themes" drop-down menu?
If that does not help, trash the preferences as well:
Users/MacPro/Library/Preferences/com.apple.Aperture.plist
and log off and on again, or restart the system.

Latency in Aperture

Similar Messages

Maybe you are looking for