Keith Reeder

But I did, and it's still a relevant question, which "a good spec in my machine" doesn't answer. It is good forum etiquette that if someone asks for information in response to your request for help, you provide the information. And many of us have no such problems, meaning that it's very possibly a "local" problem (ie something about your machine) rather than a general problem with the software... Same question, Pavel - tell us about your computer.

I don't get the sense that it's a Comment & Critique (C & C) forum, but a showcase for the capabilities of AP. But I'd also suggest that anyone who posts a picture implicity invites comments over and above the actual intent of a forum like this one, so (because I don't believe there's a documented rule against it) have at it!

Just out of interest - are you printing these files? Because if not, you can completely ignore the DPI setting.

A site search would have saved you the trouble of asking that...

Windows 8.1, 16gb of RAM - and AP flies on my machine. Stable too - it has only crashed once since I bought it about a month ago (and never during my use of the beta).

Not that confusing, apparently - this is the first post I've seen on the subject, and the OP figured it out too. Dunno: I don't think it's unclear that if you select (say) the tiff export option, you get a tiff. (No idea what I did to end up with two posts!)

Apparently not that confusing, Alfred - this is the first post on the topic that I've seen, and the OP figured it out too.

So three out of four respondents are happy to pay $200+? Seems a bit unlikely, doesn't it? I don't think people are taking your survey very seriously, so I doubt you're getting your "cold, hard facts".

So this is loading a Raw file, tzoumaz? 9 or 10 seconds is what a few of us have reported seeing with Raw files. Definite room for improvement, but Serif is aware of the problem.

I've assumed in this situation that "Affinity Files" simply means "formats workable in AP (or AD)". It's an accurate statement, and it isn't a problem given that the file is saved in the format I want anyway.

Course it's relevant, Patrick - if a user doesn't want (literally or metaphorically) to wish his life away watching an "in progress" indicator spinning ad infinitum. There are users on this forum right now with more than 4gb who are having serious performance problems when trying to edit large image files or use multiple adjustment layers, and so on. It's a truism that the minimum RAM on which a programme will run, and the amount of RAM required for it to run well, will usually bear little resemblance. That's why I specifically used the phrase: "not nearly enough for what most people will use Designer (or Photo, for that matter) for". Would you agree that I'm going to get a far better "user experience" with my 16gb of RAM than would a user with 2 or 3gb of RAM?

XP can only use a maximum of 3gb of RAM - not nearly enough for what most people will use Designer (or Photo, for that matter) for.

...Is, I think, a good way to evaluate Photo - I know what results I can achieve in PhotoShop, so let's see what Photo can deliver. It doesn't disappoint! Turnstone Reed bunting Cormorant Gannet Gannet Turnstone These were all taken back in 2014, on the East Yorkshire coast of England (Canon 70D/Sigma 120-300mm f/2.8 OS and 1.4x or 2x extenders, all hand-held) if anyone's interested. It's on the basis of results like these that I've been happy to replace PhotoShop entirely in my workflow, with Photo: not because I have a problem with Adobe or its subscription pricing - I don't - but because I simply don't need it any more.

OK - I'll play:

It's Christmas! They do get time off, you know...

If saved compressed in Irfanview it then opens in AP. Opens uncompressed in Windows Photo Viewer and Photos.

What R-C-R said... What you've done here is broadly equivalent to walking into your doctor's surgery, saying "I don't feel well" and expecting a thorough diagnosis to follow...

Just for balance, it handles the ones I use perfectly well. They do, Mike - there's regular input on the Adobe forums from designers, software engineers and other staff.

Sticky/last used settings are coming, Webb - you'll probably be able do this within a release or two.

Because Optics Pro is a one-stop deal - you either convert the file or you don't. In AP, the Develop stage is the precursor to further editing in AP: it makes perfect sense, given that the presumption is that you're developing prior to editing, to check whether you really want to stop the whole workflow in its tracks. Indeed, I'd argue that Optics Pro has this wrong: in pretty much any application you care to name, from image editing software to word processing, the default is that you're asked whether you want to abandon changes to a file you've changed.

Gets very close though, Patrick - there's nothing in rroddy's list that immediately jumps out as being impossible in Photo.

Photoshop does all of that - you don't need PS and Lr purely for image editing.

Something interesting(?): this happened to me last night. Editing a tif image converted in Capture One Pro 8 (resized to 1200px), I opened it in Viveza. It opened at 50% and the colours were exactly as you describe: zooming in to 100% view, the colours corrected. It happened repeatably on that file, but not on any others, including other Capture One conversions. And this morning - no problem with that or any other file. But...For some files, the small Navigator window shows the same "purple filter" look.

Ne too: although it's an easy problem to work around - in my case by selectively applying sharpening using the Topaz Detail plugin.

Exactly the same as PhotoShop in that regard. I don't get any sense that Photo is intended to become a Lightroom/Capture One replacement - that is, a Raw converter/DAM with editing abilities: it is (and is intended to stay, as far as I can tell) an editor with Raw conversion capabilities. Personally I don't want or need any native cataloguing function in Photo - what I use now does the job perfectly well, and I don't see a call to duplicate it in Photo.