Aperture 3.0.3 released

http://support.apple.com/kb/DL1040
Has anyone had the opportunity to see if this fixes any graphic bugs?

Yes, it does have similar issues. However, I am not sure about reverting to 10.6.2, though if you should still have problems, it would be worth posting to help others.
To reinstall, take the SL Retail DVD from the shelf next to your FULL BACKUP EXTERNAL DRIVE (HINT) and run the DVD in the computer. 10.6 will reinstall over 10.6.x Then do the combo 10.6.2 update (and other non OS updates like printer drivers, itunes, etc..) and turn off automatic software updates in system preferences to avoid a mistake in the future. The computer will automatically look for updates upon your reinstall, make sure to uncheck the MacOSX update check mark to avoid doing this again.
Feel like a windows user? I do.

Similar Messages

Plugin to import Aperture librairies does not release the memory used by the librairy after the import is completed

Let suppose I import a 30GB Aperture Library into LR which is on my HD. After the importation, if I send the imported library to the Trash and clear the Trash the disk space is not released by LR. So after a few importations I get the message that I do not have enough space on my HD to copy another library on the HD from an external drive which contains many Aperture libraries.

Casita17, I recommend you evaluate ssprengel's questions and advice. Please read the following below, as we don't want you to lose images! I fear that you may be using a "referenced" library in Aperture, and this is the reason your disk space is not being released. I would NOT RECOMMEND breaking your library into pieces for now. You may very likely lose critical linkages, especially in albums. If you have a number of Aperture libraries to begin with, then never mind. Just be aware, Lightroom users generally recommend using only one lightroom catalog, which it sounds like you're doing.
Lets forget your system drive for now. Do you have two times the disk space on your photos drive? If not, do you have another drive laying around with as much space? I recommend you make a backup before you continue.
I'm not quite sure what approach your are using, but I think the root cause of your dilemma exists because of how Aperture and Lightroom manage and store your images. It may help to post what actions you take, step by step, and include the error messages.
You may already know some of these concepts, but lets leave no stone unturned.
First, Aperture uses "libraries", which contain all metadata and previews. These images may be stored within the database (managed images), outside the database (referenced images), or a combination. Can you apply a filter to your all photos selection, and tell us how many managed and references images you have?
Please read this for a better explanation:
http://www.lifeafterphotoshop.com/managed-vs-referenced-files-in-aperture/
Second, Lightroom's catalog is like an Aperture library. Only ALL images are stored externally, "referenced" in Aperture parlance.
You should be able to create the Lightroom Catalog on any drive. However, where you eventually store your images depends on what options you choose in the plugin when importing these images.
Any "managed" photos in Aperture WILL BE copied to the location you specify in the plugin. Any "referenced" files MAY OR MAY NOT BE copied to the location. They may be copied, or they they may remain in place, depending what options you select in the plugin.
Not sure I follow where you have your aperture library, images, and where you eventually want to store your Lightroom catalog, and where you want to store your lightroom images. I'd suggest not breaking up your Aperture library.
If you are short on disk space, I suggest making a backup. Then, select all photos and change them from managed to referenced, which will relocate the photos from within the library, to outside the library, preferably on the same drive. Then, create a Lightroom catalog, wherever you have room.
Run the plugin and choose the option NOT to copy the files. This way, it will leave them in place on your photo drive. Some images may be copied to the lightroom masters destination any way, so you may want to choose another location on your photo drive in the plugin import options anyway.
When the migration finishes, you can delete the Aperture library, which will not remove all that much, and will not make much more space available. And do NOT delete the image location you designated in Aperture, because you'll now be using it for Lightroom. But this way, you'll be able to keep your space usage under control.
But KEEP your backup, even after the migration, JUST IN CASE!

Aperture 1.1.2 released!

Definitely available via Software Update, fixes stability and performance issues.
Certianly seems to speed things up....
Jez

