More Aperture 3 bugs....Grrrr

The export to email options are totally messed up. You can select the size of the photo but aperture happily ignored that and uses it's previousm setting. You can see this by quiting aperture, going into preferences again and there is the old value. So for example, if I select medium JPEG it will still pass along a great big full size one across to mail, if that was the previous setting.
Now you can get it to remember the option but only if you edit the new size you have selected and pretend to change it and then save it. All fine and good you would think - a workaround. Well no, this leads to an even worse bug...
Try and add a new option. I tried JPEG and made it full size (by duplicating the existing one) and then moved the slider along to full quality. Well that results is a 12MB JPEG file - for a 12MP camera? ***?
I've never seen such a buggy application from Apple before. There is *no way* this application was properly tested. I'm getting a little tired of beta (or is that alpha?) testing this.

I can't agree with you more. I keep thinking it's me, but this is a horrible release:
1) Memory leaks like crazy.
2) Gratuitous pinwheel of death for no good reason.
3) Mouse scrollwheel support broken.
4) Your preset bug.

Similar Messages

[svn:fx-trunk] 11208: More styling bug fixes:

Revision: 11208
Author:   [email protected]
Date:     2009-10-27 16:30:03 -0700 (Tue, 27 Oct 2009)
Log Message:
More styling bug fixes:
- Add borderAlpha, borderColor, and borderVisible to NumericStepper
- Make LinkButtonSkin respond to cornerRadius, rollOverColor, and selectionColor
- Draw opaque white background behind data grid header so contentBackgroundColor doesn't bleed through
- ItemRenderer/DefaultItemRenderer no longer draw contentBackgroundColor. In the "normal" states, the background of the renderer is transparent so the skin background color shows through.
QE Notes: 5 DataGrid bitmaps need to be regenerated.
Doc Notes: None
Bugs: SDK-23437, SDK-23367, SDK-23351, SDK-23345, SDK-23339
Reviewer: Kevin, Ryan
API Change: no
Is noteworthy for integration: No
tests: checkintests gumbo/components/NumericStepper components/DataGrid
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23437
    http://bugs.adobe.com/jira/browse/SDK-23367
    http://bugs.adobe.com/jira/browse/SDK-23351
    http://bugs.adobe.com/jira/browse/SDK-23345
    http://bugs.adobe.com/jira/browse/SDK-23339
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/NumericStepper.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/ItemRenderer .as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/DefaultItemRenderer.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/NumericStepperSkin.mxml
    flex/sdk/trunk/frameworks/projects/sparkskins/src/mx/skins/spark/DataGridHeaderBackground Skin.mxml
    flex/sdk/trunk/frameworks/projects/sparkskins/src/mx/skins/spark/LinkButtonSkin.mxml

This bug figures out also when creating a custom spark ComboBox, then trying to programatically update the userProposedSelectedIndex property. The proposed selected index is selected, but does not apply the same skin as when mouse is on rollover or item is selected due to up and down keys.
The issue seems like updating the status of the item renderer to rollover or selected to get the same skin applied.
Please could you attach DropDow nList.as that you edited ?
Thank you so much.

More Aperture/iPad syncing issues

Each time I create a new project or album in Aperture, I have trouble getting the images to the iPad when I sync. I sometimes need to sync several times until the images are recognized and imported to iPad. I do have the albums designated manually, rather than all, which means I have to sync and then sync again after I check the checkbox for the new album. I understand that, but sometimes I have to go back into Aperture to make sure the previews are updated. If I choose to update the previews for a project, Aperture will usually tell me that they're already up to date, but often they will not show up on the iPad, even after I check the appropriate box for the album in iTunes. Sometimes I get good results if I delete the previews and regenerate them in Aperture.
The second problem is the sort order. Even if I have "sort by filename" selected in Aperture, they do not show up in this order on the iPad--despite what the support article says about this. They appear to only show up in Date order. I've tried repeatedly resetting the sort order, but it does not change on the iPad. Sometimes I have to delete the album from the iPad, (uncheck the album in iTunes and sync again), then recheck it and sync yet another time. This does not always work, however.
It is very frustrating. The interface between Aperture and the iPad is very wonky. I often have to sync repeatedly, just to get the photos on the iPad and even then they're usually in the wrong order.
Aperture appears to have two types of previews: "previews" and "sharing previews," but "sharing previews" don't seem to appear in the documentation. I've noticed that, even when Aperture says the previews are up to date, when I exit the program, it will sometimes (but, maddeningly, not always), give the message, "updating sharing previews" before quitting. I cannot figure out how to force this, however. Sometimes opening and closing Aperture several times will cause it to do this, but I can't be sure.
iTunes seems to have its own process in which it "optimizes" images for importing to the iPad. Like Aperture's mysterious "sharing previews," "optimizing" does not show up in the iTunes documentation or help files.
This process either needs to be improved, or at least documented so users can understand how to avoid these problems.

