Aperture 2 is buggier than 1.5.6

Aperture 1.5.6 under Leopard (fully updated) was buggy on my PowerMac G5 with 6.5 GB of RAM and Radeon 9650. The Viewer blackout bug was especially annoying, prohibiting A-B comparisons of edits and slowing my workflow.
I bought the upgrade to 2.0, only to find that I could not update from my Academic license (real smart marketing, Apple) so I've been using 2.0 in trial mode.
The Viewer blackout bug is still present, with the "enhancement" that sometimes the Viewer window goes yellow instead of black. The underlying characteristic seems to be randomness. I can't predict when it will happen or what the screen will look like when it happens.
Worse by far, for usability, is that 2.0 becomes slower the longer the working session, then the cursed beachball starts appearing occasionally, then it's in my face every time I make an edit. So I quit and restart. At least quitting and starting is faster than with 1.5.6.
The slowdown comes on sooner and sooner with each restart of Aperture. After about three restarts the spinning beachball seems to last forever and I cannot start any other application, like Activity Monitor. That exhausts my patience and I kill my Mac by holding in the power button.
After restarting Leopard, the whole sequence of getting slower and slower repeats. I'm not a professional programmer, but the pattern suggests a severe memory leak, which eventually affects other applications like the Finder.
Why is it that Adobe can write image processing software that works on the Mac better than Apple? In fact, I have no reliability problems with any software other than Aperture, so the I don't have a hardware issue. TechTool Pro passes my Mac. I repair disk permissions frequently, using Disk Utility and sometimes DiskWarrior.
Although I have used Macs since the Mac Plus, persistent Aperture bugs through a major update combined with the upgrade-from-Academic crap is souring me on Apple. Who is supposed to know Macs better than Apple?
I love the Aperture interface and the results of editing images. I'm unhappy about not being able to update my Academic license for 2.0, but I planned to buy the full version anyway. However I would by nuts to "upgrade" to such a disastrous new version.
I'm curious why there are not more reports of the problems I'm seeing on this forum. Lots of people seem to be experiencing bugs, but different kinds of bugs. A few people have even posted high praise for the upgrade to Aperture 2, so they appear to have no problems. My Mac is completely stock, except for a Sonnet SATA card that is essential for managing the extra hard drives my photography requires, and no other software has problems with that card. Why does Aperture behave so differently on different Macs?

Thanks for your reply. I have automatic generation of previews turned off, share previews with iLife and iWork turned off, and use embedded JPEGs turned on. Aperture 2 works at reasonable speed for a while after starting, then slows down more and more with longer use. Then the Viewer blackouts start, with an occasional yellow screen instead of a black screen. The SBOD may start before or after the Viewer blackouts start.
Since my original post, only hours ago, I've also now seen the Viewer image appear upside down and distorted side-to-side (once). As with all the Viewer weirdnesses, the Viewer image looked normal again after restarting the application. As reported earlier, the SBOD and Viewer appearance problems increase in frequency after multiple restarts of Aperture, until I am forced to reboot my Mac.
I'd classify these abnormalities as bugs.
The Radeon 9650 graphics card was bought as an upgrade when I purchased my PowerMac G5. It is not the fastest graphics card, to be sure, but no other applications, including Photoshop CS3, have the least problem with it. Slowness is not the most serious issue I'm having. Having to restart the application repeatedly, then eventually reboot the OS, is the big issue.
The upgrade from Academic is not related to the problems I'm having with Aperture 2. As I wrote previously, I will pay for the full version - I WANT to buy the full version because I love Aperture 2 when it works - but I would feel like such a dummy to spend my money on an application that is so buggy that it interferes with my workflow. If anyone knows of a way to make Aperture 2 work on my Mac, I will be delighted to learn it.

