Probably any image changed from the 1.1 to 2.0 raw decode will look different. If you are happy with the way they looked before, then I would just leave your previous photos as 1.1 decodes.

Also, the Tint slider does have a bug. Just clicking on it drastically changes the color temperature of the image without moving the Temperature slider! I double-click the Temp slider to reset it. After that, Temp and Tint work fine.

i notice images that are moved from 1.5.6 to 2.x are dramatically different if you've used the Levels adjustment. Since Levels got pushed down the brick hierarchy, it makes sense that adjustments made with levels would appear differently, since their now technically out of sequence, for how the image was originally adjusted.

not a problem unless you unwittingly convert thousands of images and need to go back and redo the adjustments on each one. ouch.

I discovered this morning that the control-V, that brings up the vignette, also brings up the inspector (which I like to keep hidden).
I usually use the floating HUD to do the adjustments.
Is this just me? Or have others discovered this too?

ctrl+v adds the vignette tool but does not reveal the inspector panel for me. Does this happen routinely for you?

Hi Ellen,

about your article (adjustment tools):

Maybe you should mention that the Moiré correction does a great job at removing the cyan/red or blue/yellow fringe which can appear when you photograph on light baggrund (could be a branch on the sky).
And it does not blur the picture at all.

IMO, nothing else can achieve the same correction in Aperture.

I have a video on my site showing clearly the effect.

Always a pleasure to read you,

Francois

Thanks Francois, that's an excellent point! I'll check out your video when I get home (I'm in the arctic Circle right now with limited internet.)

I am having trouble with Aperture two also.
I have lost images. I guess I am not sure it is aperture, but I look at the images on my card in the 1Ds Mark3 then when I put it in my card reader and go to import in aperture there is just the space for the images. And then if I try to look at them on my camera again there is just a question mark. Any thoughts?

Adam, what you are describing sounds like a corruption on the card itself. When the card's directory becomes corrupt - which can happen if the power to the card was disrupted while the card was reading or writing - scenarios such as what you are describing can result. CF cards also become corrupt for other reasons which are sometimes never discovered. I recommend trying a card recovery program such as Photorescue (www.datarescue.com ) What you are experiencing isn't an Aperture 2.0 issue but something that's been an issue for a long time now with memory cards.

Ellen

Thanks. I am going to get some new cards today
.I had another question that is probably an aperture prob. When I shoot in the monochrome mode on the 1Ds Mark 3 when imported it turns it into color for some reason. It is really weird. Any thoughts. Sounds like the adjustment tools problem but when I push to reset it does not do anything.

Adam, when you shoot in raw format some camera settings are not applied until the actual conversion. If you were shooting in JPEG, you'd see the image as monochrome because all camera settings are "baked into" the file. But the beauty of raw is that you have all the data at your fingertips. That way you can fine tune and tweak your choices after the fact. So no, that's not an Aperture problem either - that's the way raw files work!

Ellen

Hello Ellen,

I'm a new Aperture (v2.1.2) user, and have been bumping into this “Unsupported Image Format” issue after some time editing. It feels like a nasty bug in Aperture. So far, restarting the machine has always brought it back. I've been doing a ton of reading online about it, and have yet to see a definitive explanation.

Should I be concerned about the time spent, with the possible corruption of my data structure? I've seen others saying the problem resulted in an ugly process to restore things to working...

I'd rather switch to an inferior product than suffer through an occasional manual database rebuild.

Any thoughts would be appreciated,
-Steve

I'm having some similar issues. I'm decreasing the size of my library by changing to referenced files. I'll put the masters ok a Dobo unit and see if that helps. I'm traveling ally right now do it might take mr awhile to resolve the issue. But I'll be glad to let you know. Relatnchinf and: or rebooting always solves the problem for me for awhile.

Having the Unsupported Image Format message too. Did a big edit job for a client today and bam this crops up. I can't believe it - this is awful for a pro product and I am worried about the files and the time I have lost. I have googled around and it seems plenty of other people have encountered this message seemingly out of nowhere. I hope it is a one off, but if I can't rely on Aperture then I can't use it as a pro tool. After all the time and effort converting to Aperture I feel really let down right now... Urgh.

Jay, although it's inconvenient, relaunching and/or rebooting does solve the problem - although with extensive graphic use, it reappears. There must be some sort of a memory issue occurring. I know the folks at Apple are listening and will hopefully solve the problem soon. However you don't have to be alarmed that the files are being corrupted - they're fine. If you're at all concerned about that, use referenced files and back them up on another drive.

Hi Ellen,

I can't help but wonder why everyone is so thrilled with this "Professional" class product. Yes, it does so many things well, but details like this are disturbing - and your answer isn't overly warm & fuzzy either.

I realized early on to reference my files, never trusting an enclosing database to always behave. Keeping the RAW files exceedingly safe is easy, simply back them up to a real cloud solution using a service like Amazon & Jungle Disk.

Losing every version adjustment is the horrible nightmare I want to keep from happening, and this "memory" issue is the tip of just such an iceberg. Sadly, this problem has been going on since verion 1.0, and that is why I'm upset. Apple has never communicated things well, and I was hoping an "O'Reilly" forum might be more than a marketing scheme.

Take care,
-Steve

Steve, a lot of people really like Aperture because it is one of the most efficient solutions for organizing, editing and optimizing your images. It makes it easy for me to go through a lot of images quickly and generate high quality output. Is it perfect? Definitely not - it clearly has room to grow. But then again this is just the second generation of this software - and it's already quite impressive. It is without a doubt, my preferred software to use in my personal workflow.

As with most software, there are occasional glitches. I don't like them, but they're not a deal breaker for me. The memory issue I've experienced appears to be related to the huge files from a 31 megapixel camera I'm using. Digital technology is evolving and there are some growing pains. I can handle relaunching if I have to. You sound quite angry but I'm not sure why. Losing every version adjustment would indeed be a nightmare - that's why you should have a backup of your library - however you choose to do it. But I'm not sure why you think you're on the verge of having that happen.

Just so you are clear, the O'Reilly forum is independent of Apple. Those of us who blog are sharing our experiences, tips, and suggestions in hopes that it may be of benefit. Some of us, including me, are Apple Certified Trainers in Aperture 2.0.

>just the second generation...

Meaning 3rd Gen = more features, less stable, old bugs continue - oh, and the requirements to run v3 semi-effectively will go up too. I'm using stuff that is "comparable", 8 megapixel & PPC G5. Is this issue related to the video memory, available RAM, or System memory corruption? Apple likely knows, choosing to remain quiet.

Has anyone been brave enough to actually *use* their backup library once in a while? What was the process, and how did it turn out?? When Apple actually says something related, it is often frightening:

* Mac OS X v10.5.3 Leopard or later is strongly recommended. Earlier versions of Leopard did not provide full compatibility between Time Machine and Aperture.
* Do not perform a restore operation while Aperture is running. You may lose data from your library if you perform a restore while Aperture is open.

The first point they make is out and out scary, the second seemingly obvious, but not stressed enough in a solid & *published* procedural workflow.

Here's someone actually thinking about what can likely go wrong:

http://maczealots.com/articles/aperture-backup/

The reason I came here was because O'Reilly Aperture Forums are independent, but who is actually tearing into the bowels of the software? I was hoping to find Derrick's PhotoPlus Expo "Best Practices" presentation, but that's a proprietary marketing choice most authors choose to make. Ellen, you can teach me how to use Apterure, but where does the professional photographer learn that they have created a GIANT house of cards?

-Steve

Hi,

Given you posed this back in March, (nine months ago) and the Unsupported image problem is still, well, a problem - actually a big problem for me) I was wondering if you had any thought about switching to Adobe LIghtroom.