1. Some people have reported slow syncing with anything but the iPad's own USB cable (e.g. using a US cable from an iPhone/iPod). Try different cables
2. More work - disable iTunes syncing completely, then re-enable a bit at a time, e.g. one movie at a time, one playlist at a time, one photo album at a time. There are periodic reports of syncing issues caused by a bit of media that's been corrupted, and this (tedious) approach allows you to identify where the problem might be.
3. If that fails, do a clean restore back to factory settings, then progressively re-enable syncing as above.
Hope this helps

Mail in Mavericks - even more problems/bugs

Apart from the details (basically bugs) that accompany Apple Mail from previous versions without any corrections (! ), Mavericks brought yet another "improvements"
The most disastrous one is the following
SEARCH DOES NOT HAPPEN ANY MORE WITHIN THE SELECTED FOLDER:
So far, when I was in a particular created mail folder ("on my Mac"), the search was done just within the folder (very logical)
But now , after the new OSX was installed , when I am in a particular folder and start a search for a sender, now I don't see just the emails from this sender within this very folder as before, bit I see ALL the emails from all the folders by that sender. This is simply terrible and makes no sense.
For example I make a folder "invoices" where I put all the mails that include invoice. When I go to that folder and want to find invoices from a particular sender, so far I found them (by writing the sender's name into the search field). But now in the new OSX - when doing that I see ALL th existing e emails from that sender from all the mailboxes, so the search and folder is good for nothing ... It is quite upsetting and makes the work miserable.
Apart from the old bugs - like 1) when the new mail is coming, if the messages are grouped, in the preview pan and notification I don 't see the content of the newest message, but of the previous one, till I specifically go there and open the message 2) when I go to the Sent mailbox I very often do not see the addressees, but me as a sender in all the mails in the list, only if I go there second time, it changes and I finally see the addressees in each mail - quite annoying
we have new minor bugs now
1) notifications are delayed: before the notification came immediately - now I open the email read it and then only the notification comes
2) adding attachements takes much longer than before. Till Mavericks , clicking on an attachement took just nothing before it was added to email, now it takes few seconds ...
3) sending and receiving messages pane. When you send 1 email - why in the sending pane you see "Sending 36 of 36 or 68 of 68" when you send one message ? The same for receiving. Quite a nonsense ...
What is the use of 0,000x mm thickness of apple hardware when the basic things do not work as they should and become even worse ?

Mavericks user experience with Mail, Safari, etc. has been the worst program upgrade I have ever seen. I cannot even list all the issues others have under discussion in other threads and I find I have almost all of them too. User experience fail.

Fixed 11.0 BUG, but had another more serious BUG in 11.1

But no one found this BUG, \u200b\u200bI have a question, and also did not care for me, from time to time lay off 750 people this time, the 11.0 developer to cut, resulting in 11.1 H.264 encoding so bad. And 11.0 full immeasurably.
https://bugbase.adobe.com/index.cfm?event=bug&id=3005174 I guess because the fix this BUG, \u200b\u200bcaused. In fact, not good, if not repaired
https://bugbase.adobe.com/index.cfm?event=bug&id=3047043 11.1 New BUG, \u200b\u200bbut did not care for me, this is a very serious BUG, \u200b\u200bif not found, then it will put an end to 11 series, but 11.0 is excellent, and I hope can be restored to 11.0 in 11.2 look like.

But no one found this BUG, \u200b\u200bI have a question, and also did not care for me, from time to time lay off 750 people this time, the 11.0 developer to cut, resulting in 11.1 H.264 encoding so bad. And 11.0 full immeasurably.
https://bugbase.adobe.com/index.cfm?event=bug&id=3005174 I guess because the fix this BUG, \u200b\u200bcaused. In fact, not good, if not repaired
https://bugbase.adobe.com/index.cfm?event=bug&id=3047043 11.1 New BUG, \u200b\u200bbut did not care for me, this is a very serious BUG, \u200b\u200bif not found, then it will put an end to 11 series, but 11.0 is excellent, and I hope can be restored to 11.0 in 11.2 look like.

Vault does not work any more Aperture 2.1.1

Hi,
I just experienced that the vault function does not work anymore for me. When I click on the icon to show the vaults I created, nothing happens and Aperture seems to hang for some time. Sometimes it finally comes back and I can quite Aperture normally. Sometime I just need to force exit.
I switched to a different library, where no vaults have been created and when I tried to create one by opeing the vault area first, I got the same effect. When I select directly "create vault", it creates the file, but it does not put any content in.
I'm using Aperture 2.1.1 and MacOS 10.5.4.
Any hints ?

