totoff

Thanks very much for getting back. I've not used the beta any more since this happened but updated last week to 1.7. Let's see if it works.

I would like to check back if you were able to replicate and adress this issue? Thanks for letting me know.

Hi Sean, I did upload two files: .afdesign - this is the one which lost about two or three hours of work .pdf - this is the PDF I exported before quitting the app. By comparing it to the .afdesign file you can see how much was lost Both files are named Konsequent Basispraesentation.

Hi Sean P, thanks for your reply. 1. application created Affiinity Designer directory (not file) 2. yes 3. yes 4. yes - just let me know where and how Best regard

Hi there, I'm working on AFD Beta 1.7.11 on MacBook Pro from 2018 with Mac OS X 10.14.4 and have to report a very serious problem with file saving: After working for some days on a larger project I saved the file (to iCloud), exported a PDF and quit working for this day. The other day upon opening the file I was prompted with a dialogue box asking if I would like to restore from a previously stored version (like after a crash). Not thinking about I clicked ok and AFD opened a version of my file which reflected the status from tow days or so before – all subsequent work was lost and couldn't be restored. I made a copy of the file leaving the original file as it was, double checked all relevant settings (i. e. restoring intervall set to 300 seconds) and started again this time working on the copy. During work I manually safed on a very regular basis every few minutes. After being ready I once again exported my work as PDF, saved and quit the app. Upon restarting the app and reopening the working copy file, once again the file didn't reflect the last saved status (the one I exported the PDF from) anymore. This time not as many parts as before where lost, but all parts done within the last two hours of work before quiting were gone. Different to the day before no prompt appeared. I haven't used the Beta again since then but went back to 1.6.1 so I can't tell if this is file specific or not. But I can definitely confirm that the file was saved over and over again manually including the last version before quit (the one I exported the PDF from). I can also confirm there wasn't a crash or forced quit before this.

@walt.farrell thanks for your reply. Unfortunately I can’t post the picture in question to explain the task as I’m away from my desktop machine. In short, I have a portrait with an “atmospheric” background. I changed the aspect ratio of the canvas from 4:3 to 16:9. Now I need to fill this empty area I created with this background. Fill with inpaint failed as it always clones the person’s face as well.

Dear all, I need to clone from a static source point with the clone tool in photo. In other words I want the source point to remain fixed where it was originally set instead of following the clone tools movement with a fixed distance while hovering over the target area. From what I understood from the docs, this behavior can be achieved by unchecking the “aligned” checkbox but this doesn’t work for me (actually checking or unchecking the box doesn’t seem to change the tools behavior at all. Bug or feature or my fault - don’t know). Is that possible? Any help appreciated. Thanks.

Thank you very much for this comprehensive answer. Solved.

Hi all, I'm having a hard time wrapping my head around saving for web with export persona. I need to save for web in different sizes and for different screen resolutions. My filenames have to follow this naming conventions: myfile@2x.jpg myfile.jpg myfile_medium.jpg myfile_medium@2x.jpg etc. How can I achieve this? I know I can choose from presets like 2x in the slices panel in export persona. However, choosing 2x for example doubles the pixel size (in other words: interpolates the image) which is not what I want. I tried various other setting options without fully understanding it. Please have a look at the screenshot attached and you will understand my questions. Thanks for your help and replies!

Photo Mechanic is great but it want´t work together with images saved as .afphoto for the reasons described above. No DAM on the market will — and that´s the No. 1 issue with Affinity Photo for pro users imho.

You wan't find. The proprietary file format is the issue. This either needs to be addressed by Serif or a "native" DAM developed by Serif is required. No DAM on the market will overcome the boundaries build into the file format.

Hi all, I've followed this thread and the other ones about DAM carefully, but a very simple question I feel isn't answered: how do you catalogue and manage images with the proprietary .afphoto file format? As far as I see, .afphoto files neither support metadata, nor sidecar files nor thumbnails bigger than low, low, low resolution finder thumbnails. So how do you rate pictures, how to you tag them with keywords, how do you sort them in collections (aka smart searches), how do you get a preview that let you do a quick look and rating? None of this seems possible with .afphoto files (apart from native finder methods that apply to all image files). I don't need a new DAM as a Lightroom replacement nor another raw converter. All I need is a way to catalogue thousands of images in a way described above. Something like Adobe Bridge or Graphics Converter supporting .afphoto files would be good enough. I feel this is a big disadvantage of .afphoto files that they doesn't support image file management. How do you solve this?