Similar Messages

  • Can I use aperture library on more than one machine

    My situation is thus:
    I have a Macbook Pro on which my Aperture Library resides, in wherever Aperture decided to put it when I bought the software.
    I now have a iMac, which obviously will be better than the Macbook for photo editing.
    But I want to be able to take my Aperture Library with me when I take the Macbook out and about, and if necesary still edit on the Macbook.
    Is there any way to share the Aperture Library, so that I can edit on the iMac, but leave the library on the Macbook, and then edit on the Macbook if I wish.
    I am the only user, and will only be using Aperture on one machine at any one time.
    I have searched archives but not managed to find the answer.

    Is it possible to simply share the directory that contains the necessary file(s).
    If your Library is in the location that aperture picks by default, then it will be in your "Pictures" folder - look for a file with a name like "Aperture Library. aplibrary".
    What you will need to share depends on your import strategy for the master images. If you use managed masters, and all your master images reside inside the Aperture library, then you simply need to make this library file accessible  or copy it to an external disk.
    If on the other hand your masters are referenced, then I would recommend to consolidate them into the library before you share the library and then share the consolidated library.
    If you will share your library over the network or just by moving it to an external device is really up to you, but you might consider  the following pros and cons:
    - If you want to profit from the faster CPU on your iMac, then you should keep the library on the fastes volume that is available, and a network volume might be much slower than a directly connected volume.
    - if the network fails during a critical operation your library might get corrupted, if it resides on a network volume - there have been quite a few problems reported in this forum.
    That is why I suggested to use your Macbook as directly mounted external volume, that leaves the library in its place on the Macbook Pro - no need to copy - and you have a very quick and stable connection,  but the decision is yours to make. You will have to be comfortable with the workflow you choose.
    HTH
    Léonie

  • Aperture book quality - worse than before?

    Hello everyone,
    My photo studio has been using Aperture for 8 months now and we are very happy with it. We love the organization, web output, etc. We also LOVE the book design layouts, but the quality of the book printing has been degrading over that past few months.
    The first books we printed with Apple (around Nov/Dec 2006) were great, then about 3 months ago, we noticed the labels on the hardcover books went down in qulaity (almost like they were just using a color laser printer), and today we received five books in the mail and the quality is terrible. Also, two of the books have the "Made on a Mac" page in the back (like iPhoto).
    It seemed to me (since I have had books printed by both Aperture & iPhoto) that the older Aperture books were of higher quality than the iPhoto books. Now, it seems as though they are one-in-the-same and our studio cannot have this lower quality book - it is not up to our standards.
    I would gladly use another manufacturer, but every other design software out there for each respective company is terrible and takes three times as long for us to design a single book. I LOVE the integration of the books in Aperture and it makes our timeline two weeks shorter with our clients and that is what sets us apart from other studios in this town.
    Has anyone else had these problems or noticed the change/degridation in the quality of the books?
    Thanks!

    C'mon Apple,
    There is no way you don't know that the quality of your "sticker" covers is horrible. Maybe when you first launched your book service, but it has now been years. I just received three books, and all three have tacky, peeling front stickers.
    Please give us an alternative, even if it costs more, that allows us to show our work with pride. After spending thousands and thousands on computers, software, cameras, lenses, etc., the cover of the books drags that first impression into the ground.
    Thanks!

  • Aperture 3.0 slower than version 2

    Hi,
    I recently purchased Aperture 3 because of the new features which I think are really good. Furthermore I expected version 3 at lease a little bit faster than older versions.
    In contrary Aperture 3 is as slow as it can be! It regularly stops my entire system and I have to shut down Aperture to i.e. read my emails.
    The work with MobileMe galeries doesn't work at all. When I start Aperture I change the sorting criteria for my Aperture galleries and it always sets it back to "manual". I really don't expect that in a professional software.
    I don't have a slow machine running here. It's a late 2008 MacBook Pro with seperate graphics chip. It's always set to maximum power. But if running Aperture it's like working with my first G3 233 MHz.
    When does Apple finally release a software update which solves all the problems with Aperture? It is really annoying. I should have purchased Lightroom and not the all new Aperture version.
    Luckily I didn't have the problems with importing my Aperture 2 library.
    Thanks for your answers.
    maexer

    Aperture 3 is easily faster than version 2 on my 2008 macbook pro with 10.6.
    Are you running the latest aperture 3 updates and prokit updates? If not, run software update, if you are - go to the finder and move everything to the trash that is inside these folders:
    Hard Drive/Library/Caches
    Hard Drive/System/Library/Caches
    Hard Drive/Users/(Your user)/Library/Caches
    Also delete this file:
    Hard Drive/Users/(Your user)/Preferences/com.apple.aperture.plist
    Reboot... It will take a little bit. Report back if this works.

  • OBIEE 11.1.1.6 - less buggy than 11.1.1.5?

    Hi, we've been waiting to implement 11.1.1.5 for months now, but it's been so buggy and the patches so nonexistent that we haven't been able to go live. I'm just now starting to evaluate 11.1.1.6 - but curious to hear from others if you've had a chance to play with it, and if it seems more stable and error free than 11.1.1.5?
    Thanks,
    Scott

    Here are just a few of the issues I'm having:
    1) Admin tool: no objects available to select from when importing metadata
    I raised this issue on this forum first, and then raised an SR with Oracle. Eventually, Oracle gave a workaround. See this thread: No objects displayed when importing metadata
    2) Prompts based on "SQL Results" do not work.
    I want a prompt which presents to the user some radio buttons, such as "Today", "Month to Date" and "Year to Date".
    Therefore, I set up a dashboard prompt, where the choice list values are "SQL Results", and then specified the SQL as:
    "select 'Today', valueof(today_date) from dw32 union select 'Month to date',valueof(current_month_date) from dw32 union select 'Year to date' , valueof (current_year_date) from dw32"
    As you can see, this uses the "today_date" etc repository variables to return the actual dates. It also selects 2 columns, the first column being the display value, the second being the underlying code value returned (as described in the Oracle documentation).
    Although when run, the prompt looks ok, the BI Server then uses the display value (i.e. the first column - e.g. 'Today') in the underlying database SQL select, instead of the corresponding valueof(today_date), so resulting in an invalid query.
    3) Prompts based on the "* Prompt User" operator do not work.
    I want to simply provide the user with the ability to decide which range of dates to produce a report on.
    In the prompt editor, the "is between" operator is available. This works ok if I use this in a prompt on its own. However, if I select the "* Prompt User" option, the following happens when the user runs the prompt:
    - there's no "is between" operator available
    - there are lots of extra operators available that I don't want the user to see. E.g. "is like", "is ranked first", etc, which don't make a lot of sense when specifying a date.
    - if the user selects e.g. "is greater than or equal to", then the underlying SQL is not correct anyway.
    All I'm trying to do is to produce a (what I thought would be) simple prompt that allows the user to select either a date range, a single date, or options of "today", "month to date", "year to date". It seems it's just not possible.
    4) It's not possible to format a seconds value as HH:MM:SS
    I tried this when I was doing some prototyping in Oracle BI 11.1.1.5 - not yet tried in 11.1.1.6 but I can't imagine it will have been changed.
    I simply need to be able to use the "Custom Format" option in an analysis's column properties to be able to format a seconds value as HH:MM:SS, where HH can be more than 24 hours. E.g. this value could be the total number seconds worked in a week, but we need to show as hours, minutes and seconds. However, it's just not possible - Oracle allows the [FMT:time] option, but this only displays up to 24 hours.
    5) Re-branding
    I need to be able to re-brand the analytics user interface with our own company logo - and preferably with a logo that's dependant on who logs in.
    I followed this tutorial:
    http://www.oracle.com/webfolder/technetwork/tutorials/obe/fmw/bi/bi1113/customizing_obiee11g/customizing_obiee11g.htm
    My first attempt, several hours later, produced variable results. It kind of worked (although it's obviously going to rerquire a lot of effort to get it to look right), but the editing of analyses then only used half the screen width for some reason. And it looks like it's going to be quite a job getting it show a different logo for each user who logs in - maybe using the SKIN session variable? Why is everything so difficult to do!
    6) Application of data filter doesn't work.
    As this will be a multi-tenanted implementation, I need data-level security. I created a data filter in the metadata repository, and then applied to an application role.
    However, it didn't work - BI server still returned all data. Some googling later I discovered other people had had the same problem. After several hours trying to get this working I gave up on it for the time being, to come back to later.
    It seems that nearly everything I try to do involves:
    a) ploughing through acres of Oracle documentation, as it's not immediately obvious from the user interface how to do the less obvious things
    b) hours spent trying to get it working
    c) hours spent googling trying to figure out whether it's just me that's not doing something right or whether other people have had the same issue
    d) either giving up and trying to do it a different way, or raising an SR with Oracle, which can take many days to follow through.
    It's interesting to see that Gartner's latest Magic Quadrant for BI (dated February 2012) backs up my own experiences:
    "References rate OBIEE as difficult to implement, with only SAS Institute considered more difficult. Also, the product was rated as having lower than average ease of use scores."

  • Using Reference Files - Aperture Library still larger than file storage

    Still new to Aperture, and so far LOVE the metadata tagging functionality, but am troubled by the huge size of the Aperture library. Here's my stats so far, after a couple of days of importing, with no image management done so far other than assigning some metadata...
    # photos managed as reference files=1175
    Size of folder where reference files are stored=883MB
    Size of Aperture library (.aplibrary)=1.44GB
    My expectation would be that the ratio of Aperture library to reference file folder would be about 1/10. But 1.6/1 seems way out of whack. I selected all photos within Aperture and then selected "Manage Reference Files..." and all 1175 file references showed up. On that basis, I'm pretty confident that the jpegs aren't being copied into the Aperture library. But I cannot explain why the library continues to be 1.5+ times as large as the reference file folder.
    This seems to defeat the purpose of keeping reference files external from Aperture.
    Am I missing something, or is this to be expected? If these ratios hold, then it seems if I end up managing 10GB of photos I will incur another 15-16GB of storage requirement just for Aperture to do its thing.
    What is Aperture doing with all that hard drive storage space?

    By default, Aperture creates previews of all of your images. A preview is little more than a JPEG copy of the original. The size of these are determined by the settings in Aperture's preferences. When you're dealing with RAW images, the size of the previews are significantly smaller than the master image, but if you're working with JPEGs, then the previews can balloon the library to as large (large when you add up the thumbnails and duplicates) as the referenced files.
    You can reduce the size of the previews, or delete them and turn them off all together if you're not sharing your photos with other iLife & iWork apps from Aperture. There are some other reasons you may find them beneficial, and this article will help you determine if they are right for you:
    http://docs.info.apple.com/article.html?artnum=304499

  • Aperture 3.6 buggy under Yosemite?

    I've been getting some strange library bugs running Aperture 3.6 under Yosemite. Photos will appear and disappear in preview, might also be seeing some preview file corruption.
    As Aperture is not being developed further I'm inclined to jump to Lightroom. Just wondering if anyone else is seeing anything similar or if there's a simple fix.

    The only challenge I've had with Aperture 3.6 had to do with reprocessing images with the updated RAW engine for Yosemite. I had one project that I just chose to import again, but other than that things worked well. But, once through the initial reprocessing hurdle, I am very happy with the results I'm getting. Aperture may be going away, but it's clear to me that the imaging foundation that sits in OS X continues to improve. I'm actually moving some projects I shot with my Fuji X-TRANS cameras from LR back to Aperture.
    I hope you situation improves and you were just experiencing some bumps while reprocessing.

  • Aperture suddenly acting buggy:  photo adjustments not showing up

    Aperture has starting acting really oddly.  The primaryt thing I've noted is that when I make adjustments, frequently they aren't being reflected in the image shown (as if the "preivew" isn't being updated.  I know the adjustments are doing something, since the histogram curves change as I'm making changes. Moreover, if I toggle between the master and the version, no change is displayed (although the histograms do change).
    The above behavior happens about 80% of the time, with the other 20% of the time things act normally. I can't determine any pattern to when things work or don't work.
    I tried deleting all the previews and recreating them all, thinking maybe there was some issue with the preview database. Alas, that didn't solve the problem.
    Any ideas?

    Argelius,
    Please test with a new, small Library, and see if the same behavior persists.  Also see:
    http://support.apple.com/kb/HT3805
    Ernie

  • HT4007 Using Aperture 3 on more than one home computer

    My family has 5 Apple computers in use around the house - if I buy Aperture 3 as a download can it be used on all of them at no further cost? Is there a different key code that has to be entered each time? How does it work?

    If you buy Aperture from the AppStore for personal use, you are entitled to install it on any Apple branded computer you control without any additional cost. Just sign into the AppStore with the Apple ID you used to buy it, and you will be able to download it again on your other machines. You do not need to enter a licence key.
    Regards
    Léonie

  • Dw cs3 - even more buggy than previous versions?

    Hi peeps.
    i have to say over the last few years this product has been
    getting more and more unusable, buggy and just worse :(
    4 examples (cant think of more off the top of my head):
    :: im inserting FLV videos into a page - i do an F12 to
    preview in my test environment (using php). FLV simply are not
    transferred accross... this means i have to keep copy/pasting into
    the design environment... wtf!
    :: i cannot FTP files over about 7Mb to live sites. all i get
    it connection lost. yet, when i use a FREE ftp client like cute, i
    have no problems. i have tried all configs to get out. why is the
    limit at ~7Mb??
    :: i can design a really nice, although complex CSS layout
    that works flawlessly in IE, FF, opera etc. yet looks like crap in
    the designer. why cant it render proper CSS layouts???
    :: i design a PHP site, yet multiple times throughout the
    project various PHP elements and includes stop showing. meaning its
    almost useless to see and design view. i might as well use notepad
    or something else that can do code colouring.... which also isnt
    perfect as comments in PHP sometimes mis-colour.
    :: not to mention the annoying issues with photoshop STILL
    not importing clipboard 1/2 the time - meaning i have to restart pc
    with all open apps etc... tital pain in the backside.
    wtf is going on? the adobe premium suite is amazingly
    expensive, and since i live in England, is DOUBLE the price of the
    US version. yet we are told that we pay additional money for the
    language packs!

    > :: im inserting FLV videos into a page - i do an F12 to
    preview in my test
    > environment (using php). FLV simply are not transferred
    accross...
    Did you upload the FLV file to the test environment? You will
    need to do
    that.
    > this means i have to keep copy/pasting into the design
    environment
    Huh?
    > :: i can design a really nice, although complex CSS
    layout that works
    > flawlessly in IE, FF, opera etc. yet looks like crap in
    the designer. why
    > cant
    > it render proper CSS layouts???
    Let's see one of these layouts, please. Can you post a link
    to one of the
    pages?
    > :: i design a PHP site, yet multiple times throughout
    the project various
    > PHP
    > elements and includes stop showing. meaning its almost
    useless to see and
    > design view.
    This would be a function of your local environment and
    testing setup, I
    believe.
    > :: not to mention the annoying issues with photoshop
    STILL not importing
    > clipboard 1/2 the time - meaning i have to restart pc
    with all open apps
    > etc...
    > tital pain in the backside.
    Photoshop?
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "Liam T" <[email protected]> wrote in
    message
    news:[email protected]...
    > Hi peeps.
    >
    > i have to say over the last few years this product has
    been getting more
    > and
    > more unusable, buggy and just worse :(
    >
    > 4 examples (cant think of more off the top of my head):
    >
    > :: im inserting FLV videos into a page - i do an F12 to
    preview in my test
    > environment (using php). FLV simply are not transferred
    accross... this
    > means i
    > have to keep copy/pasting into the design environment...
    wtf!
    >
    > :: i cannot FTP files over about 7Mb to live sites. all
    i get it
    > connection
    > lost. yet, when i use a FREE ftp client like cute, i
    have no problems. i
    > have
    > tried all configs to get out. why is the limit at ~7Mb??
    >
    > :: i can design a really nice, although complex CSS
    layout that works
    > flawlessly in IE, FF, opera etc. yet looks like crap in
    the designer. why
    > cant
    > it render proper CSS layouts???
    >
    > :: i design a PHP site, yet multiple times throughout
    the project various
    > PHP
    > elements and includes stop showing. meaning its almost
    useless to see and
    > design view. i might as well use notepad or something
    else that can do
    > code
    > colouring.... which also isnt perfect as comments in PHP
    sometimes
    > mis-colour.
    >
    > :: not to mention the annoying issues with photoshop
    STILL not importing
    > clipboard 1/2 the time - meaning i have to restart pc
    with all open apps
    > etc...
    > tital pain in the backside.
    >
    > wtf is going on? the adobe premium suite is amazingly
    expensive, and since
    > i
    > live in England, is DOUBLE the price of the US version.
    yet we are told
    > that we
    > pay additional money for the language packs!
    >

  • Importing Aperture Library, but more than 2x the number of photos

    I'm just switching back to iPhoto after trying Aperture, and just dragged the Aperture library into iPhoto.
    But its apparently importing 13,826 photos, even though there are only 5031 in the Aperture library.
    What's going on there?

    What you imported was the original and preview versions that exist in an Aperture library. If you have a backup copy of the library before you imported the Aperture library revert to it and then Export the Aperture photos full size to folder on the desktop and import into iPhoto.
    Or, if Aperture stores the originals in side its library package somewhat like iPhoto you could open the package and drag the folders containing the full sized originals into the open iPhoto window (the recovered backup library).
    Otherwise you could try using Duplicate Annihilator to remove the duplicates. But be sure you're removing the smaller preview version instead of the full sized original file.
    Terence Devlin uses Aperture so may have a better solution.
    TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
    I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. Just put the application in the Dock and click on it whenever you want to backup the dB file. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
    Note: There's now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

  • Is the PRINT quality of Aperture's RAW different than Photoshop's?

    I've seen various comments suggesting that Aperture doesn't handle raw files as well as photoshop. Is this just a screen issue or it is also a print quality issue?

    Depends on how Aperture is handling this. The
    preferred internal rendering intent is used in ICC
    applications that don’t specify a conversion. And you
    can easily change this tag.
    How, where? I'd LOVE to know.
    IF Aperture actually
    tells it’s conversion engine “Use Relative
    Colorimetric”, that’s what you get.
    I'm pretty sure it does, but I'd still like to know if you think there's a way to change this, and run some test prints. I can match aperture's prints exactly by setting the rendering intent in PShop to rel. colorimetric. Sadly, for most of the good art papers, the shadow quality is much better using a perceptual intent, so that means printing through photoshop right now.
    At least in Photoshop (and I’d assume Aperture), soft
    proofs are always Relative Colorimetric with black
    point compensation. So the soft proof should be OK.
    Not true, at least in CS2. You set the rendering intent for soft proofing under Proof setup.

  • Aperture exports jpeg files larger than original RAW files

    Can anyone tell me why a RAW file (10.6mb), when exported as a jpeg (10.8mb) from Aperture ends up larger than the original RAW file. The same RAW file when opened and then saved as a jpeg (6.4mb) in Photoshop is a lot smaller. The photo dimensions and resolution are the same in both saved files (34.5mb open file 300dpi 4256 x 2831 pix). I have tried this on several photos, all with similar results. For information I am saving the photos in both Photoshop and Aperture at 300dpi, original size and at a quality setting of 12. In these examples/tests I have done no work to the photos, obviously the file sizes increase after work has been carried out on the photos (in both Ps & Aperture)
    Almost doubling the size of saved jpegs has a massive implication on my library and may be one reason to consider Adobe Lightroom as this gives similar jpeg file sizes as Photoshop, i.e. almost half the size of the original RAW file
    Reducing the quality setting on saved jpegs is an obvious way to reduce file size, but not answering the question of the considerable discrepancy when saving to the same quality in different software
    Is this a feature of Aperture and nothing can be done about it ? I would prefer to use Aperture but cannot cope with the large jpeg sizes !
    Any comments would be much appreciated - thank you
    Nick

    Think you might be right Allen - The 12 quality saved jpegs seem to be pretty high quality, closer to the original than maybe the files saved in Ps at quality 12. I have just run an identical set of processing actions on all the files in Photoshop and the jpegs previously saved in Aperture at 12, 11 and even 8 quality settings seem to be better than the same files saved at 12 in Ps
    Bizarrely the file size drops from 10.6mb at quality setting 12 in Aperture, to 3.2mb when saved just one notch down at quality setting 11 in Aperture. That is a massive drop, esp considering the next one down, saving at quality 10 results in a 2.8mb file
    rw just ran some checks and tests on the file export settings and file sizes in Aperture, on a file I sent him, and we get the same results. So at least my version of Aperture is not up the wall !!
    Would be useful to have the explanations from Apple as to the vast variance in settings and file sizes, but I guess we will just have to keep guessing - and buying more and more hard drives for all the large files
    I am considering keeping the RAW originals in future, and I suppose in this case I need only save smaller jpegs, and issue at whatever size they are needed at the time - just needs a bit of planning to look after an ever increasing collection, which is about to have two sets of images added at a time now. Added to the already amassed 80 000 images at last count !)
    Thanks
    Nick

  • Aperture wants to repair library every time I work on any photo

    I open a photograph in Aperture 3, export it to Photoshop (CS5.1) as I have done countless times before, then work on it in PS and save the revised version to a location outside of Aperture. When I return to Aperture it is inert, giving me a big blank gray screen. I can't even force quit, as it doesn't appear in Force Quit's menu of open applications. Very strange. When I try to restart, eventually a prompt comes up saying Aperture has a problem with its library, and needs to repair it. So it takes an hour to do that. Then Aperture looks normal, until I work on another photo, then it happens all over again, an hour + each time. This is slightly inconvenient! Do I need a rebuild? Any ideas? This just started today. Aperture has not been buggier than normal lately, though all new work has been going into LR for the last year or so. Yes, that's a pretty messed up work flow.

    It seems you might be confusing two different workflows.
    ⇧⌘o is the shortcut for "Edit with external editor".  That is not the same as exporting.
    When you edit with an external editor, you must save the changes you make _to the file that was sent to the external editor_.  It will then appear in Aperture.  You do not save from your external editor "to a location outside of Aperture".
    Either "Edit with external editor" and save your changes, or create a new file by exporting from Aperture and then opening it in an editor.  Do not "Edit with external editor" and then save as a new file from your external editor.
    HTH,
    --Kirby.

  • What's wrong with my MBP. (it's running more like a PC, than a Mac)

    I have a Mac Book Pro 15" 2.16 that I've had for nearly a year. It's always been far more buggy than my imac G5, but lately it's becoming unbearable. It's rare for me to get more than 24hrs of uptime, and the system frequently just freezes completely, and all I can do is shut it down and restart.
    Sometimes when I'm using it the screen grays out and it gives me a message stating that I have to restart. At this point all I can do is power down.
    It has the 513 of factory ram, and then a 1gig stick of corsair value select. I've been wondering if it;s the ram, but I've been pulling the ram modules and trying to run them individually, so we'll see how that goes.
    Any tips??? I should note that I'm running attached to a 30" Cinema Display most the time, and I have various firwire and USB devices hooked up. It does run smoother when I have nothing hooked up, and I can shut it down without just having to shut it off, but it seems it should not be crashing hardly at all.
    I frequently run maintenance scripts, and also have tried running applejack, but it does not fix the problem.
    Any thoughts would be appreciated. Is this normal with the intel macs? My imac G5 hardly ever crashes, and I'm fed up with this thing.
    Gavin
    Imac G5, Mac Book Pro 15"   Mac OS X (10.4.10)  

    The one thing I notice, apart from the RAM which others have commented on, is the process of these kernel panics: panic, shutdown, restart. There is no mention in your posting of anything else to check/fix/repair.
    If that is it, then you are investing in disaster and a series of repairs and maintenance checks is suggested. A KP causes certain processes in the OS to be incomplete and carrying on without fixing those could cause problems.
    I would at least start with a Safe Start (hold the shift key down at startup) and I would also recommend starting with the install DVD holding down the D key for a hardware check.
    I would also urge that you at least run the Disk Utility on the startup (install) disk and if necessary buy a stronger utility. I use Disk Warrior and run that often, before problems occur. Once there are problems it may be all you have.

Maybe you are looking for