I had a similar problem. A portable Maxtor USB drive worked fine as a vault till this am, then message that there is not enough space. Get Info tells me about 54 GB available, and my entire Aperture Library is only 54 GB. Up till today it did incremental backups just fine.
I added a firewire drive and it seemed to work as a second vault, except while Get Info for the drive says it has a 50 GB Aperture library now, the Vault window in Aperture says this vault is backed up but it only used up 3 GB of the drive. The second widow for the original drive shows the expected amount used, ie about 50 GB.
So if I run Get Info on the firewire drive, it tells me I have a 50 GB Aperture library, but the small vault window in Aperture says only 3 GB.
I was going to reformat the original USB drive and re-try it, but this last information is coflicting, Any ideas on how to proceed?
Don

More Aperture improvements

This article http://www.appleinsider.com/article.php?id=1752 says that the next OSX update, 10.4.7, will have help for Aperture users.
Mark

This article http://www.appleinsider.com/article.php?id=1752 says that the next OSX update, 10.4.7, will have help for Aperture users.
Mark

One more iOS bug found

When using advanced editor, the cancel button tries to post and gives a message that you cannot post a blank form. It does not cancel.
This is the one that made my wife finally sigh and say "what is wrong with them? they don't normally mess up this bad" after hearing me complain about lack of iOS support. She also just said i dont sound this mad at M$. Then she observed why, we expect so much more from apple. How they could over look millions of ipad users.
Jason

I agree that the example does not (and should not) compile.

More Sound Bugs

OS 10.5.1 doesn't recognize the onboard speakers on my Powerbook G4. Headphones work fine. This is new since upgrading.

walkerx wrote:
TrickyDicky wrote:
Walkerx wrote
Virgin you will need new line number, also they really throttle your connection if you go over certain amount each day. So you could be worse off in relation to speed overall.
Seems these days you can take your line number with you providing you stipulate that, & I wouldn't attract a throttle policy
Nice, makes it easier for you, but are you sure about the throttle policy or do you not do much downloading/streaming, etc
have you checked this link as from reading that unless you do hardly anything on the internet, you'll be in permanent traffic management and throttling of connection
BT throttle like mad. On BT BB my torrent speeds were about 15KB/s for a full 7 hour period between 4pm and 11pm. The rest of the time I got 1000KB/s.

Again, a new annoying bug in 3.1 (Handover to CS3)

Congratulations Apple!
This is already the third new bug, Apple built into the version 3.1 . With version 3.0.x everything worked fine.
Try this:
- Handover four NEFs to CS3 via context menu
- 3.1 produces 4 TIFFs as expected
- but only one image is opened by CS3
Again, Apple well done.
You broke my workflow, since there is no more a batch processing available, as it was before with 3.0.x.
Thanks a lot, 3.1 is the worst update for Aperture so far!!!!!

I just tried this with another external editor (Acorn) and it worked perfectly - I got 4 images.
So I'm not sure it's an Aperture bug?

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.

Aperture incorrectly duplicating exif data - how can I stop this?

The situation...
a) I have 2 cameras (Canon 5D, and a Canon 5D MII)
b) I imported photos from 2 Compact Flash cards (1 from each camera) where the file names (e.g. _MG_9670.CR2) clashed. (i.e. both cards used the same file numbering range)
c) Aperture imported the images correctly, however the EXIF data on both images match identically apart from image resolution. Aperture believes these photos were taken at the exact same date/time and with the same camera which of course is incorrect.
d) If I export the original files from aperture and use the finder 'Get Info' option I can see that the RAW files contain correct EXIF data, so the issue must purely be an aperture bug.
Question - is this a known bug and is there any way to work around this?
Unfortunately I have spotted this on some wedding photos I shot for a client so I have had to switch to Lightroom for some confidence in not loosing important photos. Hopefully if someone can provide a workaround before I get stuck into my editing I can switch back to Aperture that I am more familiar with.
Thanks
Adrian

Interesting problem. The duplicate filenames could be causing Aperture to get confused but I've never seen this myself. Do you have Do not import duplicates set in the Import pane? If it is not set and you set it does Aperture see the files on the second card as dups?
As a test, when you import from one of the cards (either one) rename the originals. Does the EXIF problem still happen? If not then you will need to rename one of the cameras files either on import or in the camera. I believe Canon allows you to set a filename no?
Also make sure to file a bug report with Aperture, Aperture->Provide Aperture Feedback, look for the bug report entry.
If renaming the files does not fix the problem post back.
regards

Aperture corrupting images during editing