After upgrading to Aperture 1.1.2, the application crashes on startup. Rebuilding the library doesn't address the crash issue but since a rebuild forces Aperture to launch with all projects and folders closed, I am able to better focus in on the source of the problem. The problem seems to be in the latest project I imported. Fortunately, I still have the images on my Flash card, so I will try to delete the project and recreate it.
My library has approximately 65 projects and 6000 images (~100Gb). The images in this library have been acquired from a Canon 5d.
I will continue to troubleshoot the problem and report back but I wanted to post this as a warning to anyone looking to upgrade.
Thanks.

Breaking news - Aperture 3.01 just released!

Says' Improves stability and addresses number of issues....upgrading, memory etc etc
Sounds good! When it works Aperture 3 is a great upgrade. Let's hope this solves the many problems that had various 'workarounds' - so more people can enjoy using it!

There's a sticky at the top of the page and a good half a dozen threads on the subject already...
Ian

Open letter to Aperture developers

Since I guess this forum is monitored by Ap developers, I thought I could use it to tell them (and every Ap user) my opinion as a pro photographer who has been using Aperture since its first release.
The point is why we all are using Aperture instead of - for example - photoshop?
The answer is pretty simple. Aperture is intended to speed up the workflow of photographers who have to deal with many thousands images, and I might assume that this is the only reason for the most of other photographers out there. If we should adjust only a dozen of images there would be no difference between using Aperture or another photo editor app, that would only be a matter of preference.
So let's be honest, Aperture is VERY SLOW, and it's not a matter of demanding hardware. I personally have a new 8 core Mac Pro with 16gig ram, latest video card, super hard disks etc.
I could enumerate countless problems into aperture but I will leave these for other threads in this forum.
I just needed to tell my opinion and ask everybody who deal a considerable amount of images his experience with Aperture.
Mine is very good to some point, but absolutely terrible in terms of speed and reliability.
Apple should seriously take into consideration this problem and improve Aperture in terms of speed and reliability.
Many of you may ask why I don't switch to LR. Because I am too used to aperture and getting used to LR would result in slowing down even more my workflow.
However if next Aperture version will not be much better than it is now, then I (and I think many others) will switch to some other app.

Since I guess this forum is monitored by Ap developers,
It's not. The forum is for Aperture users to help other Aperture users. It's all explained when you joined.
Aperture menu -> Provide Aperture Feedback is the route to them.

When going from Aperture 2 to 3 and managed library to an existing Aperture 3 referenced

I am having to move several 2 TB Managed Aperture 2 Libraries to a new drive because the drives they are on are full and cannot be upgraded. I am copying them over to a new 4 TB drive and can either export the images out of the managed Aperture 2 Libraries or should I, once they are on the new drive, upgrade the "Managed" Libraries to Aperture 3 then export the images. I have been using Aperture 3 for about a year and have about 7 TB of images in an "unreferenced" Aperture 3 Library which is where ultimately I want to be able to access the old images.
Also what is the best way to export them out to maintain the integrity of the "Project/Folder/Album" structure I use.
And finally, is there a theoretical limit as to how large the Aperture 3 "Unreferenced" Library can be? My Unreferenced Aperture 3 Library is almost 200GB's. I have about another 6 TB's of images to add once upgraded.
Thanks for your help!!