Thank you. Solved.

Hello forum, I'm running AP 1.6.6 from the App Store on a MPB with Mac OS X 10.13.3. I have the Google Nik Collection installed on my machine and enabled it as a plugin for AP. Other image editors on my machine are Photoshop CS 6 and Graphic Converter 10. This setup worked fine for more than a year until today when I tried to open Settings -> Photoshop Plugins under AP settings panel. AP crashed immediately and does so again and again whenever I try to access the settings panel. So far I have done the following steps to solve the problem: uninstall AP and reinstall from the Appstore -> try to access AP settings -> crash uninstall Google Nik collection -> try to access AP settings -> crash reinstall Nik collection -> try to access AP settings -> crash This means, as for the moment, I can't access the settings panel without AP crashing no way what I do. Apart from this the app is working fine. Any ideas? Your help is very much appreciated! UPDATE: I've also moved com.seriflabs.affinityphoto.plist out of the library/preferences folder to no avail :-(

7 .afphoto files on my machine account for 1.5 GB. Sure, storage is cheap these days. But how to handle this with hundreds of pics and how (and where) to backup? Sorry, it does make a difference – at least for me.

Hi all, I bought AF Photo when it was launched to the market but quickly stopped using it for two reasons: huge, huge, huge file sizes and and no support for IPTC metadata. However, I came back recently wondering if this issues are sorted out in the meantime. Unfortunately I found myself disappointed again. I've read this thread carefully and decided to compare AF Photo against Photoshop CS 6. I made my tests with the following parameters: .CR2 Raw file with 3744 × 5616 pixels straight out of the camera "save history" feature turned of no edits at all, no layers, just opened the file in the respective application (AFP/PS), press "develop" and save in application file format This is what I found: | Color format | .afphoto | .psd | |:--|:--|:--| | 16 Bit RGB | 167,5 MB | 126,3 MB | | 8 Bit RGB | 167,5 MB | 62,3 MB | | 8 Bit, saved under new name | 167,5 MB | 62,3 MB | (unfortunately the editor doesn't support markdown - but this should be a table …) I think the table speaks for itself. PS files are considerably smaller compared to .afphoto, reducing to 8 bit does nothing in AFP, but in PS. Ben has tried to be helpful explaining how AFP manages file sizes and how to reduce it possibly but shouldn't an app for professionals just work? "Save under a new name to reduce file size" reminds me off Windows 2000 somehow, especially if it has no effect on file size at all. I would love to have somebody from the AFP staff addressing this thread again explaining if we may hope for improvement. In the meantime I'll stay with Adobe (though I don't like to). Thanks

Will the next release bring back the rotation tool in develop persona? The software is unusable without this - and could also enjoy several improvements in raw file handling too (see several posts in the forum here). Thanks.

Same here, no matter what I adjust. See also: https://forum.affinity.serif.com/index.php?/topic/11084-ap-fuji-raf/ Considering my overall experience about 10 days after purchase I would say AP is still in beta. Great potential but the roll out to the market came to early (e.g. no rotation tool in developer, macro persona has been removed, poor raw conversion and so on ...)

Thanks Jim for clarifying. However, the same alert appears upon opening JPGs with Adobe RGB assigned. AP is set accordingly.

No, it does not. All fine. I've checked again with several files (.CR2, .RAF, JPG) with Adobe RGB assigned (checked twice with Finder info and Photoshop) - they all trigger the notification. Did you assign the RGB profile in AF or in another app?

Paul, thanks for your reply. I'm currently not at my Mac. Will give this a try this afternoon GMT.

As far as I understand you will be prompted to save your developed file as a new file - so it's kind of non-destructive.

Yes I did and got acceptable results with gradation curves. However, I see a significant loss of details in middle tones. E.g. gray hairs in a portrait. While in ACR there are still tones in the darker areas in AP all I get is "mud" - no details at all. Just an example. Sorry for my English, I'm not a native speaker.

Hi Forum, I shoot in Adobe RGB and have likewise set color space in AP to Adobe RGB. However, whenever I open an image in AP a get a prompt saying the file was converted to Adobe RGB. Is this a bug or intentional? Thanks

That's true unfortunately. Many details are lost in AP compared to ACR and colors appear weird/not neutral sometimes. Room for improvement ...