Hello,
Starting a few days ago, aperture started corrupting images during editing. This was normally at the time of my fist cut, going through doing simple straighten and croping. Sometimes it would happen when doing a small lighten or darken of the exposure. I purchased a new MacBook Pro about a month ago but this only started happening this week. No OS or Aperture upgrades this week. I did have a crash earlier this week and after the crash my Spotlight re-indexed my computer. I updated QuickSilver this week and Awaken. I tried quiting both QS and Awaken but problem still happens. The real scary thing is I usally have to go back and re-import the raw CR2 image to fix the problem, doing an update from master or resetting all adjustments does not fix the problem. Below is an example of an image with the problem. This is a Version Export of a corrupted image, as you can see the cor Can I get any help?

Ernie Stamper:
The Aperture Libraries are on the local drive. I do have an external Firewire drive I can use to test your theory but since I recently replaced the whole laptop at the Apple store so I am thinking it is not hardware related but one of three things: an Aperture bug, my configuration, or memory (see more on memory below).
leonieDF:
I don't think it is related to a hardware issue unless it is memory. I took the laptop into the mac store because I was having a hardware issue not discussed in this thread. The laptop was completely replaced except for the memory since I purchased 8GB of memory after the computer was purchased. I put the 8GB memory back into the new laptop. If this is a memory problem it is not showing up in diagnostics. I am planning on doing two things this weekend. First thing is putting back in the original apply memory and testing. If I still get the issue I am going to do a complete uninstall of Aperture and re-install maybe something in my settings/libaries are corrupted. I am reaching for straws at this point. I might also try a complete reformat and only install Aperture and test to see if something else installed might be causing this, but I can't think of what it would be.

Can I slim down the size of the Aperture Library by moving the Preview files elsewhere?

Hi all,
I have an Aperture library of almost 20,000 photos, dating back to around 2007. Almost all the master images are stored on an external drive (backed up of course), with only my recent and 'in progress' masters being stored in the library itself. Previously I have had my library split up into one library for each year, with the older years libraries being stored on the external drive where the masters are, in order to keep the size of my 'current' library down. So my current library, stored on my internal SSD, contained only photos from this year and last year, and only a few of the masters for these images. Confusing? Sorry!
Now, I recently decided to consolidate the libraries into one huge library, because it was annoying to have to switch between libraries to find older photos when I wanted them. I did this, leaving all but the recent masters on the external drives (referenced). I thought that the size of the main library would remain reasonably sized, since there were no extra masters being moved into it. However, the library has grown massively - up to over 70GB, which is huge when you consider it's on a 128GB SSD which is also my startup drive.
I'm pretty certain the reason for the huge size increase is that the Previews for all the older images are stored in the Library file, rather than anywhere else. This makes sense - they are previews, they're supposed to be able to be viewed with the external drives disconnected. So my question is this. Am I able to change the location of the preview files to be on my OTHER internal hard drive (non-SSD, much larger), so that they're still available without the external drives, but are not cluttering up my startup drive. And, if not, what should I do!?
Thanks a lot

Glad it worked, but permit, if you will, some observations:
-- Bloated Previews are a known Aperture bug, which came and went within a few updates in Aperture 3. Getting them back to the proper size is simply a elegant step to take.
-- A Preview set to your largest screen size and a quality of 6-8 should be all but indistinguishable from the Master at 72-100 dpi screen image. (Not print resolution.) I REALLY doubt you are going to loose any quality.
-- While using a symlink to stick the Previews on a HD is clever, it may also defeat the whole purpose of using your SSD. Previews are read a lot and are, I suspect, used for all adjustments at less than full resolution. (N.B. I could be VERY wrong on this.) Thus, depending on the amount of RAM on your Mac, you could end up reading and rereading your Previews over a slower link and doing this a lot. You own use will quickly determine if this is an issue or not.
I have blathered on, at length, about what I think matters for size and speed here: https://discussions.apple.com/message/17959625#17959625. Some of this may be of use.
I went through a lot of these issues when I tried to fit everything on a 128 GB SSD, so I know some of the issues you are facing. As I noted before, you really only need a Library (minus most Masters) of about 30 GB and that is with large, high quality Previews.
I actually took the SSD out and stuck it in an ancient MacBookPro (in preparation for a trip to Blighty this summer) and have not noticed a huge drop in Aperture speed. (I do miss the speed of applications launch, restart, however.) One thing that I did find that made a small, but nice difference, was keeping all of the Masters on a separate, dedicated drive. Once defragged, etc. that was very fast. Don't know if you could achieve the same results by partitioning a larger drive, but it might well be fun to find out.
DiploStrat

Two bug fixes in 1.03 firmware

It looks like the constant rebooting bug is fixed. I loaded something over with an equalizer set and nothing bad happened. The other more trivial bug fix is that world times now work properly if you are in a time zone where daylight savings time is set.
The bug where the date in the Date and Times settings always shows in US format is still there.
Michael

Sorry I missed the existing thread on this topic. Please reply to that one.
Michael

More Aperture 3 bugs....Grrrr

Similar Messages

Maybe you are looking for