I have been using Aperture 3 for about a year and have about 7 TB of images in an "unreferenced" Aperture 3 Library which is where ultimately I want to be able to access the old images.
If I understand you correctly, you want to create a consolidated single aperture 3 library on your new 7TB drive.
And now you have a small aperture 3 library on that drive and want to add the images from several Aperture 2 libraries, that are now on a different drive, that is filling up, correct?
Also what is the best way to export them out to maintain the integrity of the "Project/Folder/Album" structure I use.
To keep the integrity of your old projectaa and albums, your edits and tags, without losing the lossless workflow, I suggest to import your old libraries as libraries and not to export the images from these libraries to reimport them.
I'd do the following for each of your Aperture 2 libraries:
Do you still have Aperture 2 running, along Aperture 3, or can you reinstall it? Then I'd run the Aperture First Aid Tools on each of your old libraries to rebuild them and to ensure that they are having no glitches. Do that in Aperture 2, if possible. To launch the First Aid hold down the key combination âŒ¥âŒ˜ and double click the Aperture 2 library. Then select "Rebuild".
Copy the rebuild library to your new drive.
Double click your Aperture 3 library to launch Aperture 3 on it and use the command "File > Import > LIbrary" to import the Aperture 2 library into the Aperture 3 library. This will maintain all your projects, albums, edits, metatdata tags.
Repeat for all your Aperture 2 libraries.
Before you delete any copy of your old libraries, check carefully, if they imported well. And check, if your backup of the old libraries is current, before you do the rebuild in Aperture 2.
Regards
Léonie
And finally, is there a theoretical limit as to how large the Aperture 3 "Unreferenced" Library can be? My Unreferenced Aperture 3 Library is almost 200GB's. I have about another 6 TB's of images to add once upgraded.
There is no limit to the size of an Aperture library, that I know of. For merging libraries by importng one into the other you will need plenty of free space. See this: Aperture 3.4.3: Release notes
Scroll down to the paragraph "A note on upgrading your Aperture library" at the end of the document.
It might be better, to distribute your combined library over two drives. 6TB on a 7 TB drive might be problematic, because the OS may occasionally more free space to perform repairs and rebuilds.

Full report on Aperture at PMA (include 1.1 features) up

I've just put up my PMA overview - as PMA continues I'll continue to go back and flesh out detail for things I may have missed (and expand the booth coverage with pictures). I think I've pretty well covered the 1.1 features though.
http://insideaperture.com/Site/Aperture%20PMA%20Overview.html
To keep in tune with updates, make use of the rss subscription from this page:
feed://insideaperture.com/Site/PMA/rss.xml
As I add new information to any section of the overview I'll announce it via that news channel.