I like the Aperture UI better but if this is the kind of support and quality to expect perhaps switching is the way to go. However, I am sure Lightroom has its own set of warts. Just wondering how ugly they are in comparison.

Thanks in advance for any comments.

I think your last couple lines describe the situation accurately - each program has advantages and disadvantages ... as well some issues that should not exist. I prefer to stick with Aperture confident that it will get better - perhaps not as quickly as I'd like, but I vastly prefer the interface and overall approach of the program. The Unsupported Image Format error message is apparently a catch all error message for when it runs out of memory. I'm fairly certain the Aperture is aware of the issue, and I can only assume that the fix is a more major undertaking than what we might guess. Once you understand the issue an dknow the work around, it's just a bit of a nuisance, not the nightmare that it first seems. So for me, the advantages of Aperture will cause me to be patient.

Regarding the "unsupported image format", I often get it too, even more after upgrading from a Canon 40D to a 5DmrkII (and shooting raw). So the running out of memory thesis is apparently correct.

Another 6 months down the track and still no fix for the Unsupported file error.

Can anyone give an alternative for very large libraries & edits (not lightroom)

Mick

I am not sure if it is only a memory problem, I tried clearing the RAM from my computer (G5) and it did not do any good, and rebooting the computer does not solve the "unsupported" problem either. I have another copy of aperture on my laptop and when I access the main library on my G5 with it, everything is fine. So the only work around I have right now is to use my laptop and access the library on my G5. There does not seem to be any rhyme or reason for this problem right now. I suspect that the operating system may have something to do with it also. Maybe when they come out with snow leopard next month it may solve some problems. One can only hope.

Im a new MAC user and I have Aperture 2.1.4. I started experiencing the same problems with the corrupted files.

I ran disk utility and it tells me to reinstall OS X (I have Snow Leopard). Did anyone try this? Any news from Apple?