Ablichter

I don't know why someone would do it, but convert it to 16 bit and its size will at least quadruple sextuple 4,26MB to 25MB. PS open a JPEG and only converting it to sRGB (even when it is in sRGB already) quadruples it.

Ah, okay. Aside that I believe that we don't really are able to discover the source(s) this collage have been made from, if it was made from a photo, someone indeed don't need to use a cam >500$ or shot RAW to ruin 'photos' this way. Same with most results of HDR I see around for years. Serious.

Sorry, I don't get what you want to tell.

Never the idea would come to my mind starting my PP workflow with an 8bit image which already is lossy compressed and developed by cams firmware.

.afphoto is no image file format, it's a propritary format to store the whole project, see also this thread and by this they should be treated as such. They are (so far) of no use outside the serife-bubble, not with PS, LR, Bridge, DAMs. Sorry when this already is known, but since TIF/PSD still gets compared with .afphoto files, I thought it's worth mentioning it again.

IMHO it's mainly not a question to which category it belongs than rather where in the workflow. Since this is not a resample it's just assigning metadata - I rather would have it assigned (like in ACR, fixed but changeable) before I press "develop" than have to assign it again and again for every single physical output. Or there is a automation in Photo persona which assigns (an adjustable) DPI value to an image as soon it gets an image transited from Develop persona.

I sencond this.

Loading RAW is slower than it was with V39. With V42 a preview is shown faster, but the developing takes longer. A difference up to +3 seconds with V42. Tested with a 64MB CR2 on two machines.

I couldn't reproduce this allegedly Microsoft Installer problem by enable logging and afterwards deleting the missing MSI*logs, but you should try like here is described with the LoggingOn.reg to switch logging ON (since we don't know in which state the MSI-logging is on your computer). Than you install AFP again, so that logs should be written. Before that make sure %temp% is writeable (usually it's c:\users\<your_login_name>\appdata\local\temp but you could have changed this) Since the MSI*.log -which is allegedly was missing- should have been written now, you should be able to uninstall. If still no joy, switch logging off like told on the site and try again. If this also not helps, you IMHO only can delete all Affinity Photo folders and clean up registry.

Not when I worked in Develop Photo on another image before. Open a RAW with PS, click Cancel in ACR. What happens? Does ACR stay open? No. Does PS close? No. What happened when "Done" was clicked?

Yes. 'cause it wasn't changed until some clicked Develop. Why? Assume I accidently loaded a RAW/DNG and just want to cancel its loading without I have to close Develop Persona to get back to Photo Persona. Usually Photo Persona is the starting point, no? This is where I want to get back.

As an IT guy I see it as Jon does. A cancel button (should) stop the current action and return me to the state I was before (which was Photo Persona) - without the need to press any other button.

Well, I do cancle the load op - or rather this is what I'd like to happen when clicking cancle.

Okay, thanks for clearing this.

Yes. No, it's not. Sorry. Aside that a "cancle" in ACR means not to touch the RAW (means also its metadata is untouched), it's not like this in ACR. Even with all values set to zero (except whitebalance and tint) we get different results. I either expect those zero values being applied or - even better - that the image is not opened at all when cancle is clicked. Combined with the actual behavior the metadata might get changed, in case they decide in future to write them to a sidecar file or a database (as ACR does).