Thanks for the info kgelner. But I am not sure I
agree with one of your conclusions. For instance,
Apple saying that third parties may provide custom
book sizes has nothing to do with opening up the API
for plugins. Custom book sizes could be delivered
without access to the API.
<...>
The thinking here is that if they expect custom third party books, that implies eventually publishing a standard for design of the books - as it stands now you can't be sure a custom book would work in the next version of Aperture (even just point releases like 1.1). I agree it's a bit of a stretch but published support in one area implies thinking of third party extensions which leads naturally to other areas.
You should note that the info on certification has
been on Apple's website for weeks.
Hmm, I had missed those before!
Come to think of it I still do not see the second level certification class for Aperture, I'll have to take a look.
Also of note, Josh Anon's Aperture2iLife program
already makes it possible to use images from Aperture
projects in all other iLife applications (except
iPhoto). While it would be good to eventually have
this capability within Aperture, I don't see this as
nearly important as say improved RAW decodes.
Will full resolution? I think it may only be using the large JPG thumbnails. Not that it makes much difference for most iLife uses.
All in all, it's my opinion that the work Apple has
done on Aperture addresses most of the legitimate
concerns voiced by users. Several photographers at
the show have called me after seeing demos to report
vast improvement in performance and RAW decodes.
That's great to get some other afirmations on the progress, I'm glad I'm not the only one who thinks so. The Apple booth is definatley pretty busy and the reaction has been very positivve - I think Apple is going to come away from the show with a positive reaction from a lot of people.
I am excited about the progress Apple has made in
only 13 short weeks. While they will never be able to
please all of their critics, Apple has at least shown
they are listening.
That impressed me as well! It seemed like in a short timespan they had added some impressive things, really key things too like the color meter, DPI support, and a very good plan for RAW decoder upgrades (which I'm sure had been in the works for a while before Aperture even shipped).

Aperture 3.3 libraries readable by Lion and Snow Leopard?

I have been running Aperture 3.1.3 under Lion and under Snow Leopard. We have family iMacs that, for what I consider very good reasons, we do not want to upgrade to Lion. Now there is Aperture 3.3, and this seems to have major changes. If I upgrade on my Lion Macbook to this new Aperture 3.3 will our older Snow Leopard iMacs still be able to view (and edit) the libraries? These iMacs run 3.1.3 and cannot upgrade to 3.3 without upgrading to Lion.

The Upgrade to Aperture 3.3 is a major new release. Aperture 3.3 requires Lion - MacOS X 1.7.4, and will only run on Macs with 64bit Intel Processors. If you upgrade to Aperture 3.3., your Aperture Libraries will be converted to a new format, that is incompatible with earlier Aperture versions. You will no longer be able to open these libraries on your older iMac. Sorry.
Léonie
Added: See the Technical Specifications: http://www.apple.com/aperture/specs
and the Aperture 3.3.1 release notes

Aperture Projects Disappearing out of the Library

Aperture 2.1 3C27
I have been using Apple computers for over 15 years and Aperture since it was released.
Some of my Aperture library today disappeared from the desktop. This has now happened on two different machines. On another occasion I was working on a library and there were 4 projects. 2 of the projects have disappeared from the library. This happened as I was transferring some images to an external hard drive. I have tried rebuilding the library and regenerating the thumbnails. I have also gone to "Show Package contents" and there are only two projects in there, so ontologically only 2 exist. This is disconcerting to say the least and has erased hours of work. Has anyone else had similar problems or know of a way to prevent this?
Jason

I have just had the same thing happen. I would say about 95% of my projects are missing!!! If I look at the default Library I only see about 5 projects when I know there are about 109 projects (correctly stated on the opening splash) and 5000 photos. It correctly sees over 500o images in the All Photos smart folder, but none of the projects or albums!
I looked inside the aperture library.aplibrary and the approject objects are there.... just not in the aperture!
I have added about 4GB in the last 2 days, and I did have a hard restart today, but have run onyx and checked permissions, all else seems to be fine. I do run this on a filevault account (no choice - work).
Help! what can I do?
Message was edited by: Daniel Gratiot

Upgrading Aperture to 3.6 for Yosemite.

I am on a late 2012 Macbook Pro and do all my photo work on it. I am very happy with Aperture 3.51. I would like to finally upgrade to Yosemite from Mavericks. I have held off due to the wifi and boot camp problems I have read about. Now with the latest realeas of Yosemite I would like to upgrade to stay current. Apple has taken Aperture of the App store and I can't find anywhere else I can get the update to Aperture 3.6. I am totally happy with aperture and if I need more I use photoshop. I have an extensive library of aperture files as I have been using it from day one. I do not want to or need to migrate to lightroom or any other App. If Aperture 3.6 was released for us people who want to continue to use it, why is it no longer available. I have never been so disappointed in Apple. I don'e want to use Photos and I don't want to loose adjustments to thousands of photos or spend the time to change them all to tiffs.
Is there anyway I can still get the update? I would have downloaded the update earlier but being incompatible with Mavericks it the App store wouldn't let me download it for future use. Please help if you can.
Harry Bergeest

Did you ever buy or update Aperture from the App Store? If you never did (if you only ever installed from CDs), then you may have trouble finding it in the App Store. I think there are a few threads in this site which work around that issue.
I was able to download Aperture from the App Store with my 10.10.2 system, but it wouldn't run until I upgraded to 10.10.3. I may suggest cloning your hard drive, then upgrading to Yosemite 10.10.3 and trying Aperture 3.6. If for some reason it doesn't work out for you or you can't get it from the App Store, wipe the drive and restore your Mavericks system from the clone.
But don't rush into it, because downloads from the App Store are still verrrrrry slow. It took me several days on a 50mbps connection to download 10.10.3

Aperture 1.1 and Olympus E-500 RAW files

Hi there.
My problem:
RAW data from my Olympus E-500 isn´t supported by Aperture 1.1
After importing RAW files there´s no image data and the preview displays "unsupported image format"
I wonder why, since that camera is listed in the compatibility list under http://www.apple.com/macosx/upgrade/cameras.html
Even if it is not listed in the compatibility list of apertures supported RAW filetypes, in my understanding aperture should deal with those files if the OS supports the camera. But this understanding seems to be wrong..
I know that RAW files can be quite different in structure, so files generated by the E-1 seem not to be the same as RAW files generated by the E-500.. even if they have the same files extension. But I wonder that even the E300 is supported but not the E500.
Does anybody knows if there is a workaround for this or if there is a chance to use Aperture with these files in the near future?
Thanks for any information.
G5 Dual 2.5 GHz, 4GB RAM Mac OS X (10.4.6)

I know that RAW files can be quite different in
structure, so files generated by the E-1 seem not to
be the same as RAW files generated by the E-500..
even if they have the same files extension. But I
wonder that even the E300 is supported but not the
E500.
You are indeed correct that the .ORF raw files generated by the E-1 and the E-300 are different from those generated by the E-500. Olympus must take the responsibility for this. I will assume that they had some good reason for changing the file structure between camera models, but I don't know what it is and have difficulty imagining what it could be. When the E-500 was released, there was considerable discussion about this on several forums (notably the Olympus SLR forum at dpreview.com) as there were several other software programs (sorry, can't remember which specific ones) that also had been working well with .ORF files from the E-1 and E-300, but did not support E-500 .ORF files.
Why Apple has not added support for the E-500 raw files is another good question, and I hope you've posted your request as feedback for the Aperture team. I am using Aperture and an E-1, and have been enjoying the combination ever since Aperture 1.0 was released. The raw conversions for the E-1 have definitely improved since 1.1 was released, so Apple knows something about .ORF files. I hope that you will also get to experience that (soon) when support for the E-500 files is added. I'm not aware of any workaround at this time, but will post here again should I come across one.
Let's hope that Apple has not simply assumed that all .ORF files are equal, and has not noticed that you have a problem.

Using Aperture with a Network Attached Storage (NAS)

Hi,
I would like to make my Aperture library accessible from severals Macs and for different users on these Macs --- not at the same time. The idea is that only one user from one Mac can use Aperture at a given time.
The basic idea is to install the Aperture library on a Network Attached Storage (NAS) --- either will all photos included or with all photos stored in a separated folder structure --- next to the library ("externally referenced masters").
The NAS I am planning to use is a QNAP TS 239 Pro II+, which will be attached to a Gigabit Ethernet network (to which all Macs are connected too). Following the reviews, the QNAP should be capable to deliver a read/write performance in the order of 70 Mb/s ... hence performance-wise there should be no problem.
I've read through various forums and found many messages telling that using Aperture with a NAS is not possible or at least not a good idea. The posts in the forum were partially a bit confusing; people were telling contradictory things. I also had the impression that the answers depend on the actual version of Aperture. Apple itself put in the release notes of Aperture 3.1.1 about Vaults: "Fixes an issue that could sometimes cause Aperture on a computer with Mac OS X v10.5.8 Leopard to stop responding while updating a vault stored on a network volume." Hence, it seems that Aperture 3.1.1 can work with a NAS ... at least it can use vaults that are stored on a NAS. On the other hand, it's exactly the topic of vaults where many people say that this does not work with a NAS ...
To clarify things, I try to get some clear and competent answers here. The questions are:
Can one store and use the Aperture library on a NAS (whose disk is formatted using a UNIX file system, e.g. EXT4) ?
If yes, does this work in both configurations: (a) with a library containing the masters, and (b) with a library with externally referenced masters (that are also located on the NAS) ?
If a user on a given Mac on the network has opened Aperture (and thus the library on the NAS), is this library the blocked for other users ? (That should ideally be the case.)
If it is NOT possible to use an Aperture library on the NAS, is it then possible to store it on an external, HFS+ formatted drive connected to the NAS via USB ? (QNAP allows to format its external drives with HFS+).
I know that putting everything on an iSCSI target volume on the NAS is a solution, but is iSCSCI properly working under OS X (10.6). I read that one has to install an iSCSI Initiator software first ... which is not from Apple itself.
What about Vaults: According to the Aperture 3.1.1 release notes, it seems to be possible to use vaults on a NAS ... is this really the case ?
Is usage of Aperture on a NAS depending on the file protocol used to transfer the data ? I read also that if one uses the AFP protocol (supported in a QNAP NAS) then everything's fine ... Is this the case ?
Thanks a lot in advance for any clear and correct answer!
Rainer

Can one store and use the Aperture library on a NAS (whose disk is formatted using a UNIX file system, e.g. EXT4) ?
Not reliably, no. You will encounter issues. You could use Mac OS X disk images on the server, mount them on a client, and work that way. Note only one machine can mount the disk image at a time.
If yes, does this work in both configurations: (a) with a library containing the masters, and (b) with a library with externally referenced masters (that are also located on the NAS) ?
(a) no (b) no.
If a user on a given Mac on the network has opened Aperture (and thus the library on the NAS), is this library the blocked for other users ? (That should ideally be the case.)
Aperture does no locking. There is a very high likelihood you will corrupt the library if you do this.
If it is NOT possible to use an Aperture library on the NAS, is it then possible to store it on an external, HFS+ formatted drive connected to the NAS via USB ? (QNAP allows to format its external drives with HFS+).
How would you be accessing it then? If it's over a file protocol (SMB or NFS or ...) it likely won't work.
I know that putting everything on an iSCSI target volume on the NAS is a solution, but is iSCSCI properly working under OS X (10.6). I read that one has to install an iSCSI Initiator software first ... which is not from Apple itself.
Right. There is no Apple-provided iSCSI initator. I don't know how well 3rd party initators work.
What about Vaults: According to the Aperture 3.1.1 release notes, it seems to be possible to use vaults on a NAS ... is this really the case ?
I've done vaults reliably for years using a Mac OS X disk image stored on the NAS, that I mount before backing up. I wouldn't do it "naked" (i.e. stored directly on the NAS).
Is usage of Aperture on a NAS depending on the file protocol used to transfer the data ? I read also that if one uses the AFP protocol (supported in a QNAP NAS) then everything's fine ... Is this the case ?
AFP might have a better chance than other protocols but... frankly... it's a bad idea. If you MUST share a library across many machines, use something like a Promise DS4600 (direct attached) and plug it into a machine when you're using it.

Upgrading to Aperture 3 on Mac Book Pro

When I try to open Aperture after upgrading to 3 I get the following error "Insufficient Disk Space"
"There is not enough free space on your Aperture Library Volume"
I have 28 GB available HD space left. Can anybody advise on how much space I need to open 3?
Thank you

Hi Ngiri
I don't think the issue is directly with Aperture itself. Instead, since you've just performed the upgrade to v3, the process is that of the once-only upgrade of your Aperture library file. Aperture v3 uses a newer file format than earlier versions.
How big is your Aperture library file? If you're unsure of where to find the answer, the file itself is most likely located at the top level of your Pictures folder. ie /Users/ngiri/Pictures/Aperture Library (If it's not there, you've relocated it elsewhere, so you probably don't need me telling you where that is... )
There's info about the upgrade process in the final section of the [Aperture v3.0.3 Release notes|http://support.apple.com/kb/TS2518]: 'A note on upgrading your Aperture library'.
Aperture temporarily uses extra space on your hard drive during the upgrade process. This is for the purpose of backing up critical library info and insuring the integrity of your data during upgrade. If you don't have adequate space on your hard drive to accommodate the upgrade, Aperture will display a warning dialog. You may need to move your library to a different hard drive with more space in order to upgrade it, and then move it back to the original drive when the upgrade is complete. Any space used by Aperture during the upgrade is released and made available to you again once the upgrade has finished.
Hope this helps...
Regards,
Gary

CAN'T CREATE VAULT!!! aperture 2 with mac os 10.5.4

hi! i cannot create vault from aperture 2 to external hd. usually with he older version everything works well. now when i click the menu vault in the bottom left also the window vault doesn't work fine. And when i create a vault in the external hd aperture doesn't leave me to update the vaults, doesn't leave to delete....
and the general usage of the aperture interface turns out difficult!
i use aperture since the first release and switching to the aperture 2 was a great experience but i wasn't expected to find this important function disabled...
thanks Matteo

this i my external hd. i tryed but creating a new vault (that appears in the hd) aperture crash (not shut down but doesn't work)
Nome : L_8
File System : Mac OS esteso (Journaled)
Bus di connessione : FireWire
Supporta Journaling : yes
Journaled : yes
Numero disco : 3
Numero partizione : 3

Aperture 3 Viewer Issues

Today I started seeing some issues with my viewer and viewer modes in A3.
I'm not sure if I've hit a setting and changed it accidentally or what, but right now when viewing just a single photo, its off center in the viewer, shifted right.
When I view in grid mode, some of the pictures run off the viewer to the right and I'm not able to access them. Can't scroll to see them, nothing.
I hope this isn't a bug.

I suggest you lodge a bug report. Here is a copy of the bug report I just lodged:
"Problem:
1. Photos previously imported into earlier versions of Aperture 3.0, 3.01 are now said to be an earlier version and so have to be re-processed. This is stupid.
2. If I'm lucky enough to see an image in the viewer, after it has been loaded, re-processed and then processed, it is represented as a kaleidoscope of pretty blue, red, black and other colours. These aberrations obscure the entire image or parts of it. Further, if I scroll to the next image, it becomes a mosaic of the previous image and the image I have selected to view.
Feedback / Commentary:
These problems began after I upgraded to the latest release of SL (10.6.3) and Aperture (3.02).
As a loyal user of Macs for the past 10 years, and Aperture since Aperture 2.0 was released, my whole experience with the move to Aperture 3 has been an unmitigated disaster. It took far too much tinkering to get Aperture 3.01 working and as soon as I was happy, along came 3.02 and now I'm back to square one. In fact, when I think about it, its even worse. In fact even worse than anything I had to deal with in Aperture 2.
This is has been and continues to be a huge disappointment.
Having read the discussion fora, the best advice I have seen is that I revert to Aperture 3.01 and SL 10.6.2. Are you kidding? Downgrade my software? Is that the best advice to hand. This is a shallow farce!
What the **** is going on with you people?
Please find it within yourselves to dignify a dedicated user with some acknowledgement of this post, or better still a fix for this debacle.
Regards
Luke Cornelius
For the record, due to the incomplete options listed in the tick box form below, my system details are as follows:
Model Name: iMac
Model Identifier: iMac6,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2.16 GHz
Number Of Processors: 1
Total Number Of Cores: 2
L2 Cache: 4 MB
Memory: 3 GB
Bus Speed: 667 MHz
Boot ROM Version: IM61.0093.B07
SMC Version (system): 1.10f2
Graphics / Display:
NVIDIA GeForce 7300 GT:
Chipset Model: NVIDIA GeForce 7300 GT
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 128 MB
Vendor: NVIDIA (0x10de)
Device ID: 0x0395
Revision ID: 0x00a1
ROM Revision: 3021
Displays:
iMac:
Resolution: 1920 x 1200
Pixel Depth: 32-Bit Color (ARGB8888)
Main Display: Yes
Mirror: Off
Online: Yes
Built-In: Yes
Display Connector:
Status: No Display Connected"

Aperture 3.0.3 released

Similar Messages

Maybe you are looking for